package distribution by bittorrent

[solorin]

http://benjaminkerensa.com/2012/05/30/package-updates-over-bittorrent-protocol

[gerald_clark]

Not too practical for lots of individual small packages.

[solorin]

you're basically making the same point as the third comment down.

granted there needs to be a certain volume in some measure
before bittorrent's more apparent advantages come into play.

however,  a decentralized model empowers the community over gatekeepers.
i think that inherent advantage is enough reason to consider these technologies.

i think there's probably ways to implement this where one could kick in for the other,
under the right conditions.
or have two pieces of infrastructure in place.

for example a section of the wiki could be reserved to post torrents,
and each individual packager could provide seeding.
with DHT, i believe there doesn't even need to be a centralized tracker anywhere.

this is in off topic anyway. i just posted it to see if i could spark any imaginations.

[curaga]

Require each packager to seed = require them to be always on, and to have a fast upload connection. That would be a big hurdle IMHO, with the caps, per-mb charges and even the always-on requirement.

The main isos already have torrents, not officially posted ones but with md5sum you can be sure they're genuine. (though I don't get why, when they are both small and can max one's download by using more than one mirror and aria2).

[solorin]

this is still being locked in to thinking in a top-down centralized manner.

>Require each packager to seed = require them to be always on, and to have a fast upload >connection.

that's actually what the current system of distribution requires of it's one central node,
and what the swarm can address if properly cultivated.
but y'all know how bittorrent works, no need to rehash.

the third poster(in the article comments) and you both do make an interesting point tho. 
that the useful pieces of information shared are quite small.
whether they be the isos (small compared to other distros)
packages(many packages in the repo are quite small already).
or updates to binary packages (even smaller).
and that bittorrent traditionally makes more sense for large file transferring.
but i'm not so sure that that's a good reason to dismiss it so flippantly.

if there are enough peers sharing at any given moment, the benefits would still
be apparent - particularly if they are all trying to hit one or a small subset of mirrors
for an update. it's the size and behavior of the swarm that's actually more relevant here.

if you don't have enough sharing peers, then yes the topology will default to the central server
model. and you are left where you started as you pointed out above.
but as your network scales there should be efficiencies to be gained.

o no i've gone and rehashed bittorrent for y'all. o well.

[curaga]

Certainly it would be useful for the full repo, say monthly, given the occasional questions on how to grab everything.

But that would need a dedicated seedbox with the bandwidth to handle the multi-gb uploading.

[solorin]

this is all just whimsical musing i suppose.
probably the Core community isn't at all big enough
to realize any of those efficiencies anyway.

bittorrent is meant save the *distributor's* bandwidth.
and if ibiblio's got enough for everyone's needs then i guess there really is no
practical point.

[solorin]

i take it all back. i'm going to have to respectfully
disagree with you gentlemen.
after a more thorough reading of the thread
the debian guys seemed to have thought this out already.
and http://www.camrdale.org/apt-p2p/
does seem like an interesting solution
that could use a tinycore counterpart.
it's design pretty much alleviates the concerns brought up
and delivers the benefit's i'm advocating.

let me be clear, i'm not asking for anyone else to do anything about it

and some code from twitter in the same problem domain: https://github.com/lg/murder

[mocore]

let me be clear, i'm not asking for anyone else to do anything about it

in case it is of any interest

https://github.com/andrewchambers/magnet-linux -  decentralized linux distribution.
https://github.com/andrewchambers/magnet-linux/blob/main/mirrors/current.rec

Who should consider using magnet-linux?

Nobody yet (unless you want to participate in the design process).

[jazzbiker]

Hi mocore,

Thx for the link.