Skip to content
Posts
Yes the title is correct, but I had nothing malicious in mind!
What this is about For @qzt@queereszentrumtuebingen.de we include the public feed in a sidbar on the homepage. Initially this was done using the standard API to fetch statuses /api/v1/accounts/{account_id}/statuses and worked like a charm. The problem started when GoToSocial (the fediverse server we use, similar to mastodon) implemented authorized fetch. This is a a good thing! Authorized fetch means, that every call to a endpoint needs to be authorized by an access_token.
Introduction RSS is amazing! While not everyone thinks that, most people that understand RSS, like it. This presents a problem, as most people don’t have chance to learn about it. Unless there is a person in the community that doesn’t shut up about how great RSS is (maybe that person is you), they might not even know what it is, let alone use it.
One big reason for this is, that when you click an link to an RSS feed you download a strange file that most people don’t know how to deal with.