socket VS corrosion

we're working toward this with Socket runtime (https://github.com/socketsupply/socket).

Our ultimate goal is to provide a web browser-compatible environment (for quickly building UIs) with a state of the art P2P protocol — A DTN design that is fault and partition tolerant, with comprehensive and complete NAT traversal, without any server or cloud infrastructure requirements from the user — lowering the technical and monetary barriers for distributing and parallelizing work beyond the cloud.

if you're looking for an easier way to build p2p applications, you might be interested in the Socket runtime (https://github.com/socketsupply/socket)

How easy would it be to make a Socket-based GUI program, stick it on a thumb drive and run it on a friend's PC?

The Distribution Guide (https://socketsupply.co/guides/#distribution-guide) has instructions for code signing on Apple platforms, but I'm curious about the "weekend project" angle. Like, does `ssc` produce exe, apk? Could I use it to make a self-contained app that can launch without installation on Linux?

Definitely check out SocketSupply! https://socketsupply.co/guides/#p2p-guide

There is a brand new one called Socket, it’s more targeted at web developers - no rust or anything required. Backend is also completely optional. It supports all mobile and desktop — it will ship a stable release next month: https://github.com/socketsupply/socket

Their client application (written in Go) is open source: https://github.com/superfly/flyctl

They have a few other notable open source components, I think these two are particularly interesting:

- https://github.com/superfly/corrosion

- https://github.com/superfly/litefs

(Disclosure: they sponsor some of my work.)

https://community.fly.io/t/reliability-its-not-great/11253

https://github.com/superfly/corrosion

Couchdb/pouchdb remains one of the best: it's super easy to setup and is production-ready, but it's gonna be json docs with no transactions, so it can be limiting.

Y.js and automerge emerged as solutions combining CRDTs and content transfer, they look really promising. There is a Y.rs version if that's better for you.

I've always dreamt of building something on top of Syncthing, ie something that would use file synchronization. It's more versatile and will definitely last longer than anything else, and it has some built-in capabilities for having a third party helping transport but not being allowed to read content.

I recently came across https://github.com/superfly/corrosion , a service discovery and state management tool that is working completely p2p. CR-SQLite, in particular, allows multiple tables from multiple databases to be merged thanks to CRDTs. I'm sure there's a lot to build on top of it.

I feel like you're not really interested in full p2p but want some centralization point to manage some auth stuff, so I'd investigate couchdb/pouchdb first.

Any thoughts here on Fly's Corrosion? https://github.com/superfly/corrosion

We’re using cr-sqlite as part of our distributed state propagation system. It is indeed easy to bundle in the app!

https://github.com/superfly/corrosion

It would be possible to distribute cr-sqlite changes in many different ways (like you said, http or torrents, etc.) since any change can be applied out of order.