Paul Frazee

Multi-author (aka Multiwriter) will solve this problem. Rather than copying private keys between your devices, you'll add each device as an owner over the dats. That way corruptions cant occur...

@DougAnderson444 That initial tech demo has been iterated a lot since then. There's going to be a string of tech updates over the next 6 months, and I expect multiwriter...

@DougAnderson444 It's a tricky situation. You need to avoid writing from 2 places at once, and if you restore from backups you risk overwriting history if your data isn't 100%...

@alexindigo It would make a lot of sense to appoint backup nodes (home devices, cloud services, etc) which you can restore from. They would ensure you refetch all of the...

@alexindigo I don't think what I described runs counter to that. So long as you can fetch the latest state of the dat and restore the private key on your...

@krisradio We don't have an official process because currently the protocol doesn't support writes from 2 different devices. There's a chance you can corrupt the data if that happens, so...

It does support symlinks, but it's saying there's a "loop" which means you have a symlink that's leading back to itself somehow and could potentially go infinitely

The 0.8.x branch is getting replaced with 1.0 very soon. We moved from the "dat protocol" to an updated replacement (same team) called the "hyper protocol." We released the 1.0...

Sorry for the delayed response, I declared inbox bankruptcy for a couple months while we finished 1.0. And huh, wow, that's a really odd bug. I haven't seen anything like...

@metanomial Some of your observations about the import issue aside (fair point, we'll need to discuss) this is ultimately a question about whether a browser is also an applications platform....