Using Tahoe-Lafs capabilities on mobile devices

[Zooko Wilcox-OHearn]

On Mon, Feb 24, 2014 at 9:35 AM, Rudenko Pavlo <9finch9 at ukr.net> wrote:
>
> My name is Pavlo and I'm a member of a team currently working on a project of Open Source P2P TV platform which is called Nebel.tv.

Welcome!

> This is p2p architecture similar to what you can find in the bittorrent but different to the extent of it application to lossy storage of media data.

It doesn't sound unreasonable to me to use Tahoe-LAFS for this.

> Using LAFS we plan to overcome "tracker node" needs: as all members of the network will become 'trackers' for their own published content as well as the content of their directly visible peers.

I think that a "tracker" (or "meta-tracker"?) in BitTorrent tells you:
for a given file which servers have part of that file. LAFS replaces
this with a decentralized "DHT-style" routing. This may be slightly
less efficient in some cases (or it may not — I haven't seen it
measured and compared), but it eliminates the need for that service
from a tracker.

Now there's another service that you need, which letting people
discover or browser content, and giving them the link to that content.
The "link" in BitTorrent would be the .torrent link or a "magnet" link
or something. The link in LAFS would be the read-cap.

Regards,

Zooko Wilcox-O'Hearn

Founder, CEO, and Customer Support Rep
https://LeastAuthority.com
Freedom matters.