Yes. The usual problems. Discovery, identity, storage.
Identity is the hardest problem. Yes, there's stuff like OpenID. But few non-programmers use it. We badly need some kind of ID system that doesn't depend
on a vendor that's in the advertising business.
Discovery is a problem mostly because Google has a monopoly in search.
The problem with federated storage is that storage is currently organized by "where", not by "what". There's the BitTorrent approach, where the address is the hash of the content.
There's IPFS, but it's 90% Make Money Fast with crypto and 10% actually storing stuff.
Whatever happened to the DOI concept?
There's distributed caching, like PeerTube, which works better. Every file has a home location, but if lots of people want something, it gets replicated. So if your cat video goes viral, your tiny server won't be overloaded. That solves the problem of popular content, but not the long tail.
And because the option to not index posts is enabled by default and a good chunk of the fediverse is opposed to indexing due to their irrational fear of bots:
Identity is the hardest problem. Yes, there's stuff like OpenID. But few non-programmers use it. We badly need some kind of ID system that doesn't depend on a vendor that's in the advertising business.
Discovery is a problem mostly because Google has a monopoly in search.
The problem with federated storage is that storage is currently organized by "where", not by "what". There's the BitTorrent approach, where the address is the hash of the content. There's IPFS, but it's 90% Make Money Fast with crypto and 10% actually storing stuff. Whatever happened to the DOI concept?
There's distributed caching, like PeerTube, which works better. Every file has a home location, but if lots of people want something, it gets replicated. So if your cat video goes viral, your tiny server won't be overloaded. That solves the problem of popular content, but not the long tail.