I like to build things. github.com/grjte
- Tweets 70
- Following 140
- Followers 606
- Likes 192
🧵 Could Bitchat have 5x the range and 100x the throughput for the same power expenditure? I explored how Wi-Fi Aware could improve the reliability and throughput of Bitchat and mobile ad-hoc networks in the absence of internet connectivity. #bitchat
👇
2
3
12
2,356
6/ Wi-Fi Aware would complement BLE as a secondary transport to boost connectivity or enable high-throughput direct messaging. BLE provides a backbone for a ubiquitous baseline mesh. Wi-Fi Aware enables extended range and higher-bandwidth hops when devices both support it.
1
1
213
7/ Check out the details, including a deeper discussion of challenges, a prototype of Bitchat over Wi-Fi Aware, and general notes on cross-platform Wi-Fi Aware implementation
👉 grjte.sh/bitchat-wifi-aware
1
177
I had a great time on @zeroknowledgefm chatting about local-first and emerging use cases for prog crypto. Thanks to @AnnaRRose @nico_mnbl and @goblinoats! Also to Brooklyn Zelenka & @alex_jg for useful & interesting discussions beforehand. I'm excited for more exploration here 🚀
🎙️This week @AnnaRRose and @nico_mnbl chat with @goblinoats from @TonkLabs and @grjte from @BainCapCrypto about local first architecture. They discuss CRDTs, data sovereignty, sync servers, and how ZK shows up in local-first systems.
zeroknowledge.fm/podcast/367
1
3
23
2,921
🧵 The AT Protocol shows the power of a personal data store. All of our public atproto data is easy to find and access. We can interact with it flexibly in myriad ways and combinations.
Wouldn't it be nice to do the same for our private and collaborative data? 👇
1
5
17
1,817
8/
Because your apps are local-first, the user-centric data repo that your personal sync server provides is portable, just like your atproto identity. Update the location of your PSS, and your local-first data will sync in the new data store as you continue to use your apps.
1
3
420
9/
A personal sync server acts as your local-first PDS, offering local-first benefits—like offline access, data ownership, and multi-device support—while enabling the interoperability and flexibility of the AT Protocol.
👉 Read more: whtwnd.com/grjte.sh/3lne2va6…
5
300
🧵 The AT Protocol (atproto), which underlies Bluesky, lets us to interface with the same data in as many ways as we can conceive of through AppViews that each provide a different "view" of the network.
Can we make our local-first software as interoperable as the AT Protocol? 👇
1
3
8
872
8/ Second: local-first software applications can provide multiple AppViews for private data that never gets published. By using shared lexicons and data, independent local-first applications can smoothly interoperate, easily understand data sets, and modify them correctly.
1
3
248
9/ Combining atproto's Lexicon schema system with local-first software offers a lightweight way to unlock interoperability. If you're interested in these ideas or working on similar ones, I'd love to hear from you.
👉 Read the post: whtwnd.com/grjte.sh/3lndyhyv…
3
187