For anyone who cares, the reason I a argue for a sovereign e2ee filesystem, is because that is the only thing we can make interoperable between apps... just like POSIX and files in general are the only interoperability success story in history. What I consider feasible is taking that and make it Web native without getting locked in platforms like Google Drive. Once that is in place, let the best app developer win, and if one file format becomes very useful, we reverse engineer it like we always do, like interoperability always worked; forcefully.

أصلا عادي

Let's start ove, and start small, from the minimum viable digital sovereignty and grow from there, worst case scenario we achieve something really good but not popular... Social media is an all or nothing, when it fails to take off, it crashes and burns, with absolutely nothing left standing. Let's ratchet progress on digital sovereignty, we already have miraculous foundations (Bitcoin, Mainline, and Cryptrees) all of which was invented around the same time for some reason! It is our turn to make the new wave of tech and products, and we should build them with soundness and care, that they can germinate and survive to be passed on to the next generation, even if this one simply never gave a fuck.

By the end of this month I should have the first usuable implementation of Cryptree in Rust, as a crate abstract enough to be used by anyone ... then I will go hard on the opinionated layer; identity, key management, host api etc. #Mlkut

You can always open

Pkarr Relay

to check on Mainline DHT and see an estimate of the current nodes count, it makes me smile usually.

If you were using Github as an alternative to Google Drive or Proton Drive, would you miss being able to grant access to subfolders and files? Or is the coarse access control by Repository enough for your needs? What if Github can let you share single files in private Repositories? Would you still wish for sharing subfolders too?