search

ronilaukkarinen / fedionfire

Watch every Mastodon/Fediverse post in real-time - filter the firehose
https://fedionfire.stream
9 stars 1 forks source link

Use relays instead of Streaming API #3

Closed ronilaukkarinen closed 1 year ago

ronilaukkarinen commented 1 year ago

The better way to develop something like this is to use the Relay's functionality, instead of the streaming API.

By using the Relay's API, you'd also be needed to add in a privacy policy to document how data is stored, handled, distributed and secured.

For a bit of background, take a look at this ticket: ‪https://github.com/mastodon/mastodon/issues/24116

ronilaukkarinen commented 1 year ago

@ThisIsMissEm Can you give me a hint on where to start with this? Streaming API is now a bit familiar to me, but I can't seem to find documentation about Relay API anywhere.

I'm now going to ask a very newbie question, since I don't know enough about this. How to fetch data from relays via EventSource or something similar? I need some head start.

ThisIsMissEm commented 1 year ago

So a "relay" is just any automated service instance; essentially they are added by an admin, and then receive content via activitypub. This has a bit more information: https://joinfediverse.wiki/index.php?title=Fediverse_relays&mobileaction=toggle_view_desktop

ThisIsMissEm commented 1 year ago

You could also talk to @astro who's behind FediBuzz.

astro commented 1 year ago

FediBuzz not only consumes Mastodon's streaming API but also serves it: https://fedi.buzz/api/v1/streaming/public

ronilaukkarinen commented 1 year ago

Oh I see! Thanks. Definitely helpful. I mistakenly thought there is a thing called Relay, but now I get it. Will probably get more energy first and then get more focused on this… Thanks again. 🫶

ronilaukkarinen commented 1 year ago

Closing this in favor of #4.