4 ms·
Thank you for your write-up, I ran into similar issues a couple of months back. Another gripe with the technical implementation of mastodon is the CORS headers
by louismerlin 3y ago
Thank you for your write-up, I ran into similar issues a couple of months back.
Another gripe with the technical implementation of mastodon is the CORS headers required to access the ActivityPub API [0].
Because of this issue, an activitypub-aware frontend for mastodon has to have its own mastodon server running, which adds a whole bunch of hurdles.
[0]:https://github.com/mastodon/mastodon/issues/10400 https://github.com/mastodon/mastodon/issues/10400
- jeroenhd 3y agoI think this only applies to web clients, but I don't think ActivityPub's C2S protocol was ever designed to be used by arbitrary web clients. I suppose you could work around it by setting up some kind of proxy for requesting Mastodon URLs; you may need to do that anyway if the other server has authorised fetch enabled. There are a whole bunch of technical implementation details that I disagree with when it comes to Mastodon. I wish the many MissKey forks would stabilise, because it seems a lot saner (yet every time I consider setting up a server, there has been a new fork thst everyone is switching to).
- junon 3y agoCORS only applies to browsers, this is an inherently different problem.