Post suggeriti
Gli ultimi otto messaggi ricevuti dalla Federazione
-
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.
-
here's a side-project we might work on. writing up what a *good* RSS feed coming from a social network would look like.
they all seem to rush through it and often leave out one crucial bit. if we just wrote up a simple profile they probably would all just do it that way.
interested??
-
@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
-
These are two major updates any great improvements.
1/ ‚Quoots’ improve the CX on user level.
2/ ‚managed hosting‘ is a great way to establish financial independence and also drive adaption. I am sure, many orgs will appreciate this service. And I cannot wait for more public services (e.g. the police) to post their updates on mastodon instead of [insert walled garden].
Good job. 👍
