Chebucto Regional Softball Club

@antolius @julian or just treat it as ambiguous?

@julian @antolius arguably, activitypub as a protocol in NodeInfo should be deprecated and in its place activitypub-s2s and activitypub-c2s should exist, since activitypub is two protocols in a trenchcoat

@dansup @silverpill sounds like if a NodeBB instance isn't federating and isn't using activitypub, then it shouldn't list it in the protocols supported?

cc @julian

@julian eh? I mean, sure, or just detect whether the request is a GET / HEAD / OPTIONS request, and then don't send the content-type header? (since those methods don't support request bodies iirc)

@julian which actually makes sense, because with a GET request, you're not sending any request content, and Content-Type applies to the request body, not to the content type you want back.

@julian oh! it's because you're sending the Content-Type header, send Accept instead.

@julian try sending `Accept: application/jrd+json`

Since that's the content-type for webfinger, not application/json. In fedify, the fetch call is also with redirect manual, such that max redirection logic and SSRF checks can be done.

@julian fedify manages it, so many take a look at their webfinger implementation?