Thank you to everyone who came to @tabconf 7 and made it wonderful this year!
4 days of: cordial debates, technical workshops, talks and panels, interactivities, meshtastic devices, hardware hacking, the CTB puzzle. So much fun.
7 Things I would like to share from TABConf 7.
1. Huge sponsor love for enabling our grants and supporting the conf: @lclhostresearch@HRF@SetDevBTC BitcoinTutorials @spiralbtc@FulgurVentures@unchained@jintekc@fedibtc@andurobtc@CleanSpark_Inc@lightspark DCD
2. So many new faces inspired to build on Bitcoin. Special love to the Brazilian crew who also hit the Rust Bitcoin Summit at @bitcoinpark_. Shout to @lucasdcf on the great work with @Vinteum_org and @satsconf_ (Nov 7).
3. Thanks for personalized education and attention from so many talented folks especially some core contributors like @murchandamus and @achow101. And those encouraging technical education with a carrot 🥕 via CTB donors, you rock!: @jintekc@fedibtc@bitcoin_bugle@AnchorWatch@TaprootWizards.
4. Adhoc and satellite events and activities were a blast: @StephenDeLorme@atlbitlab 👷🧑🏭💃 @ShellyLegit@isabelfoxenduke Afterparties 🥳 @D_plus__plus Mario Kart Double Sats 🚗 @niftynei Bitcoin at work-shop. The chess tournament crew: @jondomedia@bitcoinpartykc@bitcoinburnbabe. ♟️
5. Massive thanks to @AEHW1@CryptoDoc20@briimhd Brandon @exfrog @_AlexLewin and all volunteers for setup and breakdown in record time.
@lclhostresearch crushed the Socratic BitDevs village as always. Hardcore trivia was amazing and super efficient.
6. Debate panels drew big crowds again. Year 2 of the format and going strong. Thanks @Truthcoin and @cryptoquick for setting context and involving the audience.
7. The warnet hosted by Zipkin was awesome. Big shout to @ChaincodeLabs for supporting it the last 2 years. Hacking LN ⚡️⚠️ nodes was a blast. Our evening WoT with @ChristopherA 🔐workshop sparked ideas for recurring web of trust events at TAB.
I cannot wait to see you all next year for TABConf 8. Tickets are on sale now at early prices. Support the conference and grab yours today! Save the date: TABConf 8 is Oct 12-15, 2026. Mark your calendars! 🗓️
I’m in. Missed the last 2. Also, TVP will sponsor up to 10 students and/or people with serious project ideas who want to attend and invest time in their idea.
Michael, can you help find people who need a ticket?
Roger Dingledine, co-founder of @torproject, on why Tor was built as a non-profit, and why that structure matters for the work itself.
Privacy and anti-censorship infrastructure doesn't fit a venture-backed timeline.
The people who depend on it most can't wait two years for a project to be "profitable," and the work is rarely something a board would prioritize on a quarterly roadmap.
What sustains it is community support, public-interest funding, and structures built to put users first.
A whole ecosystem of small nonprofits has grown up around Tor, building whistleblower submission systems, secure messaging, mobile archiving, anti-censorship infrastructure, and tools for activists and journalists.
The Internet Freedom Project is built to support this ecosystem. A $115K match pool from @cakewallet, @ZcashCommGrants, @Logos_network, and @OctantApp amplifies every donation made to the ten projects below through June 18.
Support @SecureDrop, @open_archive, OnionShare, @r2refresh, @OnionBrowser, @OpenObservatory, @PasKoocheh, @unredacted_org, Miaan Group, and Osservatorio Nessuno.
https://t.co/ASpCN4Q2it
DO NOT use Telegram in sensitive applications. Telegram does not need to have its message encryption broken for users to be tracked at the network layer. Telegram sends MTProto over unencrypted TCP, exposing auth_key_id - a long-lived identifier tied to the client’s authorisation key. An ISP, hotel WiFi operator, mobile carrier, transit provider, or surveillance system on the network path can see that identifier if they can observe the traffic. It can remain stable across app restarts, IP changes, VPN use, network switches, and location changes. Secret Chats protect message content, but this leak is below that layer. That makes the attack passive. The risk is in retroactive correlation. Think a journalist using Telegram from different networks for months, then joining hotel or corporate WiFi under a real name. That one identity anchor could make old logs searchable for the same auth_key_id. The fix is simple - mandatory transport encryption for all MTProto connections, with no unencrypted fallback. Telegram chose not to do this. Source: @kaepora https://t.co/TJALYAwaOs
1/ We are sharing additional details regarding our investigation into unauthorized access to GitHub's internal repositories.
Yesterday we detected and contained a compromise of an employee device involving a poisoned VS Code extension. We removed the malicious extension version, isolated the endpoint, and began incident response immediately.
Data centers aren’t stealing your water.
Even if the total water draw of data centers triples by 2030, they’d require just 8% of the water consumed by American golf courses.
@dodgeblake interviewed @AndyMasley, the man who’s been debunking AI water doomerism. Full story 👇