@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?

@puppygirlhornypost2 @trwnh @julian context for where this came from: trying to figure out if a given nodebb server is currently federating (i.e., has AP enabled)

@julian I was going to contribute it, but uhhh, no can do: https://github.com/NodeBB/NodeBB/issues/13391

I don't see a clearly documented path for development, so whilst I could probably make the required code change, I can't verify it would work

@julian in your webfinger controller for nodebb, you could support discovery of the instance actor via url:

https://community.nodebb.org/.well-known/webfinger?resource=https://community.nodebb.org/

Where the resource is exactly `base_url` from nconf

@hongminhee I know there's a FEP for emoji reactions, but I don't think there's ever been one for custom emojis? https://codeberg.org/fediverse/fep/src/branch/main/fep/c0e0/fep-c0e0.md

@hongminhee sounds like there needs to be a better FEP written, one which encourages alt text for custom emojis?