grjte

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-a…

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.

🧵 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 👇

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 🚀

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/3lne2…

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.

🧵 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? 👇

@cryptobuilder_ @harrykingdon_ @ZuBerlinCity @goblinoats Benefits of local-first architecture are that apps work offline, you never have to wait for things to load (because all data is local), but you can still access across all your devices or share and collab. User control and ownership without losing the benefits of the cloud

@harrykingdon_ @ZuBerlinCity @goblinoats @grjte 😯😯 Does local first means client side? Or is it something different? What does AT stand for?

Jamming on the agenda for @ZuBerlinCity, need your opinions!! ❤️ Among the topics to be covered: - The future of zk-mpc (co-snarks): expanding to other proving systems, efficiency, applications - Risc v or not risc v (let's fight!) - Can we zk-prove LLMs? - Is iO a psyop or a magic pill? - Lattice-based snarks: design overview, performance relative to other approaches - Designing ZK-specialized hardware: what does it mean, how much does it cost, does it make any sense - ZK-VM fuzzing - Hash function security: how will we know that Poseidon is secure enough - Does zkTLS work? - PIR: current state and the way to go - Privacy: different definitions and executions - Quantum cryptography: glimpse into Among bonus sessions: - How to build open source products and not to lose all your friends? - How to stay normal while doing cryptography in crypto and living on CT? - How to propagate cryptography into the world: TikTok, technical writing, and other channels Any other currently hot topics to cover? Any particular people to invite? Am I missing some major cryptography questions?