@lanodan

> can you send something like a bug report?

The gitlab 500s for me when I try to use it logged in, but the quick version is the same thing I've been complaining about a while, essentially /notice vs. /objects, and what you get back if you GET /users/p.

These already work correctly and do more or less what you want:

* "Accept: application/json" returns JSON
* "Accept: application/ld+json" returns JSON
* "Accept: application/activity+json" returns JSON
* "Accept: application/activity+json;q=0.9, text/html;q=0.1" returns JSON
* "Accept: application/activity+json;q=0.1, text/html;q=0.9" results in an attempt to load the webapp

These are the cases that are upsetting:

* "Accept: application/json, */*" results in an attempt to load the webapp
* "Accept: application/activity+json;q=0.9, */*;q=0.1" results in an attempt to load the webapp
* "Accept: application/*" results in a 302
* "Accept: */*" returns an attempt to load the webapp

I don't think it's possible to get a 405 or 406 out of Pleroma. I don't think it should be the case that it attempts to *just* load the webapp, I think it should return HTML with the content on the page and the script tags that load the webapp, that way the resource is at least represented.

Right now I'm just parsing JS but I plan to parse HTML (so as to make it easier for this to work properly: https://www.infoq.com/presentations/web-api-html/ ; I've done that kind of API before and the result is exceedingly pleasant).

> There is way worse for Accept header stuff btw

That is why PeerTube got S-tier. I played "Guess the magic string" for a while and then made a ranty post.