Closed Cl0v1s closed 1 year ago
I posted about an issue about webfinger searching of lemmy posts in mastodon now not working here and someone mentioned I should mention it in this issue as well in case its related
Haven't been able to follow almost any Lemmy groups from Akkoma due to this error, except one for some reason: !196@lemmy.blahaj.zone, which works just fine.
Maybe they answer differently to the webfinger request?
And maybe that community is all I need... rule
The root of this issue is in activitypub_federation crate. Webfinger is resolved using generic object fetching here: https://github.com/LemmyNet/activitypub-federation-rust/blob/af92e0d53204a2ccd13bc0db3c58de24bff646bf/src/fetch/webfinger.rs#L39C26-L39C43
And the function for fetching, which due to it being generic has nothing to do with webfinger, accepts only one MIME type and it is activity+json https://github.com/LemmyNet/activitypub-federation-rust/blob/af92e0d53204a2ccd13bc0db3c58de24bff646bf/src/fetch/mod.rs#L54
Does this need work for the other way around? I notice we don't have handling of this mimetype in our default nginx config
We route all requests to .well-known path to backend:
https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx_internal.conf#L86
Thanks for your work !
Requirements
Summary
When trying to follow a Lemmy instance from external softwares (such as Akkoma), Lemmy starts webfinger queries accepting only a
application/ld+json
MIME type where it should bejrd+json
orxrd+xml
https://datatracker.ietf.org/doc/html/rfc7033#page-11This leads to fails on the foreign server.
Steps to Reproduce
(With foreign instance being pleroma / akkoma)
Technical Details
Crash on Akkoma side, after the Lemmy request:
Version
BE: 0.17.4
Lemmy Instance URL
lemmy.world