Telegram support

[sjehuda]

I am not fond of that (yet anothre data-mining) platform, but it would probably be useful.

@ccbikai, the creator of project RSS.Beauty, has created project https://github.com/ccbikai/BroadcastChannel

I would have asked him to merge it with Granary, if it was written in Python.

[snarfed]

To clarify, the request here is for Telegram support, right?

I'm not very familiar with Telegram myself, I don't really use it, so I wouldn't be the best person to build this, but I'm open to it. My main reluctance is that granary is primarily aimed at social network type data, not messaging, which is very different. I take it that Telegram is kind of both though? If so, it could maybe still work.

Here are Telegram's API docs. I think we'd use the "Telegram API" there.

[sjehuda]

Yes. Indeed. I just did not want to explicitly publicize that platform, and therefore I wrote TG.

TG is another closed XMPP server.

They might be utilizing eJabberd, with their own modifications, of course.

TG has two type of chats, "chat", and "super chat", and also "channel".

The "chat" is a basic chat as of XMPP.

The "super chat" is really a PubSub service (same as of XMPP) which everyone is previledge to post to it.

The "channels" are really Atom Over XMPP (XMPP PubSub services) which only selected people are able to advertise to it.

So, by TG I refer to "channels", not "chat" nor "super chat".

---

Both of these are HTTP gateways to TG channels. Channels are the advertising platform of TG.

https://blog.rss.tips/

http://rsshub.app/telegram/channel/aboutrss

@AboutRSS Do you know of a Python developer who would want to add support for TG into Granary?

[snarfed]

Thanks! Understood. A volunteer would be great! But also, before we start, I'd want to hear from a user, with a use case where they really need Telegram support in granary, and a concrete plan to use it immediately, as soon as it's available. Like #860!

[sjehuda]

* I am not over that network anymore. * There are people who exclusively share data over there. * The information is productive and interesting. * I intend to immediately use it. Question -------- If you would ask me how so; that is, why not other centralized networks? My answer, is that I have never had an account over a centralized publishing platform. My only centralized account was over WA, after pressured by people to have it. I have experimented with TG as a proposed replacement for WA. Eventually, after I have created a few channels that turned popular, which was a grave mistake to do, I was inside the TG network for too long, that I discovered sources of interest. Interesting channels would be "libreware" and "aboutrss". Thankfully, "aboutrss" maintains presence at https://blog.rss.tips/rss.xml Post script ----------- I sense that this platform, if is popular as it states, is subsidized, and has a purpose (i.e. a plot, so to say), to try to concentrate people into that publishing network instead of regular internet sites. The consequent purpose, is to lock communities, in order to moderate their size; that is, there might be two communities of identical values that have 30K and 50K subscribers, yet they are not aware of each other. I am attempting to create parallel communities over decentralized networks, such as Nostr, DeltaChat, and XMPP, or RSS, just so that it would be possible to reach to them without accounts.