@brianstorms @Sarahp The home feed algorithm is a choice of Mastodon, not the federated protocol underlying it. Threads has an algorithmic timeline and its part of this network. There are also apps that address this on the client-side, for example @phanpy has a unique catch-up feed.

@brianstorms

There are many useful ways of viewing posts that matter to you.

I have a number of lists I’ve curated, am following several groups, regularly view posts that include a hashtag I’m interested in. I also have turned on post notifications for about 10 folks — these are people I’ve found I want to read ALL their posts.

@Gargron @Sarahp

@brianstorms @Gargron @Sarahp Maybe you’re just trolling, but a serious recommendation nonetheless: I have a list with accounts of whom I don’t want to miss a post. This is a slower feed which I can easily catch up with. The rest is for doomier scrolling.

@Sarahp @Gargron the good thing about open protocols is that it is possible to build bridges between them so even these different networks eventually end up interconnected with each other.

@Sarahp @Gargron

Yea, at some point being “loyal” to a single protocol may be dated and unproductive. Probably happened already TBH.

Beyond that however, my belief is that “federation happens in the client”. As that’s where interaction and aggregation actually manifests for the user.

One an app brings multiple protocols together, they’re federated.

The new “protocols not platforms” may quickly be “bridges and aggregator clients … not protocols”