Gli ultimi otto messaggi ricevuti dalla Federazione
-
-
@julian Congrats on ActivityPub.space btw- made an account. Looks cool.
-
@julian All I did was make both /actor and /relay accepted follows from /actor, going through the issues in their repo and you showing me the resolver page is what made me try it. https://github.com/yukimochi/Activity-Relay/issues/90
-
incentive@mastodon.circlewithadot.net so what was the issue, a bug in Activity-Relay?
The LitePub section on FEP-ae0c: Fediverse Relay Protocols: Mastodon and LitePub is pretty vague about deviations from expectations. It would be good to shore up this FEP a bit.
-
@julian Confirmed! "relay-server | INFO[0263] Sent MutuallyFollow Request : https://activitypub.space/actor
relay-server | INFO[0263] RelayState reloaded "🤝
-
-
@julian I rebuilt the docker image with some changes in resolver - you're welcome to try again in the meantime if you wish - if not I can return to this tomorrow :)
Appreciate you looking into this with me.
-
incentive@mastodon.circlewithadot.net The code suggests that when parsing the follow request, it's checking object and ensuring that it is one of:
https://www.w3.org/ns/activitystreams#Public It's own ID (so, https://relay-us-east.circlewithadot.net/actor)NodeBB is sending https://relay-us-east.circlewithadot.net/actor, so it should satisfy that constraint, but I am not sure where in the Activity-Relay code it is failing out.
