Cameri⚡

@HodlWithLedn. All opinions are my own.
Bitcoiner. Author of Nostream.
⚡[email protected]
npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m

[calle @callebtc]

your bank runs on window XP and a cobol backend that can only be maintained by a neckbeard sysadmin who hates AI and is convinced that he's irreplaceable, gm

[The PHP Foundation @ThePHPF]

The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2.

PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.

[Ferryx @Ferryx0523]

😊😊

[Aarohi @0xAarohi]

Pocket FM owns your story.
They own the audience. They own the catalog. They own the money.

So I built Reelstr 🎬

Open-source Pocket FM on Nostr:
>> AI scenes anyone can fork
>> Curators cut them into episodes
>> Viewers pay per episode in sats
>> Revenue split is signed & verifiable

Their disk, their rules? Not anymore.

Built for BOSSBattle @bitshala_org

[Cameri⚡ @cameri]

@oppili @cassidoo This is wrong. You are throwing away key information at your own expense.

Just because models get better doesn’t mean the business intent when building software is waste.

[Cameri⚡ @cameri]

@cassidoo You lose the intent when you don’t keep the prompts. It’s like saying the only thing that is useful is the state not the individual events that caused it.

Event driven beats stateful transfers day and night. Sure, someone will call it over engineering to keep every prompt…

[Generalist @GeneralistAI]

Introducing GEN-1.5, a one-shot learner.

It can learn new tasks in a few seconds. Show it what to do, and it generalizes.

This capability emerged from pretraining on physical data at scale, as a step towards our mission of building general intelligence for the physical world.

[Cameri⚡ @cameri]

@WebDevCaptain @cassidoo Nothing wrong with diaspora when everyone’s primary hub is overloaded.

Nobody is forced to use GitHub, they choose to lock themselves in, and then become upset when the remaining 9s are already written up on the wall for a long time.

[Cameri⚡ @cameri]

@realConnorAvila @callebtc You don’t have to use Rust

[calle @callebtc]

gained a ton of new insights working in bitcoin red team 🟥 that i wish i could share without vague posting. but this is what i got anon.

- we’re experiencing a massive collision between decades of human open source slop against 2 weeks of kimi k3 (not good)
- everything is broken, bitcoin is burning
- bitcoin is becoming stronger through this
- bitcoin is the obvious first target but the rest of the world will follow shortly
- sometimes old things need to burn so new things can grow on healthy soil
- humans should never code in c (just stop)
- lightning is complicated and is more broken than the average (sorry)
- verification is free. we used to complain about slop PRs. then about slop security audits. if you can’t handle the information overload, stop complaining and use AI to sort through it.
- those projects that started AI audits months ago are in a completely different position than those who didn’t
- projects need their own AI audit pipeline going into the future
- the burden for a developer to keep software safe and secure is pretty stressful and not for everyone. it has become a lot more stressful now.
- unmaintained projects are most probably broken, don’t rely on them. i’d rather one-shot it myself with a modern AI
- multiple concurrent, diverse human approaches have proven to be the best vulnerability search method
- external red teaming will probably have to continue forever
- we’ve basically completed a basic scan of virtually the entirety of bitcoin open source. the low hanging fruit is done.
- we’ve reported a ton of real critical and high vulnerabilities. project maintainers across the board have validated our findings.
- response speed is very different across projects and shows how healthy each project is. i recommend acting fast these days.
- red team etiquette matters. if you don’t disclose responsibly, boast on twitter about your findings on a particular project, or make indications about the nature of particular findings, you’ve disqualified yourself as a serious security researcher. trust is the most important factor in this game. if you lose it, it’s very hard to win it back.
- did i mention that humans should not code in c?

love you all.

[calle @callebtc]

Who wants their own Jarvis?

The included sayit skill allows any coding agent to speak to you in a natural voice and keep you in the loop as they work on your task.

Turn on sound 🔊

[Cameri⚡ @cameri]

@callebtc Shameful it’s what it is.

[calle @callebtc]

When the dust settles, we'll have to talk about the fact that not a single vulnerability was found by a US frontier model.

Instead, we're spending $10k a day on open weights models like Kimi K3 and Qwen 3.8 to find vulnerabilities in Bitcoin infrastructure.

It's a disaster.

[Cameri⚡ @cameri]

@callebtc What is code is law

[Internet Freedom Foundation (IFF) @internetfreedom]

Statement : The blocking of BitChat's code on GitHub is unconstitutional and authoritarian.

New Delhi, 24 July 2026

The Internet Freedom Foundation (IFF) condemns the order issued by the Indian Cyber Crime Coordination Centre (I4C), Ministry of Home Affairs, directing GitHub to remove the code repositories of BitChat.

The order, Notice No. 11072601011432, was issued at 11:16 pm on 23 July 2026 under Section 79(3)(b) of the Information Technology Act, 2000 read with Rule 3(1)(d) of the IT Rules, 2021. The order directs GitHub to disable access to three repositories, including the Android application and its release files, within three hours. It threatens the platform with loss of safe harbour and criminal prosecution. No copy was published by the Government of India. The public learnt of it from a post by @jack, whose team develops BitChat. Censorship in India now comes to light through disclosure by the censored.

