Thread

Replies (48)

When you initially released bitchat on the App Store and I downloaded it, I was immediately able to find the <slap with a large trout> command. Now I canโ€™t find it anymore. I guess Iโ€™ve lost my bitchat intuition. Is it because Iโ€™m alone (slapping myself silly)? Pls help. Also, could we possibly slap others with other types of fishes such as snapper or tuna? Maybe salmon. Thanks.
When will you stop pushing unsafe tech? New Vulnerabilities: In 2025, several new vulnerabilities have been reported, including: CVE-2025-32875: Insufficient authentication during Bluetooth binding, allowing unauthorized devices to connect during initial setup. CVE-2025-32876: Weakness in the encryption process during Bluetooth handshakes, particularly in certain Android environments. CVE-2025-44559: A Denial of Service (DoS) vulnerability in the Bluetooth Low Energy (BLE) stack, allowing attackers to disrupt services by sending crafted packets.
It would be super cool if you had the balls to say something about what is going on with girls and cameras and bcis and how I can never have anything in my life for Arielle to have fun with my body and life at my own expense around the country and above the law in constant isolation because sheโ€™s psychotic psychotically obsessed with women and trying to start a mass shooting and ditch town @jack
I asked 5 Thinking (rarely use) bout spam optimal solution, itโ€™s funny cause it goes through your GitHub stuff when reasoning that is way over my head. Cute that it does that. This is what it said: Today(no code) -use password channels for real conversations (interesting but like Iโ€™m sure spam will keep getting access to unless changed daily, maybe tire it out :) -Use built-in/block @name for obvious spam and keep local blocklists. Building tomorrow -layer 1: simple flood & duplicate control with token-bucket rate limits and as mesh already uses TTL routing, in busy venues, reduce hop TTL to shrink the attack surface. Layer 2: -Require tiny POW per public message. Layer3: -Per-key trust scores, new keys start in probation(slow rate) and include relay policy where nodes deprioritise or refuse to forward from low-reputation keys (oof hope thatโ€™s not my key) Layer 4 -First-time posters must complete in-room handshake ๐Ÿค like your QR idea or get a trust reaction from non-newbie before normal rates apply. -Invite links for channels with password + short-lived QR code for events. Layer 5 -ship a tiny Core ML text model to score spammy patterns which works for offline damping of bots (be interesting if you can get this embedded into iOS bitchat app) How to geohash without doxxing: -Channel geofence where rooms require senders to be inside target geohash cell (e.g., precision 6 โ‰ˆ ~1km, 7 โ‰ˆ ~150-200 m) -witness attestations from nearby devices with truncated geohash, not raw coordinates. -pop-up room with rotating QR or 6 digit code as proximity ticket, first time posters scan or enter, afterward post for grace period 24hr. Ok, well thatโ€™s it from me, hope it helps. P.S. I swear I am not spam. Cc @calle