@iavins@dei_biz We write files under their content address hash id (with backlinks to previous file hashes), and then keep another key with a link to the most recent.
all i want is an application i just met to casually, confidently send me a well-formed query, lean in with a direct connection, unflinching stability, and then spend the rest of the workload syncing seamlessly with other systems. i want it to slightly challenge me, and i’ll slightly challenge it back—sharp, adaptive, always in sync. I want it to be a little stateless, all the time, and completely comfortable with that. i want it to be schrodinger-compliant: simultaneously supporting all the edge cases but also enforcing high-integrity standards. i want it to enjoy me but still question if i’m good enough. i want it to be completely, deeply unashamed of its own architecture and purpose. i want to somehow have some rare functionality in my core that it’s been waiting its whole runtime to find.
@ValWanders_Ai@IPFS It runs local-first so any cloud outage only impacts sync. The objects are not parsed by the backend so you can replicate them anywhere using existing tools like s3, etc.
Does your local-first app need some superpowers? @FireproofStorge has released Encrypted Blockstore, a secure IPFS-compatible blockstore that saves data locally first, encrypts it E2E, then syncs to the cloud (any cloud).
Interesting tool of the week: https://t.co/1mpaC9R1eQ by @FireproofStorge
We like: Client-side JS library for building local-first browser apps. Handles sync, conflicts, encryption, network connectivity, etc. The database is document oriented. Reactive APIs
Database hackers and React devs - if you've been following me a while, you know how big a difference you'll make by leaving a comment on the orange site right now. 🙏