danbitengo

5 ms·

1.
Time, Clocks, and the Ordering of Events in a Distributed System (1978) [pdf](lamport.azurewebsites.net)
1 points by danbitengo 7d ago|0 comments
2.
Static Evaluation of Model Switching in LLM Agents Scores the Wrong World(arxiv.org)
4 points by danbitengo 17d ago|0 comments
3.
The Art of the Fugue: Minimizing Interleaving in Collaborative Text Editing(arxiv.org)
3 points by danbitengo 26d ago|0 comments
4.
Understanding operational 5G: a first measurement study (2020)(blog.acolyer.org)
1 points by danbitengo 1mo ago|0 comments
5.
Manta: Network Topology Adaptation for Self-Evolving Multi-Agent Systems(arxiv.org)
2 points by danbitengo 2mo ago|0 comments
6.
by danbitengo 7mo ago
AI agents are taking real actions — deleting files, sending emails, merging code. When something goes wrong, the question is always: did a human actually authorize that, and can you prove it? Oath is an open protocol for cryptographically s
7.
Show HN: Oath – prove a human authorized each action before your AI agent acts(github.com)
1 points by danbitengo 7mo ago|2 comments
8.
by danbitengo 7mo ago
Try it now: https://localwrite-demo.fly.dev Open in two tabs, join a room, start typing. That's the pitch. SyncKit is an offline-first sync engine. Rust core compiled to WASM, TypeScript SDK, works in any framework. What&#x
9.
Show HN: SyncKit – Open two browser tabs and watch CRDTs sync in real-time(github.com)
4 points by danbitengo 7mo ago|1 comments
10.
by danbitengo 9mo ago
Hey HN, I'm Daniel, creator of SyncKit. I've been obsessed with the Ink & Switch "Local-First Software" vision for some time now—apps that work offline, feel instant, and give users control of their data. But every t
11.
Show HN: SyncKit – TLA+ verified CRDT for local-first apps (zero unsafe Rust)(github.com)
2 points by danbitengo 9mo ago|1 comments
12.
by danbitengo 10mo ago
That's a fair point. The description does assume some familiarity with local-first patterns. I'll think about how to make the "why you'd want this" clearer for people outside that space. I appreciate the honest feed
13.
by danbitengo 10mo ago
That's actually a really cool idea! Notes are just documents, so the sync model would work well. Hadn't thought about Obsidian specifically but I like it.
14.
by danbitengo 10mo ago
For P2P multiplayer with Svelte/SolidJS, SyncKit might not be your best fit because: - It's client-server (not P2P) - No Svelte adapters yet (coming in v0.2.0) - Multiplayer games usually need P2P for lower latency Better options
15.
by danbitengo 10mo ago
You've hit on the core limitation because SyncKit has the same issue. Document/key-value like Loro and Yjs. The relational model problem is fundamental to CRDTs. They guarantee conflict-free convergence because documents are indep
16.
by danbitengo 10mo ago
I appreciate the enthusiasm! And yeah, I'm planning to start blogging about the build process and some of the technical decisions probably after launch week settles down. I'll post about it on LinkedIn and in the GitHub Discussion
17.
by danbitengo 10mo ago
See my response to skybrian above. You're both asking the same good question about the LWW messaging. Short version: system-level guarantees, not user-level concurrent edit preservation.
18.
by danbitengo 10mo ago
That's a great suggestion. The memory benchmark being buried is a fair point. I'll move it up top and create a proper benchmarks.md page. Thanks for the detailed feedback.
19.
by danbitengo 10mo ago
I haven't tried InstantDB yet, but it looks really interesting. Thanks for the pointer! Will definitely check it out.
20.
by danbitengo 10mo ago
You're right that this is confusing. "Zero data loss" means system-level guarantees (no corruption from network failures, crashes, etc), not that concurrent edits to the same field are preserved. LWW definitely clobbers one o
21.
by danbitengo 10mo ago
Thanks! For native Android, not directly yet because v0.1.0 is Rust → WASM → TypeScript (web/Node/Deno/Bun). But since the core sync engine is pure Rust, native Android bindings are definitely possible. The main paths would b
22.
by danbitengo 10mo ago
Thanks! The TLA+ modeling actually caught 3 bugs even before I wrote any code. Worth the upfront investment. It's way easier to debug a state machine model than distributed sync logic. Happy to share more about the verification approac
23.
by danbitengo 10mo ago
Thanks! Yeah, Realm's shift in direction left a gap in the offline-first space. I didn't build Dart bindings yet (Rust → WASM → TypeScript for v0.1.0), but since the core is in Rust, Dart bindings via dart_rust_bridge are definite
24.
by danbitengo 10mo ago
Not yet, but it's definitely something I'm considering. Right now v0.1.0 is React (web) only. I'm planning Vue/Svelte for v0.2.0, and React Native could absolutely be v0.3.0 or sooner if there's demand. The nice thi
25.
by danbitengo 10mo ago
Hey HN, I built SyncKit after shipping two local-first projects (RestBolt and Graft) and realizing there's no simple way to add cross-device sync. The problem: Existing solutions are either too complex (Automerge/Yjs require learn
26.
Show HN: SyncKit – Offline-first sync engine (Rust/WASM and TypeScript)(github.com)
87 points by danbitengo 10mo ago|36 comments