danh42 / mi1kb0t Goto Github PK

https://duckduckgo.com/api
I think using that would be pretty cool

Images currently need to be handled by plugins on a per-network basis. There are already weird glitches with Messenger's images, and additional networks will only complicate things more. There should be core support for sending images that gets handled by the network. Potential example:

reply({
    image: "http://example.com/image.jpg",
    alt: "Message to be displayed on text-only networks (if blank, use the image URL)"
});

Possibly also allow for supplying a message and an image in the same reply call, to be sent in the same message. Messenger allows this, and other networks could always just handle it on their end as two messages if needed.

When the bot has been connected to Mesenger for an extended period, it eventually loses the ability to respond to messages, with reply() calls failing silently. Incoming messages are still processed. This is a bug in the facebook-chat-api library, but can probably be worked around on this end by quickly dis/reconnecting nightly.

The Google Custom Search API sometimes returns image URLs as x-raw-image:///(hex) rather than HTTP links. This currently crashes the entire bot, but even if #12 gets taken care of, it would be better to select a different image rather than sending nothing at all (or an error message). If an unsupported URL is detected, maybe try a couple other results and check their URLs before failing.

This would be cool.

8 ball tells you try again in a few responses despite the fact that if you ask it the exact same question it'll rehash and tell you to try again again. Maybe add another layer of entropy or just remove those as responses something.

Fuck, any fix for this?