Fireproof 🔥

embedded document database with live sync via any backend

[Fireproof 🔥 @FireproofStorge]

Find us on @bluesky at https://t.co/lFswiEHSr7

[vibe coding ceo @jchris]

Join me and the Vibes DIY team at the @aiDotEngineer after party Friday night. RSVP: https://t.co/Gr1NKFPxBE

[Fireproof 🔥 @FireproofStorge]

Model context protocol benefits from live data https://t.co/lFswiEHSr7

[Fireproof 🔥 @FireproofStorge]

@paulgb We have a model context protocol starter thx @jimpick https://t.co/xPnesEL45d

[Paul Butler @paulgb]

You can tell sync engines are hot tech because none of the companies have pivoted to AI yet.

[Fireproof 🔥 @FireproofStorge]

I formally submit my application for the role of CEO of HTMX @htmx_org @gitpush_gitpaid

[Fireproof 🔥 @FireproofStorge]

I formally submit my application for the role of CEO of HTMX @htmx_org @gitpush_gitpaid

[Fireproof 🔥 @FireproofStorge]

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

[Fireproof 🔥 @FireproofStorge]

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.

[Fireproof 🔥 @FireproofStorge]

Great tech thread with hard questions from @pwang on #Bluesky https://t.co/yMsr8FQ7zC

[Fireproof 🔥 @FireproofStorge]

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

[IPFS @IPFS]

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

[Console - Devtools, devtools, devtools @consoledotdev]

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

[vibe coding ceo @jchris]

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

[htmx.org / C3PO of Purses (same thing) @htmx_org]

@adatta02 I think if a library surfaces a design pattern the api is probably too complicated

[ThePrimeagen @ThePrimeagen]

rolling your own auth is easier than rolling your own undo

[Fireproof 🔥 @FireproofStorge]

Web workers are the new containers https://t.co/mRfPFrT5e5

[Fireproof 🔥 @FireproofStorge]

@JungleSilicon Also in the background of our popup banner big thanks to our designer https://t.co/4KoKbhiWbn