-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
Option to subscribe to Fediverse (Mastodon / Lemmy) #63
Comments
Hey, There is no option to do that currently, I'm not familiar with the protocol used by the Fediverse and I'd have to allocate some time to read into it. It is something that I'd like to add eventually though. |
For mastodon a little tips : you can use RSS for a specific thread/person |
@svilenmarkov Thanks for the quick reply and that will take a look into it, independently if an integration is coming or not. the Fediverse uses the ActivityPub Protocol, or at least Mastodon/Lemmy are mostly using this protocol. For further reading here a few links: w3.org
@MikaXII You are right, but that only works for a specific account/thread not like your home feed / time line of your followed accounts as all-in-one place. But if you just want see posts from one specific source, than you can definitely use this. For Lemmy this works too, if you are in a subcategory next to the title in the upper section you have the RSS symbol and can use this link to "subscribe" to this thread, ie worldnews of lemmy.world. The main difference, compared to the reddit integration, for the added subreddit you see additional details like comment counter, etc. that would be cool to have this for Lemmy too and not "just" the post itself. But it all depends on how intensive this integration would be. |
Is there an option to add support for Lemmy (reddit Alternative) and/or Mastodon (Twitter Alternative)?
It would be convenient to subscribe to Threads created in the decentralized Fediverse instead of relying on services like reddit etc.
Thanks in advance for this great project!
The text was updated successfully, but these errors were encountered: