

1·
5 months agoIdea: The ads could be marked as such by the protocol or the instance would risk detestation. Then, every other instance could choose if they show ads or not.
Idea: The ads could be marked as such by the protocol or the instance would risk detestation. Then, every other instance could choose if they show ads or not.
The authentication could be another service, split from Mastodon, Lemmy, Pixelfed, … that only gave that service. The instance asks the auth server about “user@instance: password” and the server just says “OK/fail”. That or sending the user to the auth server to get a session cookie.
“Leave that algorithm riddled platform and come to this new and shiny algorithm riddled platform” 🤦
And don’t forget Peertube already uses P2P to spread the load between the server and the viewers.
The answer, in time, is to have a P2P network of federated clients/servers.
Search for hashtags. And from that, follow people and hashtags.
Easy enough? (I hope so. I can’t explain it easier but if you need it…)