5 ms·
Can't we host EasyList somewhere safer?
by rnhmjoj 9y ago
Can't we host EasyList somewhere safer?
- koolba 9y agoInternational safe zone or something distributed like IPFS?
- brador 9y agoBlockchain would be great for this.
- jethro_tell 9y agowhat would block chain give that git wouldn't? Wouldn't anyone beable to remove a domain or add a domain.
- stale2002 9y agoNo, you just have a hash of the "official" version of the list. And when the list needs to be updated, the person with the private key publishes a new list again. The advantage of using the bitcoin blockchain, for example, is that it can't be censored. DMCA trolls now have to go after every single bitcoin company in the world, to stop them from "hosting" the copyrighted work.
- jethro_tell 9y agoWhy would they not go after the guy with the private key? Any way he can escape that so could git.
- brador 9y agoPermanence. The lists would be blockchain addresses that you compile locally into the blocking list.
- jethro_tell 9y agoPerminance is not a great thing for a blacklist. Spamand ads is complicated stuff. There are false positives, and abuse.
- Kubuxu 9y agoIPFS dev here. We are quite close to having git being hosted directly on IPFS/IPLD. Things like pushing and cloning work. Example workflow: git push ipld:: <prints out CID of that commit which has 1:1 mapping to hash of the commit> git pull ipld::$CID <or> git clone ipld::$CID Important fact is: the git objects are stored in native git format. Hashes are the same, but are pretended with CID header (content identifier) which tells IPFS how to understand links and content of this object. We plan to work on remotes in close future. There is one more issue where our measure of DoS protection causes that repos with files bigger than 1MiB+ (or 2MiB, I can't recall) can't be fetched. It will be a bit harder to fix but I know we can do it.