Research intermediary file hosting service

[jwflory]

Summary

When a Telegram user sends a document file, upload it to an intermediary file hosting service to avoid leaking API key

Background

Is your feature request related to a problem? Please describe:

In v1.x.x, there is an option (disabled by default) to support sending documents from Telegram to IRC. As noted in #241, this leaks the Telegram bot API key. For the v2.x.x rewrite, we should not include this as an option without a way to mask the API key.

Describe the solution you'd like:

We might be able to use a third-party service, such as Dropbox, Mega, or other platforms to host documents. We could provide an API key option for a user to configure for any of these services.

Describe alternatives you've considered:

First we need to figure out what our possible platforms/services are.

Details

https://core.telegram.org/api/files

• Evaluate existing file hosting services out there
• Evaluate which ones have good Go libraries available
• Research rate-limiting for each platform
• Make final decision for what we will support and whether a default option is provided

Outcome

Successfully share files from Telegram to IRC without exposing Telegram bot API key

[jwflory]

Well, would you look at that? We already have an issue open for this: #159. 😅 Closing this one as a duplicate, let's use the older issue for discussing and tracking this.