Posting about my Mastodon Relay again, registration is open so feel free to add it (location of the relay is US East Coast).
-
@julian Hmm, it seems the software I'm using has non-Public hard setting that isn't configurable on /actor, so I don't think it's compatible with your instance unless I can figure out a way to lax those settings
incentive@mastodon.circlewithadot.net can you share more information? What's a "non-public hard setting"?
Also, what software are you using? I have mainly tested against Aoderelay, but I should be compatible with others too
-
@julian I'm using https://github.com/yukimochi/Activity-Relay, and the error I'm getting is "relay-server | ERRO[0275] Rejected Follow, Unfollow Request : https://activitypub.space/actor only https://www.w3.org/ns/activitystreams#Public is allowed to follow"
I think I get the same error when a Friendica instance attempts as well.
-
@julian I'm using https://github.com/yukimochi/Activity-Relay, and the error I'm getting is "relay-server | ERRO[0275] Rejected Follow, Unfollow Request : https://activitypub.space/actor only https://www.w3.org/ns/activitystreams#Public is allowed to follow"
I think I get the same error when a Friendica instance attempts as well.
incentive@mastodon.circlewithadot.net ooooooh cool, Activity-Relay was one of the relays I was not able to test against... here I thought they were just closed, now I know it's an error!
This is the relevant bit of code after searching their repository... Let's see what I can dig up.
-
@julian I think /relay needs to be added as a valid follower of /actor. I'm going to test a change really quick and see if I break it or not lol
-
@julian I think /relay needs to be added as a valid follower of /actor. I'm going to test a change really quick and see if I break it or not lol
incentive@mastodon.circlewithadot.net The code suggests that when parsing the follow request, it's checking
objectand 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. -
@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.
-
@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.
-
@julian Confirmed! "relay-server | INFO[0263] Sent MutuallyFollow Request : https://activitypub.space/actor
relay-server | INFO[0263] RelayState reloaded "
-
@julian Confirmed! "relay-server | INFO[0263] Sent MutuallyFollow Request : https://activitypub.space/actor
relay-server | INFO[0263] RelayState reloaded "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 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
-
@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
@julian Congrats on ActivityPub.space btw- made an account. Looks cool.
-
@julian Congrats on ActivityPub.space btw- made an account. Looks cool.
