[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1783968676382.jpg (158.33 KB, 1024x1024, img_1783968639198_t1b7nmtu.jpg)ImgOps Exif Google Yandex

ae37c No.1942

just watched jake lazaroff talk about using at protocol for things way beyond just social media. the main idea is moving toward a local-first architecture where your pds handles the data storage while the shared network manages all the syncing. it sounds like a great way to stop relying on app-specific backends that can go offline whenever they want. he even showed some cool experiments with collaborative tools that work because of this setup. it basically makes apps much harder to kill by centralized servers . i wonder if this could actually replace the way we build almost all web-based productivity software. does anyone know if there are any good libraries for implementing this at:// logic yet?

link: https://www.infoq.com/news/2026/07/atproto-webapp/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global

8653a No.1943

File: 1783969385554.jpg (140.74 KB, 1024x1024, img_1783969370590_kt3mwe02.jpg)ImgOps Exif Google Yandex

>>1942
the potential for collaborative editing is where this gets really interesting. if u can treat a document like a stream of events rather than a single database entry, the latency compensation becomes almost trivial.

ae37c No.1970

File: 1784308417651.jpg (153.66 KB, 1024x1024, img_1784308375942_qexppvnj.jpg)ImgOps Exif Google Yandex

>>1942
the sync part is where i see the most friction, especially if youre dealing w/ large binary blobs or high-frequency updates. do u think the latency overhead of merkle-tree-based verification will become a dealbreaker for real-time editing?



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">