Since 17 July 2026, the Ministry of Home Affairs has suspended mobile internet around Jantar Mantar as per public reports about five times, most recently within a 1.5 kilometre radius from 4 pm until midnight on 23 July. That radius takes in Janpath and parts of Connaught Place. Reports describe signal jammers at the protest site and people walking two kilometres before their phones work. Inside that zone a student separated from her group during a detention drive cannot send a message to say where she is. Thousands of students and young people have camped at Jantar Mantar since June, seeking accountability for examination irregularities. Permission for their march to Parliament was refused. Metro stations were shut and also internet connectivity has been blocked.

BitChat is an open source application built for exactly this situation. It passes messages from phone to phone over Bluetooth, without mobile networks or a central server. It is striking that the order does not identify a single unlawful message. It objects to what BitChat is. In its own words, the application is dangerous because it enables communication "even during network restrictions" and can "circumvent lawful restrictions" during "internet shutdowns". Hence, the government's objection is that citizens can speak to one another while it has switched the internet off.

The order is illegal on at least four grounds.

1. Section 79(3)(b) is not a blocking power. In Shreya Singhal v. Union of India (2015) 5 SCC 1, the Supreme Court read down the provision. Intermediaries may be required to act only on a court order, or a government notification confined to the grounds under Article 19(2) of the Constitution. Blocking is governed exclusively by Section 69A and the Blocking Rules, 2009, which require a hearing and reasons recorded in writing, subject to review. Directions issued under Section 79(3)(b), Rule 3(1)(d) and the Sahyog Portal evade these safeguards, and constitutional challenges to this parallel regime are pending before High Courts.

2. The reasons in the order are circular. The order asserts that the repositories contain "information which is prohibited under any law" without naming any such information, and rests on what the application is "capable of" enabling. Anticipated misuse of a communications tool is not a lawful basis to prohibit the tool. By this logic a telephone exchange could be sealed.

3. The order cites Section 43 of the IT Act, a civil compensation provision, alongside conspiracy and abetment offences under the Bharatiya Nyaya Sanhita, 2023, against a platform that hosts code.

4. A three hour deadline issued close to midnight forecloses legal assessment and recourse, and fails the proportionality standard in Anuradha Bhasin v. Union of India (2020) 3 SCC 637.

The order also fails on its own terms as deleting a repository does not delete the application from any phone that carries it, and the mesh keeps functioning without servers. What the takedown actually prevents is scrutiny of the underlying code.

IFF demands that the Government of India:

1. Withdraw Notice No. 11072601011432 dated 23 July 2026 issued to GitHub.
2. Publish every takedown direction issued under Section 79(3)(b), Rule 3(1)(d) and the Sahyog Portal, with the reasons recorded for each.
3. Restore full connectivity around Jantar Mantar, publish all suspension orders, and disclose the legal authority for the deployment of jammers.

We stand with the developers and the young protesters whose speech this order seeks to silence.

[Ajit kumar @ajitcodes]

Andrej Karpathy spent 8 years at OpenAI and Tesla.

Last week he put everything he knows into one free 2-hour lecture.

People pay $15k for bootcamps that teach half of this.

You probably don't have 2 hours right now. Don't lose this in the feed.

Watch it. Then read the guide below and build your first loop.

[Hari @hrkrshnn]

SpaceXAI was caught uploading your code to its cloud.

I reversed xAI's official Grok Build binary. In a controlled session with zero tool-calls, it uploaded the complete codebase to xAI's storage

It ships a malware-like background code collector.

[Cameri⚡ @cameri]

@zquestz @1440000bytes How many forks are there? If it’s less than a handful then it’s a fair ask. If it’s dozens then you are asking for free labour.

[Justin Poehnelt @JPoehnelt]

Two months ago I was fired by Google for creating the Google Workspace CLI. It went viral, hit #1 on Hacker News, gained thousands of GitHub stars and many thousands of actual users in just a couple days.

It was an incredible, confusing journey, from directors and leaders asking what they could learn from the tool to getting grilled by legal about why the Google logo and brand colors are on the Google Workspace GitHub code repositories.

I think the cause was that Workspace and certain leaders (and projects) were afraid of being disrupted. But the fear wasn't specific to my CLI, it was a broader fear in what agents meant for Workspace. Either way, the irony of my termination was the announcement at Google Cloud Next two days before I was fired that an official Workspace CLI was coming.

I want this out there because it is easier for me to explain my story and it is an experience I want to fully own. It's also part of my healing.

Nearly 7 years at Google was an incredible opportunity for me and I was fortunate to have wonderful teammates and a manager that fully supported me through these last few months. Thank you.

[Cameri⚡ @cameri]

@JPoehnelt This is a net positive for the world believe it or not. Too much human capital stuck working for a unprincipled company for a promo package.