11–20 of 45 posts
Earlier quoted context omitted.
Using its own blockchain as a ledger and a DHT network as a storage layer
Are the git objects themselves stored in the DHT, or is it just (like a trackerless torrent) the connection information needed to find peers willing to send you those objects?
Earlier quoted context omitted.
Are the git objects themselves stored in the DHT, or is it just (like a trackerless torrent) the connection information needed to find peers willing to send you those objects?
The object themselves are stored across the peers, not the connection information.
Earlier quoted context omitted.
Are the git objects themselves stored in the DHT, or is it just (like a trackerless torrent) the connection information needed to find peers willing to send you those objects?
The object themselves are stored across the peers, not the connection information.
I like more-decentralized Git, but I don't think this is necessarily the way to do it. The main problems today include plumbing around decentralized issue tracking and wikis, good Git web interfaces, etc.. Better P2P might make forking easier without centralization (Gittorrent?), but most serious projects probably won't find it difficult to obtain a VPS; data integrity and distributed authority, things the blockchain provides, are not really necessary at all.
Cloning something like Chromium or Linux is already a multi-gigabyte affair without needing everyone to download everything ever committed to the system... and what happens when code needs to be taken down for copyright reasons? I like more-decentralized Git, but I don't think this is necessarily the way to do it. The main problems today include plumbing around decentralized issue tracking and wikis, good Git web int…
Earlier quoted context omitted.
The object themselves are stored across the peers, not the connection information.
What prevents someone from using this to store backups of their harddrives, photos, etc, and consuming as much space as possible?
Earlier quoted context omitted.
What prevents someone from using this to store backups of their harddrives, photos, etc, and consuming as much space as possible?
It needs an incentive model, like for every GB of space you provide you get a GB of space from peers.
Cloning something like Chromium or Linux is already a multi-gigabyte affair without needing everyone to download everything ever committed to the system... and what happens when code needs to be taken down for copyright reasons? I like more-decentralized Git, but I don't think this is necessarily the way to do it. The main problems today include plumbing around decentralized issue tracking and wikis, good Git web int…
That code can't be taken down for "copyright reasons" is a feature in my eyes, not a flaw. The best way to stand up to censorship and legal threats is to really not be able to comply, just like the best defense against torture is not to know (and much more so if your would-be agressors have a way of being sure you really don't know, and technology can do that against censorship.)
Earlier quoted context omitted.
That code can't be taken down for "copyright reasons" is a feature in my eyes, not a flaw. The best way to stand up to censorship and legal threats is to really not be able to comply, just like the best defense against torture is not to know (and much more so if your would-be agressors have a way of being sure you really don't know, and technology can do that against censorship.)
Just turns out to be a huge drag when secrets get accidentally committed to the swarm.
Technically it's much much different of course, but if you commit some private keys/etc to Github, you have to invalidate everything used and assume that someone saw it, Google saw it, and it's cached in multiple places. Right?
Cloning something like Chromium or Linux is already a multi-gigabyte affair without needing everyone to download everything ever committed to the system... and what happens when code needs to be taken down for copyright reasons? I like more-decentralized Git, but I don't think this is necessarily the way to do it. The main problems today include plumbing around decentralized issue tracking and wikis, good Git web int…
These are new things we can do with the logical/mathematical system. As of now, the best application may not have been found. Saying how these new discoveries are 'not useful' sort of confuses the spirit of exploration.