ronilaukkarinen / fedionfire Goto Github PK

I mentioned this on Mastodon, but just to be absolutely certain it gets addressed: the streaming API doesn't just contain events of new stuff being posted. Every event sent contains a type, which indicates specific expected behaviour for the consumer.

One of these event types is deletes, which are issued when a user deletes their post: currently Fedionfire does not respect these delete events, which should remove the post from the output.

you'll also want to make sure you're respecting status.update too, not just update. status.update says "the status with this ID has been edited & therefore it should be updated in the UI"

This gives you three events you should listen to: update, status.update and delete. The other's aren't relevant for your use-case.

https://docs.joinmastodon.org/methods/streaming/#events

I have no idea how to implement this and maybe using relays is the answer (#3), but mastodon-firehose has done this in the past. It would be a blast to see as much sources as possible, since mastodon.social is just a start.

Right now the token has only read:statuses permissions so no harm cannot be done by using it. But it is not a good thing to expose the API code anyway so need to figure out a better way to do this.

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: ‪mastodon/mastodon#24116