31–40 of 501 posts
I wonder if you can tail a file, to create an ad-hoc encrypted messaging channel like: Read your messages: tail -f /keybase/private/yourname/inbox.log Send a message to someone: echo 'Hi, friend!' >> /keybase/private/yourfriend/inbox.log And I wonder how it handles filename collisions? Guess I'm going to need to play with this a bit later. :)
As for collisions, a "conflict" is handled as you would expect on file syncing services, although all conflict resolution has to be done by the clients! (Even in the unencrypted public folders, the resolution of the conflict has to be signed. And in the encrypted case, obviously the server has no idea.) This is one of the many things that had made KBFS a large and interesting project.
If you really wanted to use KBFS as a transport layer, you could avoid the conflict entirely by each device claiming a file to write to, and each one in a folder can monitor the others' files.
Plenty of invites over here if anyone would like one https://keybase.io/simonjgreen EDIT: all gone for now, but see https://news.ycombinator.com/item?id=11037629 for more
Plenty of invites over here if anyone would like one https://keybase.io/simonjgreen EDIT: all gone for now, but see https://news.ycombinator.com/item?id=11037629 for more
robinlambertz+dev at gmail
WOW: That happened fast, I'm all out of invites now... 2 minutes after posting emails started coming in and within 3 minutes I was out. Sorry if you didn't get one...
Plenty of invites over here if anyone would like one https://keybase.io/simonjgreen EDIT: all gone for now, but see https://news.ycombinator.com/item?id=11037629 for more
Edit: brennan at umanwizard dot com