Just one more centralized service bro, just one more single-source unmodifiable app bro, just one more monolithic server farm operated in secret by a single corporation bro, this time we'll get it right bro...
With bittorrent v2, the division between bittorrent and other protocols is very very thin indeed, but as @aud said the other day, "true bittorrent has never been tried" - it got spec'd and then we never really used the cool things it can do
We've got a new release of #agregore with improvements to "reader mode" and a new "View history" page!
I ended up fixing the "reader mode" and adding a "view history page" with the option to delete.
Next time I'll be focused on agregore-mobile. I made some progress last month on getting "bare" running so now I need to port the protocol handler code to it and then embed it as a daemon in the chromium code the way we did for IPFS via golang.
K, I'm gonna work on #agregore for a bit. Not sure what to prioritize since there's a lot of TODOs
Feel free to vote on anything you think I should focus on. OR link to the github issue in this thread.
Streamx is a cool library but the documentation skipps a bunch of important details. It'd be nice if the docs were more comprehensive, but at least I can read the source code to see what's "actually" true
Ahhhhh. Simulating network failures with precise timing is such a pain in the ass.
I need to simulate sending data, it being queued up in the TCP buffer and the connection dying before the buffer is flushed. In Node.js 😭 Pausing transform streams doesn't seem to do the trick. Might have better luck with a funky duplex.
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.