3 ms·

I've been working on 2. since January. All your photos, chats, e-mails, messages, health data (eventually all your data) into a single database, which can be

I've been working on 2. since January. All your photos, chats, e-mails, messages, health data (eventually all your data) into a single database, which can be distributed onto multiple removable 'volumes' (disks). Plug in the volume and the db index is seamlessly merged and queries run on all the connected volumes. No files. No cloud. Data on your disks only. There are processing nodes that run in the background indexing the content, finding people and locations in the pictures, chats. It allows you to build up a fully search-able archive of all your data, which you can physically keep in a locker or safe. But also, if you store and keep all your data on disks that you control, then many of the services that we use could just run as local apps on your server, reading and writing from your archive via an API. Social apps are just two people's archives sharing content between each other, no 3rd party services required. I worked a lot on it until about 1.5 months ago, when I got discouraged by how hard and big this project is. Breaking up with my girlfriend around that time did not help either. But now I see you mention it and it's kind of inspiring, since I've been doing a lot of thinking and gathering strength for another crack at getting a prototype out. It would be interesting to see what other people have been thinking/doing in this area. But since there's at least one person who wants it, I might actually jump back to work ;) Thank you !

dcz_self 5y ago
Do you have any writeups/examples in the public? I am on purpose not addressing the exchange of information between people – never considered it, no vision, would just confuse me. I'm also not so keen on indexing. I'm envisioning this more as a file system layer, where data is added to the database as it gets saved. Ideally there would be no way to access the data outside of the database (that would cause desyncs and the need to reindex stuff). We don't need no POSIX file systems ;)
aydwi 5y ago
I can empathize with this to some extent. I realized that homebrew is too slow and bloaty for me, so I decided to write an alternative from scratch (also meant as a learning project). Eventually got discouraged by the sheer amount of real-world workarounds and corner cases that need to be accomodated rather than some inexplicable technical hurdle. And broke up with my long-time girlfriend. Now I have little desire to go back, and things just feel meh. I play basketball sometimes to keep my sanity.

dcz_self 5y ago

Do you have any writeups/examples in the public? I am on purpose not addressing the exchange of information between people – never considered it, no vision, would just confuse me. I'm also not so keen on indexing. I'm envisioning this more as a file system layer, where data is added to the database as it gets saved. Ideally there would be no way to access the data outside of the database (that would cause desyncs and the need to reindex stuff). We don't need no POSIX file systems ;)

aydwi 5y ago

I can empathize with this to some extent. I realized that homebrew is too slow and bloaty for me, so I decided to write an alternative from scratch (also meant as a learning project). Eventually got discouraged by the sheer amount of real-world workarounds and corner cases that need to be accomodated rather than some inexplicable technical hurdle. And broke up with my long-time girlfriend. Now I have little desire to go back, and things just feel meh. I play basketball sometimes to keep my sanity.