From c020411e07ec1cc2e42ff5565df70e7c73fd2c30 Mon Sep 17 00:00:00 2001 From: Nemo Date: Fri, 8 May 2020 23:18:39 +0530 Subject: [PATCH] considering this one solved --- README.md | 41 +++++++---------------------------------- telegram-to-rss.md | 36 ++++++++++++++++++++++++++++++++++++ 2 files changed, 43 insertions(+), 34 deletions(-) create mode 100644 telegram-to-rss.md diff --git a/README.md b/README.md index acdc7db..02d939c 100644 --- a/README.md +++ b/README.md @@ -242,42 +242,15 @@ Keep it pluggable, otherwise its of no use. ## 🚀Telegram To RSS -There are quite a lot of Telegram channels that are popping up these days that I really like using. +This is fairly well solved at this point, see the following: -Except there are lots of issues with telegram channels: +- [There is an existing `TelegramBridge` in RSS-Bridge](https://github.com/RSS-Bridge/rss-bridge/pull/1175) that just scrapes telegram HTML. I've enabled it on my RSS-bridge server, so you can try it out at . +- https://docs.rsshub.app/en/social-media.html#telegram +- https://t.me/Channel2RSSBot +- https://notifier.in/ (Free for 100 messages/month, paid beyond that) +- https://tg.i-c-a.su/ (Free with reasonable rate-limits) -1. They are inside a closed network by-default. In order to access them you need to use the Telegram client -2. They are not linkable -3. No sharability without their client, and even then the content is duplicated. - -The idea is to create a generic website that does these 2 things: - -1. Publish an RSS Feed of every telegram channel it knows about. -2. Provide a direct link for every feed item on the RSS, so users without RSS readers can also browse through the listings. - -Since `web.telegram.org` is taken already by the web client, maybe something like `opentelegram.in` should work fine. - -There are a few related paid projects, but they all rely on the Telegram Bot API: - -- https://news.ycombinator.com/item?id=17617675 -- http://tele.ga/about.html - -The issue with using the bot API is that bots need to be explicitly invited -to channels, while users can join channels on their own. This makes a world -of difference in that this doesn't require perission from the channel admins anymore. - -You could likely get this sponsored from the Internet Archive if you get something up and running. - -*UPDATE*: Turns out [there is an existing `TelegramBridge` in RSS-Bridge](https://github.com/RSS-Bridge/rss-bridge/pull/1175) that just scrapes HTML instead. I've enabled it on my RSS-bridge server, so you can try it out at . - -Related links: - -- [My attempt](https://github.com/captn3m0/opengram) - didn't go anywhere because the Node.JS library wasn't feature complete. -- [MTProto Docs](https://core.telegram.org/mtproto) -- [Various Telegram client source code](https://github.com/TelegramOrg) -- [MTProto proxy](https://mtproto.co/) -- [Difference between the MTProto and Bot APIs](https://docs.pyrogram.org/topics/mtproto-vs-botapi) -- [Pyrogram](https://docs.pyrogram.org/faq#what-is-pyrogram) seems to support MTProto, so that is what I'd try next. +You can see a archive of the original idea at [telegram-to-rss.md](telegram-to-rss.md). ## 🎁 Disable Local Fonts Extension diff --git a/telegram-to-rss.md b/telegram-to-rss.md new file mode 100644 index 0000000..b51d902 --- /dev/null +++ b/telegram-to-rss.md @@ -0,0 +1,36 @@ + +There are quite a lot of Telegram channels that are popping up these days that I really like using. + +Except there are lots of issues with telegram channels: + +1. They are inside a closed network by-default. In order to access them you need to use the Telegram client +2. They are not linkable +3. No sharability without their client, and even then the content is duplicated. + +The idea is to create a generic website that does these 2 things: + +1. Publish an RSS Feed of every telegram channel it knows about. +2. Provide a direct link for every feed item on the RSS, so users without RSS readers can also browse through the listings. + +Since `web.telegram.org` is taken already by the web client, maybe something like `opentelegram.in` should work fine. + +There are a few related paid projects, but they all rely on the Telegram Bot API: + +- https://news.ycombinator.com/item?id=17617675 +- http://tele.ga/about.html + +The issue with using the bot API is that bots need to be explicitly invited +to channels, while users can join channels on their own. This makes a world +of difference in that this doesn't require perission from the channel admins anymore. + +You could likely get this sponsored from the Internet Archive if you get something up and running. + + +Related links: + +- [My attempt](https://github.com/captn3m0/opengram) - didn't go anywhere because the Node.JS library wasn't feature complete. +- [MTProto Docs](https://core.telegram.org/mtproto) +- [Various Telegram client source code](https://github.com/TelegramOrg) +- [MTProto proxy](https://mtproto.co/) +- [Difference between the MTProto and Bot APIs](https://docs.pyrogram.org/topics/mtproto-vs-botapi) +- [Pyrogram](https://docs.pyrogram.org/faq#what-is-pyrogram) seems to support MTProto, so that is what I'd try next.