Giulio Muscarello

The GitHub API has a /compare endpoint, we could use that: https://api.github.com/repos/honeytrap/honeytrap/compare/f7bc222...1585cd7 However, for production deploys I think it might be best to use the /releases endpoint (see https://api.github.com/repos/CapacitorSet/honeytrap/releases for...

This was discussed in chat with Remco, I think that storing all assets in a folder is the best solution - the alternative we explored was using assetfs, but that...

For the time being I don't expect such an issue to occur with WordPress, since I think one would rarely need to have two different WordPress honeypots running on the...

That's a good idea, I might implement it sometime. (If someone else wants to work on it, PRs welcome.)

It would be nice if one could use a more "natural" notation like `20d` for "twenty days". By the way, I think such a plugin would benefit from a scheduling...

Depends on #93. @Ichicoro is working on a scheduling API that should allow us (well, her) to implement both the Events plugin and this one. Consider this issue taken.

It should work by default in groups. Did you accidentally forget [privacy mode](https://core.telegram.org/bots#privacy-mode) enabled? In channels it *should* work, but seemingly it doesn't, perhaps due to a bug in `node-telegram-bot-api`?...

Apparently, this can't be done straight away because while "actual" media (eg. photos) has a file ID, this is not true of locations (have lat/long) nor contacts (have name/phone no.).

What is the advantage to doing this? The interface will be just as powerful but more verbose, since plugins can't use this.sendMessage but must use this.api.sendMessage instead.

Maybe this could be done with a global as well as local db (`this.globalDB`, `this.localDB[message.chat.id]`)? However, local DB access would be rather cumbersome. Perhaps it could be passed to the...