News for hackers. Stuff that matters.
Re:GitHub shouldn't allow username reuse by Klathmon on Friday February 09, 2018 @07:48PM (#16345136)
That sounds like an incredible idea!

Has anyone tried to do something like this before? I would absolutely run a torrent server to serve up my own and others' open source packages.

Re:GitHub shouldn't allow username reuse by ovao on Friday February 09, 2018 @09:21PM (#16345472)
To my knowledge it hasn’t been tried. It shouldn’t be too difficult to author a tool to do so, which could itself be made go-gettable. With this you’d avoid the mess of shipping an alternate build of the go tool and all that entails.
Re:GitHub shouldn't allow username reuse by comex on Saturday February 10, 2018 @12:03AM (#16345983)
This project was fairly close to that idea:

https://github.com/cjb/GitTorrent

I think it’s abandoned though.

Re:GitHub shouldn't allow username reuse by Klathmon on Friday February 09, 2018 @11:11PM (#16345826)
Yeah, the more I think about it the easier it seems.

You could probably write "plugins" or shims/wrappers for most package managers out there pretty easily.

And a great MVP would just be the ability to install from a magnet link.

Re:GitHub shouldn't allow username reuse by strkek on Friday February 09, 2018 @09:23PM (#16345475)
I read somewhere that big companies use BitTorrent internally to update their codebase.

But yeah, I'd really like for someone to develop a VCS like that (even more if it's in Go, with no Cgo, and under BSD, MIT or Apache license). It'd make distribution, immutability and mirroring so much easier.

Re:GitHub shouldn't allow username reuse by detaro on Saturday February 10, 2018 @06:38AM (#16346895)
There is https://github.com/whyrusleeping/gx (based on IPFS instead of torrents, but they work extremely similarly for this use case)