undefined | Better HN

0 pointsBeetleB1y ago0 comments

You can make lists in Mastodon, and put the noisy people there and exclude them from your main feed.

You can put all your Asian follows in a separate list as well if you want to quickly catch up with them.

No algorithm has its down sides, but I doubt they'll put in an algorithm that I'll like more than "no algorithm".

I'll add that I think algorithms should be the responsibility of the client, and not the server. The web client is merely one client. There's not much preventing any of the numerous other clients from implementing an algorithm.

0 comments

runako1y ago

Bluesky also has a followers feed like Mastodon. I use that one sometimes, but it's easy to toggle over to one of the algorithmic feeds as well. Sort of best of both.

Worth noting that some algorithms can be done client-side, but it may not be feasible or desirable to do so. For example in the open protocol of email, some huge majority of all mail is supposedly spam. Filtering client-side would be a tremendous waste of resources. I suspect the same could become true of any open protocol like Mastodon or AT.

Either way, I think the proliferation of sites is good for the digital ecosystem.

bigiain1y ago

> some huge majority of all mail is supposedly spam. Filtering client-side would be a tremendous waste of resources. I suspect the same could become true of any open protocol like Mastodon or AT.

I once had access to the Twitter Firehose.

It was, as you say, a mindbogglingly tremendous waste of resources.

ekianjo1y ago

The solution was always: provide several algos on top of chronological order, and let people choose.

Client side Algo cannot be implemented because the API does not give you enough controls (I know, I have written Mastodon clients)

mkl1y ago

If you can get the messages, you can run a client-side algorithm - just download everything in the last 24 hours or whatever, and algorithmically choose what to display in what order.

ekianjo1y ago

That's a huge waste of resources on the client side. If every client does that it will bring the servers to their knees.

nyclounge1y ago

While I agree with you, technically everything can be done with API, but what are the bottle neck of just have everything accessing a db table directly? Cutting out the http API middle man?

BeFlatXIII1y ago

Too much work for not enough reward.

j / k navigate · click thread line to collapse

0 comments

runako1y ago

Bluesky also has a followers feed like Mastodon. I use that one sometimes, but it's easy to toggle over to one of the algorithmic feeds as well. Sort of best of both.

Either way, I think the proliferation of sites is good for the digital ecosystem.

bigiain1y ago

> some huge majority of all mail is supposedly spam. Filtering client-side would be a tremendous waste of resources. I suspect the same could become true of any open protocol like Mastodon or AT.

I once had access to the Twitter Firehose.

It was, as you say, a mindbogglingly tremendous waste of resources.

ekianjo1y ago

The solution was always: provide several algos on top of chronological order, and let people choose.

Client side Algo cannot be implemented because the API does not give you enough controls (I know, I have written Mastodon clients)

mkl1y ago

If you can get the messages, you can run a client-side algorithm - just download everything in the last 24 hours or whatever, and algorithmically choose what to display in what order.

ekianjo1y ago

That's a huge waste of resources on the client side. If every client does that it will bring the servers to their knees.

nyclounge1y ago

While I agree with you, technically everything can be done with API, but what are the bottle neck of just have everything accessing a db table directly? Cutting out the http API middle man?

BeFlatXIII1y ago

Too much work for not enough reward.

j / k navigate · click thread line to collapse