back up dat thang

breaking out of Node-JS jail and enabling both C and Scheme env

dis 
dat://59d8099399510e23a3c693fb5887b7bba1586f4117f7ef1c5872622ada0c1181

be aware: seeding this may publicly expose your IP and the old tools are unmaintained

you might discuss here 

cabal://cf2caf3a1c4fd299471d315416b6cc3d9c5f7c678046652fb70ede4ff16698db

hosted on the web at 
(prev) https://git.worlio.com/divorce/dat-thang/
https://git.canithesis.org/divorce/dat-thang

BUILD
x86_64 GNU/Linux
see INSTALL

DESCRIPTION
i implement the SLEEP spec as a C header (similar to REST with HTML)
then i provide FFI bindings so you can call easily from scheme
i also have a novel solution for hyperswarm-dht (i think)

this is pre-alpha prototype-level software

what this means and what this does:
here be a p2p program that does away with the client-server model,
and enables you to basically share any directory in your system as a torrent (basically esentially)

the 'thang' part is the client, a mashup between AIM, Kazaa, and Impulsetracker
right now trying SDL2

dat-thang currently supports serving html, addressing different versions of archives, integration with the dillo browser

'cable' is a C port of cabal-cli, there is an experimental feature of sharing voice and video, which can be turned off with compile flags.

"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.

LICENSE
see LICENSE

This is My Software