My little girl has negative iq sometimes , not a single braincell in that cute little skull. Love her to pieces.
Other really cool #p2p things to see:
π§Composing capability security and CRDTs
https://fosdem.org/2026/schedule/event/SXSAML-brassica-chat-with-goblins-ocapn/
π’ Willow - Protocols for an uncertain future
https://fosdem.org/2026/schedule/event/CVGZAV-willow/
π¬ qaul.net - Internet Independent Wireless Mesh Communication App
https://fosdem.org/2026/schedule/event/VRTVUU-qaul-mesh-messenger-app/
π Multi-relay chat messaging & cryptographic identities with Delta Chat
https://fosdem.org/2026/schedule/event/3F9VTU-deltachat-chatmail-relays-multi-transport/
π iroh p2p connections
https://fosdem.org/2026/schedule/event/T9ACNE-iroh_p2p_connections/
π Reticulum-rs: Porting the Trustless Mesh to Rust
https://fosdem.org/2026/schedule/event/KF7STF-reticulum-rs_porting_the_trustless_mesh_from_python_to_rust/
Anyone asserting encryption is a tool for crime is either painfully misinformed or is attempting to manipulate legislators to gain oppressive power over the people.
Encryption is not a crime,
encryption is a shield.
Encryption protects you from cyberattack, identity theft, discrimination, doxxing, stalking, sexual violence, physical harm, and much more.
For safety, for privacy, for democracy, and for all our human rights, it's critical that we defend our right to encryption.
https://www.privacyguides.org/articles/2025/04/11/encryption-is-not-a-crime/
#Privacy #Encryption #DigitalRights #HumanRights #Democracy #RootForE2EE
Encryption is not a crime, encryption protects us all. Encryption, and especially end-to-end encryption, is an essential tool to protect everyone online. Attempts to undermine encryption are an attack to our fundamental right to privacy and an attack to our inherent right to security and safety.
We have a new blog post on the state of Reflection, our local-first collaborative note taking app πͺ΄βοΈ
https://modal.cx/blog/reflection-spring-update
A few highlights π§΅
My coworker and I figured out a nasty bug in our own code yesterday. It was one of those "works on my machine" situations. We ended up using some of the strategies from @b0rk 's zine, The Pocket Guide To Debugging, https://wizardzines.com/zines/debugging-guide/. We worked together, reproduced the bug, made a minimal example, identified and answered small questions, kept a log book, and analyzed the logs (a report from running the command). Eventually we solved it, and it was caused by a flawed assumption on our part.
Initially, the problem was daunting. It was involved with a tool, nuitka, that I'm not familiar with. It's a tool for compiling python applications into C and then makes a Windows exe file for running the application. It's somewhat niche, so I didn't find answers from web searches. I didn't know where to start, and things didn't make sense at all.
Having a set of strategies to fall back on was encouraging. It made the process a lot more fun too.