[tahoe-dev] filerock, SpiderOak, mega, "BitTorrent Share", Dropbox, dedupe
Tony Arcieri
tony.arcieri at gmail.com
Mon Jan 28 20:28:26 UTC 2013
- Previous message: [tahoe-dev] filerock, SpiderOak, mega, "BitTorrent Share", Dropbox, dedupe
- Next message: [tahoe-dev] filerock, SpiderOak, mega, "BitTorrent Share", Dropbox, dedupe
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Mon, Jan 28, 2013 at 9:43 AM, Zooko O'Whielacronx <zookog at gmail.com>wrote:
> It shows that there are some customers who are okay with read-cap-in-URL!
> Apparently Mega generates a URL for each file, and possession of that
> URL is sufficient to give access to that file! Maybe they learned it
> from us. I hope so.
If they learned it from you they are poor students ;) Some discussion
about that here:
https://twitter.com/CodesInChaos/status/293465296415621120
MEGA lacks Tahoe's writecaps, or any way to sign tree roots such that you
can give away a read-only cap. But yeah, looks like they have the basics of
Tahoe-style immutable files.
--
Tony Arcieri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130128/ff016351/attachment.html>
- Previous message: [tahoe-dev] filerock, SpiderOak, mega, "BitTorrent Share", Dropbox, dedupe
- Next message: [tahoe-dev] filerock, SpiderOak, mega, "BitTorrent Share", Dropbox, dedupe
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the tahoe-dev
mailing list