3 ms·
This is an interesting idea. The way the commands look like filesystems makes me wonder how hard it would be to make a FUSE filesystem for contacts based on thi
by jeroenhd 5y ago
This is an interesting idea. The way the commands look like filesystems makes me wonder how hard it would be to make a FUSE filesystem for contacts based on this premise.
One "mount -t contactsfs contacts ~/contacts" and you could literally treat your contacts as files!
What I don't like about programs like this is that they often don't respect the XDG folder configuration, resorting to ~/.pplconfig and ./.ppl/config for default configuration paths. I've already went through all the stupid dotfiles in my home directory once, moving as many as I could, and I'm not going through all that effort again.
- KMnO4 5y agoApart from a neat toy project, what benefit would “contactfs” have over just storing text files in ~/contacts?
- tomcooks 5y agoPeople could share identities as files, have public keys and contact infos, or maybe even content? Would that count as distributed social network? It would work really well with mobile
- tyingq 5y agoWas that a gentle hint regarding vcard? https://datatracker.ietf.org/doc/html/rfc6350 https://datatracker.ietf.org/doc/html/rfc6350
- mbreese 5y agoI want to say that BeOS did this back in the day. I don’t think it was specifically a FUSE mount, but rather that the contacts application read vcards (or something similar) stored as plain files in the file system. Then the Contacts app just needed to be pointed to the proper folder and it would work. I definitely remember the email application working that way, but think contacts worked that way too. It was quite a clever way of interacting with your system. Everything was still a file, but your client applications were a bit more clever in how they interacted with those individual files. It was very close to the file system as a DB concept that was popular at the time, but far more practical.