Multiwriter Dat could power the next Web (Video + blog post)
https://ar.al/2018/08/04/multiwriter-dat-could-power-the-next-web/ …
#ethicaltechnology #peerwebpic.twitter.com/fxBlYkencg
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I haven't looked into that code yet byt, when I was planning on rolling my own in the same vein, I was going to handle authorisation by signing the public key into the DAG as a special authorization operation node. Deauthorisation would similarly have a special node…
… I'm assuming multi-writer Dat is using a similar scheme but I'll find out exactly how they're doing it.
Right, it's as I'd said (& documented in the HyperDB architecture document):https://github.com/mafintosh/hyperdb/blob/master/ARCHITECTURE.md#authorization …
Ah, thanks, that's a good read. Seems a bit similar to my design, but without the 'reconcile' step - how does it ensure that all the entries remain perpetually available? It seems to me like a lost entry could result in an entire branch becoming inaccessible.
Also, it seems like it requires on a protocol level that the full history of every hypercore is kept around in perpetuity? Or am I misunderstanding it?
As far as I understand that is a feature/limitation of the design. You should be able to tombstone content but I don't see how you could ensure authorisation without the full DAG. The protocol itself supports sparse data and metadata. I'm still very new to Dat myself, btw.
I see, thanks for the commentary :) I'll have a closer look into it some time soon, in particular to see whether the availability properties are better than those of the overlay-and-reconcile model...
Look forward to seeing what you're working on too btw :)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.