4 ms·
Dat/Beaker Browser and many others can do all you described. They're just not popular because only us geeks care or understand the value of esoteric and worthl
by brokenmachine 7y ago
Dat/Beaker Browser and many others can do all you described.
They're just not popular because only us geeks care or understand the value of esoteric and worthless stuff like privacy and data ownership.
Also, unfortunately if someone shares a photo and then turns their computer off, the recipients then can't download the photo. If you share a photo from your phone, then accidentally drop it into the toilet, the recipients then can't download the photo. Those are inconveniences.
The popularity of facebook despite it's innate, deep-rooted and well-publicized privacy horrors makes it obvious that convenience and inertia always wins.
So the geeks need to produce something compelling that includes privacy and decentralization at its core, and only then will people switch. Pretty please?
- mceachen 7y agoOK, so I'm working on something that could be like that, and looked at dat and ipfs, but only IPFS is reasonable for filesystem access, and both have decidedly nontrivial access latency. DAT/IPFS experts: how would you apply it to something like a Google photos app, where the majority of assets are private, and subsets of assets are shared? How do you propagate edits (like adding and removing assets or changing asset metadata, like "hidden" or reactions) with reasonable propagation assurances?