Email or username:

Password:

Forgot your password?
Fediverse's posts Post Back to profile
Top-level
Qazm

@HistoPol @david @paul @fediversereport @fediversenews @Bluedepth @darren @juneussell @volkris @davetroy Mostly. Unlike on blockchain-based systems like Nostr and Secure Scuttlebug, ActivityPub (that is: the protocol underpinning Mastodon federation) can support an infinitely scaling network. It does this by never pulling in content unless it is (likely) needed by a local client, and by discarding duplicates of data that aren't needed anymore (like old copies of remote media. Clients can fetch a fresh copy from the origin directly, if necessary).

Normally, a large instance in fact makes processing a little easier for others, as a post needs to be pushed only once to reach all followers on a particular remote instance.

There are some exceptions to this, like boost and favourite notifications that come back on viral posts, so I hope most servers will eventually gain some way to aggregate those into lightweight "X boosts, Y favourites" messages after a threshold. That's more user-friendly than having a bunch of ★★★★★★★★★★★★★★★… in ones notifications column, anyway.

12 Mar 2023 at 21:20 | Wall-to-wall | Open on tiggi.es
4 comments
David Boles
Qazm replied to David

@david @HistoPol @paul @fediversereport @fediversenews @Bluedepth @darren @juneussell @volkris @davetroy Sorry, I didn't see this at first.

Relays are mainly to merge participating instances' Local Timelines into each one's Federated Timeline, in addition to the posts coming in through normal remote follows, which also helps to fill trending tags. It's a good way to make those discovery features more useful in a group of smaller instances with similar topics, but I'm pretty sure they always increase resource use even if they could be used to send messages to multiple direct recipients at once. (I haven't checked whether the software actually does that, but my hunch is that in many cases it does not.)

What I'm talking about is a server acting as (lower-case) relay for its local users. Let's say you have a thousand followers on mastodon.social. When you make an Unlisted post, then to reach all those followers, your server needs to push that action to that instance only once, and it'll take care to show the post to all interested users by itself.

If you attach an image, your instance needs to give it to the other one only once too, through a similar mechanism, not once for each follower. The other instance should normally cache a there-local copy for a while.

If you @-mention a few people from the same remote instance directly, they can all appear as recipients (to be notified) in the same single server-to-server message.

@david @HistoPol @paul @fediversereport @fediversenews @Bluedepth @darren @juneussell @volkris @davetroy Sorry, I didn't see this at first.

Relays are mainly to merge participating instances' Local Timelines into each one's Federated Timeline, in addition to the posts coming in through normal remote follows, which also helps to fill trending tags. It's a good way to make those discovery features more useful in a group of smaller instances with similar topics, but I'm pretty sure they always increase...

13 Mar 2023 at 0:09 | Open on tiggi.es
Go Up