So today, I was coding furiously in Python, and a thought popped into my head.
This thought comes from a brief conversation that Keshl and I had had in #sabayon on the 10th of March.
[Sunday, March 10, 2013]  <Keshl> GeekSoldier: What if, we had a, a thingy. A thingy for Equo that could act as a torrent thing, and help seed/speed up updates and stuff?
[Sunday, March 10, 2013]  <Keshl> o_o
[Sunday, March 10, 2013]  <Keshl> Optional thing in client.conf, but a thing. o_o
[Sunday, March 10, 2013]  <GeekSoldier> Ooh, that would be nifty!
Yeah, like I said... brief, but today I considered it more deeply. Would this even be worth implementing into Equo? A sort of community opt-in thing to distribute package files through bittorrent? I, personally, have not had many problems with download speeds (umd.edu is very nice to me), but I'm sure that there are people who may get better results from a p2p solution than from a single server.
Also, I cannot begin to claim that I know what kind of load is put on the issues, especially on Super Saturdays, or of the potential speed gains possible. I think that in the worst cases, it would help some of our community.
I'm just asking for your thoughts on this. I'd be willing to throw my hat in the ring to help develop some of the necessary code.