-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP redirector service for Telegram content #147
Labels
Comments
ForNeVeR
added a commit
that referenced
this issue
Oct 10, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 10, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 11, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 25, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 26, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 27, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 30, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 30, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 30, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 30, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 30, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
Oct 31, 2021
ForNeVeR
added a commit
that referenced
this issue
May 2, 2022
ForNeVeR
added a commit
that referenced
this issue
May 31, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
This update has introduced a FileUniqueId support, that's required to properly handle the photos of different sizes.
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 2, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 3, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 3, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 3, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 3, 2022
ForNeVeR
added a commit
that referenced
this issue
Jul 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As the first minimally viable step of #102, I propose us to do the following:
Add database support to Emulsion (should be optional: I host a plenty of Emulsion instances already, and not every one of them demands a separate database).
We should store the correspondence between Telegram message/content ids and our internal ones in said database.
Every content id gets a nanoid.
Every content-rich message gets that nanoid included instead of the current message link (like
https://codingteam.org.ru/tg/<nanoid>
instead ofhttps://t.me/<tgid>
).Create a HTTP service which will serve requests to
https://codingteam.org.ru/tg/<nanoid>
, and just redirect them to the correspondinghttps://t.me/<tgid>
instead.This will require us to store both Telegram message id and content id together. Collisions are possible if there are several messages with the same content id (not sure how, but technically possible). In such cases, just generate several entries (for each content id + message id pair).
At a later point, we may migrate and renormalize the database if we decide that the message ids aren't required.
The text was updated successfully, but these errors were encountered: