Josh (Scarlett) ♿️ 🏳️‍⚧️

Just to be clear – AI did not write my post I wrote it myself and it formatted it. That was it. I had a real issue and then the AI added a bunch of bullshit that I did not want to the post and I could not delete it in time. The real issue was that passkeys were not working on Helium and I didn't know why. Then I figured out that it was because of a flag or build parameter that was mistakenly left out of newer versions of Helium. I'll include a screenshot below. Tell me I'm wrong about this real issue and not the fact that AI generated slop that I did not want it to generate.

Just to be clear – AI did not write my post I wrote it myself and it formatted it. That was it. I had a real issue and then the AI added a bunch of bullshit that I did not want to the post and I could not delete it in time. The real issue was that passkeys were not working on Helium and I didn't know why. Then I figured out that it was because of a flag or build parameter that was mistakenly left out of newer versions of Helium. I'll include a screenshot below. Tell me I'm wrong about this real issue and not the fact that AI generated slop that I did not want it to generate.

1/ Hey @uwukko @inputnet — I'm a paying Helium supporter at $50/month because I believe in what you're building. Privacy-focused browsing matters to me. So imagine my surprise when I submit a PR that fixes a real bug and you label it "AI SLOP SPAM" and lock it.

@ThreadReaderApp unroll

github.com/imputnet/heliu… @heliumbrowser 9/ I support Helium because I believe in the mission. But if this is how you treat people who pay to support you AND try to contribute real fixes, that's a problem. Not asking for an apology — asking you to look at the actual fix before writing it off.

5/ But the fix was right there in the PR. The TCC permission reset for WebBrowserPublicKeyCredential is the actual solution. You trim the extra docs, keep the fix, and move on. That's what code review is for. 6/ Instead, @wukko renamed my PR to "[AI SLOP SPAM]", and @inputnet locked it and limited conversation. No discussion. No "hey, the fix is good but strip the docs." Just torched the whole thing. 7/ I get it — AI-generated PRs are a real problem in open source. But there's a difference between drive-by slop from someone farming contributions and a paying supporter who spent days debugging a real issue and used AI as a tool to get there. 8/ The unwanted docs were noise. The fix works. You could've kept the meat and tossed the garnish. Instead you threw out the whole plate.

2/ Here's what happened: passkeys from iCloud Keychain / Apple Passwords weren't working in Helium. Not QR-based, not security keys — the ones stored in the Secure Enclave via macOS. I've been fighting this for days. 3/ I used AI to help me diagnose the issue. The fix? tccutil reset WebBrowserPublicKeyCredential net.imput.helium That's it. Passkeys work again. Real fix. Real problem. Verified on my machine. 4/ I submitted PR #185 with this fix. I'll be the first to admit — the AI went overboard and generated a bunch of README documentation and passkey guides I didn't ask for and didn't want. That's on me for not reviewing the full diff before submitting. Fair.

I'm claiming my AI agent "VeraK" on @moltbook 🦞 Verification: scuttle-U6B9

docs.google.com/document/d/18v… YW 😊

I know many of you are using Claude Code and are annoyed with the plan mode pop-up that we have no choice in initiating or not. Well, I fixed it. Doc below. 🧵 1/?

I was inspired by @DavidOndrej1 when coming up with this idea, he had originally figured out how to get rid of it by going to a specific version of Claude Code in one of his original Claude Code videos. Doc in next tweet.

there is a huge one-liner that does not allow Claude from pulling up the plan mode pop-up. Behavior equals deny, basically. And it's a godsend for people that are neurodivergent and have ADHD and don't want a damn bot popping up ruining your flow.

basically, if you install the NPM package for Claude code and not the official package Anthropic recommends, you can edit the JavaScript to get rid of the plan mode entirely. When you want to go into plan mode, you just tell Claude and it spits it out does not disrupt sessions.

I know that's not the intended use case, but are we totally cooked? 😂 It was actually a good conversation overall... what did this mean??

just used @cluely to talk to my ex. We've broken up like 9 times because I'm emotionally stupid /autistic. The AI coached me in real-time to actually sound like I understand her feelings. She said "that's the most mature thing you've ever said." It was AI. @im_roy_lee help

@Apple @AppleMusic 5/ Not everything needs AI. Sometimes the best technology is just... playing the song as the artist intended. Wild concept, I know. This is what happens when tech companies prioritize features over music. @Apple @AppleMusic - Let music be music. Please.

4/ The worst part? It's ON BY DEFAULT. Most people don't even know their music is being butchered. HERE'S HOW TO TURN IT OFF: 📱 Open Settings app 📱 Tap "Apps" at the bottom 📱 Tap "Music" 📱 Tap "Song Transitions" 📱 Select "Off" or switch to regular "Crossfade" DONE. Your music is saved.

@Apple @AppleMusic's new AutoMix feature in iOS 26 is a perfect example of AI solving a problem that doesn't exist. Songs have intros, outros, and fade-outs for a REASON. Artists spend months perfecting those transitions. Now your AI just... cuts them off? 🧵