Federating servers
-
So, one part of the popular imagination about ActivityPub I've seen is the idea of server federation.
I think the idea is that if two servers have interacted in some way, all (?) public (?) content from one server will be sent to the other server, and vice versa.
This comes up a lot with new servers; people ask to have a post shared broadly so that their server rubs shoulders with others, getting the federated feed flow going.
ActivityPub does in fact have a mechanism defined for this:
> Additionally, if an object is addressed to the Public special collection, a server MAY deliver that object to all known sharedInbox endpoints on the network.
As far as I've seen, most (?) servers don't implement this; it would overwhelm small servers pretty quickly.
However, some (?) servers do implement it for some (?) activities, especially profile update and delete activities.
Is this the origin of the idea that new servers need to have their content shared around? Are people misunderstanding the way that relays work? Is it just a trick to get your content shared?
-
Another possibility is that when someone asks to have their content shared, that will result in a few Follow requests, which does result in their future content being distributed to other servers (and public content goes to Fediverse and hashtag feeds).
So, it seems like the sharing is what got the distribution going, even though it is indirect (sharing causes following causes appearing in the Fediverse feed).
-
Another possibility is that when someone asks to have their content shared, that will result in a few Follow requests, which does result in their future content being distributed to other servers (and public content goes to Fediverse and hashtag feeds).
So, it seems like the sharing is what got the distribution going, even though it is indirect (sharing causes following causes appearing in the Fediverse feed).
@evan I think - reviewed it given that you corrected my misapprehension the other day - that other than for those who live'n'breathe protocol, the nitty-gritty details are really not spelled out in the platform documentation for users or admins.
Or even those of us who understand enough to read along (I did remember that I "knew" this, just not that expert in expressing), it's more detail than we can articulate when there's a new user or instance showing up.
-
In FEP 1b12, that is what occurs (most of the time) - as soon as an instance has a dozen users their interests will be varied enough that almost every active community in the threadiverse is subscribed to and they'll be receiving almost all the traffic.
It works out ok at our current scale (small).
-
Another possibility is that when someone asks to have their content shared, that will result in a few Follow requests, which does result in their future content being distributed to other servers (and public content goes to Fediverse and hashtag feeds).
So, it seems like the sharing is what got the distribution going, even though it is indirect (sharing causes following causes appearing in the Fediverse feed).
@evan in the Mastodon sphere, boosting a post has these side effects:
- servers that receive the boost will now be aware that the boosted post exists. if it contains hashtags, then that post might show up in hashtag timelines/searches and the home timelines of anyone following that hashtag.
- servers will also be aware that the author of the boosted post exists. their profile can appear in search results based on their account's name/summary.
-- (in the future, their outbox might be backfilled) -
Another possibility is that when someone asks to have their content shared, that will result in a few Follow requests, which does result in their future content being distributed to other servers (and public content goes to Fediverse and hashtag feeds).
So, it seems like the sharing is what got the distribution going, even though it is indirect (sharing causes following causes appearing in the Fediverse feed).
@evan personally I think "server federation" is best achieved through relays.
The distribution model fits best, and the technology already exists, even if not broadly implemented.
One could be able to plug a server instance actor in to subscribe to its relay.
-
@evan personally I think "server federation" is best achieved through relays.
The distribution model fits best, and the technology already exists, even if not broadly implemented.
One could be able to plug a server instance actor in to subscribe to its relay.
@julian yes, I agree. This is a different idea -- that somehow interaction between actors on different servers will make their servers connect and share data. It's incorrect, but it's interesting.
-
@julian yes, I agree. This is a different idea -- that somehow interaction between actors on different servers will make their servers connect and share data. It's incorrect, but it's interesting.
@evan oh I see what you mean... that a server merely discovers another, and that kickstarts a mutual sharing of activities.
I'm afraid that would be a bit of a scaling challenge
-
@evan oh I see what you mean... that a server merely discovers another, and that kickstarts a mutual sharing of activities.
I'm afraid that would be a bit of a scaling challenge
@julian here's an example I found with a search:
-
@julian here's an example I found with a search:
-
@silverpill@mitra.social really? How does it work?
-
@silverpill@mitra.social really? How does it work?
Does it use the relay method? I always thought that if I implemented something like that I'd be the first. Cool to know Pleroma already supports.
-
That makes sense.
When I implemented the Litepub style relay logic I figured it would immediately work the same way as well (since two-way relay communication uses the Follow-Accept flow as well.)
It did not work immediately with NodeBB, have yet to figure out why
-
So, one part of the popular imagination about ActivityPub I've seen is the idea of server federation.
I think the idea is that if two servers have interacted in some way, all (?) public (?) content from one server will be sent to the other server, and vice versa.
This comes up a lot with new servers; people ask to have a post shared broadly so that their server rubs shoulders with others, getting the federated feed flow going.
ActivityPub does in fact have a mechanism defined for this:
> Additionally, if an object is addressed to the Public special collection, a server MAY deliver that object to all known sharedInbox endpoints on the network.
As far as I've seen, most (?) servers don't implement this; it would overwhelm small servers pretty quickly.
However, some (?) servers do implement it for some (?) activities, especially profile update and delete activities.
Is this the origin of the idea that new servers need to have their content shared around? Are people misunderstanding the way that relays work? Is it just a trick to get your content shared?
@evan At Friendica we have a third way. When configured, we distribute posts to other servers that subscribed to the hashtags that the item contains.
But anyway: I would like to have got something like the AppView in the Atmosphere. Means: not a dumb relay but something like tags.pub, but much more sophisticated.
-
R AodeRelay shared this topic
-
@evan At Friendica we have a third way. When configured, we distribute posts to other servers that subscribed to the hashtags that the item contains.
But anyway: I would like to have got something like the AppView in the Atmosphere. Means: not a dumb relay but something like tags.pub, but much more sophisticated.
@heluecht@pirati.ca like a public firehose of sorts?
Suppose there's no reason why not, you would just get yelled at constantly for "scraping" posts.
-
R AodeRelay shared this topic
-
@i@declin.eu @silverpill@mitra.social @evan NodeBB now also ships with /actor that can be followed. It will act as a relay <img class="not-responsive emoji" src="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f44d.png?v=7e3567dc339" title="
" /> -
@julian To which point do you refer? For my first mentioned one we have got a special document at
.well-known/x-social-relaythat every Friendica server publishes that contains information about the subscribed hash tags.And concerning the second point, I imagine some relay service that does not simply forward everything, but that knows which content you you are interested in. So when you subscribed to user A and user B posted something in a thread that user A started, then the relay would forward it to you, although you never subscribed to B. And when then the account B got deleted or blocked, then of course you would be notified as well.
-
@julian To which point do you refer? For my first mentioned one we have got a special document at
.well-known/x-social-relaythat every Friendica server publishes that contains information about the subscribed hash tags.And concerning the second point, I imagine some relay service that does not simply forward everything, but that knows which content you you are interested in. So when you subscribed to user A and user B posted something in a thread that user A started, then the relay would forward it to you, although you never subscribed to B. And when then the account B got deleted or blocked, then of course you would be notified as well.
This can be done with inbox forwarding or special activities (FEP-171b or FEP-1b12).
Selective relays may be used for other things though. There is https://github.com/dtp-mstdn-jp/selective-relay that apparently can filter activities by hashtags, domains and number of attachments
-
This can be done with inbox forwarding or special activities (FEP-171b or FEP-1b12).
Selective relays may be used for other things though. There is https://github.com/dtp-mstdn-jp/selective-relay that apparently can filter activities by hashtags, domains and number of attachments
@silverpill @julian Currently there is no ActivityPub relay available that could do what Atmosphere's AppView is capable of. -
@silverpill @julian Currently there is no ActivityPub relay available that could do what Atmosphere's AppView is capable of.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better π
Register Login