"why? when hyper:// is here now with so cool much better justwerks dApps(Decentralized Apps)???"
I like the sound of dat:// better, this is cooler no offense, and the scope of this project is longevity and community archival.
{tw: software developer's opinion inc} you can't build community 'archival' tools on flimsy vulnerable npm install hope it works oh it doesn't its obviously not maintained... i am trying to build good minimalist software so 20, 30 years down the line, if i have the hash, i have my files (granted someone else kept them live), "boom".
"hyperswarm" sounds badass, its just what p2p need(s(ded since 201X)). i wanna be developing hyperswarm. in this implementation its called cesspool. so when people include that particular module in their distros they will package libcess. i've always wanted to write libcess and now here it is, baby.
cesspool is essentially (old) hyperswarm under the hood, in fact the only difference are the literal bytes 'cesspool' which you can change back to 'hypercore' in the NETWORK_PROTOCOL file and it (should) find peers on that network. similarly, theoretically, you can set your own to whatever and have your own network.
you're typically going to be the only people on the network, i tried to make the bootstrapping node process as easy as possible and crossplatform.
i'm using C because ez libraries, assert is the ultimate hack, and scheme because macros *shablamo* and s7 lisp-in-C because hell yeah i specialize in beautiful elegant solutions to your networking problem.
