BTCKitty ⚡️

The world is not anymore the way it used to be! Mmmm, no, no, no!
#nostr: npub170e6afdcny0tx2ndg32w54529tz3q782xk96gfmjmwjntqnzunrqdf0txy

[BTCKitty ⚡️ @BTCKitty]

Are you OK with inflation?
Are you OK with the government and banks devaluing YOUR money to fund wars?
No?
So what are you gonna do about it?
Use #Bitcoin

[Ed Chambers @dealsanddrones]

@midjourney

[okazakitomohiro @oo_kk_aa]

ニャッキの伊藤有壱さんにお声掛け頂き、コマ撮りの展覧会に一作家として参加しています。私はコマ撮り分野ではない場所から活動をはじめて、デザインの視点でのコマ撮りに取り組んできましたが、今回初めてコマ撮り界の本丸の方々とご一緒でき嬉しいです。今6年目のマッチ撮影素材等を展示しています

[positive side of X 🌞 @positivityofx]

accuracy:100
damage:0

[Mike Schmidt @bitschmidty]

With an increasing number of discussions around the BIP54 “Consensus Cleanup” soft fork proposal, I helped put together an information site about BIP54.

“Bitcoin has four known vulnerabilities that have gone unfixed for 15 years. BIP54, "Consensus Cleanup", proposes four narrowly-scoped changes to address these issues in Bitcoin's consensus rules that date back to the original version of Bitcoin in 2009.”

https://t.co/ysNChR35Ib

[cats with powerful impression 🐾 @catshealdeprsn]

I can watch these two all day

[Jaynit @jaynitx]

In 2019, MIT professor Patrick Winston gave a legendary 1-hour lecture called “How to Speak.”

It has 18M+ views for a reason.

His frameworks:
• Your ideas are like your children
• The 5-minute rule for job talks
• Why jokes fail at the start

15 lessons on communication:

[Boris Cherny @bcherny]

I wanted to share a bunch of my favorite hidden and under-utilized features in Claude Code. I'll focus on the ones I use the most.

Here goes.

[Joseph Viviano @josephdviviano]

me: "can you use whatever resources you like, and python, to generate a short 'youtube poop' video and render it using ffmpeg ? can you put more of a personal spin on it? it should express what it's like to be a LLM"

claude opus 4.6:

[Lightning Labs⚡️🌐 @lightning]

AI agents can write code, send emails, and make phone calls. But they still can't transact.

Today we're fixing that. Releasing a new set of tools that give agents native access to the Lightning Network: lnget for automatic L402 payments, MCP for node operations, remote signing for key isolation, and scoped credentials for spending control.

The machine-payable web starts now. And bitcoin makes it possible. ⚡🦞

https://t.co/B0KW01l6ZD

[Connor Boyack 📚 @cboyack]

https://t.co/4SMw7birVU

[Matt Shumer @mattshumer_]

https://t.co/ivXRKXJvQg

[arbed_out @arbedout]

Bearish on LLMs replacing software engineering as a discipline anytime soon. But I can def see them replacing CS four year degree programs in ~ 10 years

Feeding ChatGPT undergrad text PDFs and asking to explain them blows away my old undergrad TAs by several orders of magnitude

[cats with powerful impression 🐾 @catshealdeprsn]

Im glad they didn't overreact

[cats with powerful impression 🐾 @catshealdeprsn]

My kitten Charlie loves the laundry hamper. He’ll meow and whine until you put upside down so he can become a kitty roomba.

[The Vigilant Fox 🦊 @VigilantFox]

Senator Ron Johnson opened the hearing with a bombshell: the Biden administration KNEW about deadly heart risks tied to the COVID shots, and deliberately kept it from the public.

Johnson released newly subpoenaed records exposing a detailed timeline of what officials knew and when. While Pfizer and Moderna received insider updates, doctors and citizens who raised concerns were silenced.

In February 2021, Israeli health officials warned the CDC of “large reports of myocarditis, particularly in young people” following Pfizer injections, just two and a half months after the vaccine received emergency use authorization.

By April, the CDC was already reviewing myocarditis data from Israel and the Department of Defense. But instead of alerting the public, they stayed quiet.

By the end of that month, VAERS had recorded 2,926 deaths, nearly half of which occurred within three days of injection. “Somebody ought to be looking at it,” Johnson said.

In May, the CDC considered issuing a formal health alert—but scrapped it. They replaced it with watered-down guidance that removed a key warning for doctors to restrict physical activity in myocarditis patients.

Francis Collins, then director of the NIH, brushed it all off. “Senator, people die,” he told Johnson.

In just six months, the toll was staggering: 384,270 reports of adverse events, 4,812 deaths, and 1,736 of those occurred within just 48 hours of injection.

[Alexander Leishman 🇺🇸 @Leishman]

At @River we will continue to run Bitcoin Core because it is the only properly maintained Bitcoin node software. The Bitcoin Core dev team is highly competent and dedicated to the long-term success of the network. The current state of the debate around OP_RETURN relay rules is the result of overdramatizing a nuanced technical decision regarding tx standardness rules. Running poorly maintained forks of Bitcoin (with their own large flaws) because of this minor technical debate is an overreaction IMO.

No Bitcoin Core dev wants the blockchain spammed with data because they are the ones forced to deal with the scaling issues and edge cases that follow. However, the reality today is that consensus rules allow transactions with large amounts of data in OP_RETURN, regardless of mempool policy! So, the broader debate here is twofold:

1. People want to put data onchain and they will do so with or without OP_RETURN limits. There is nothing stopping these people from skipping the mempool and submitting nonstandard txs directly to a mining pool today, or using even uglier approaches that bloat the UTXO set (even worse for the network). If we want to actually “fix” this, we would need a consensus fork, not a mempool rule change. The decision to change the standardness rules to allow these txs to be relayed seems reasonable and not a big deal.

2. The divergence between standardness rules and consensus rules: There are many transactions one could make that are valid by consensus rules that cannot be broadcast to the network today because they are “nonstandard”. This does not stop a miner from including the transactions in a block. High divergence between standardness rules and consensus rules leads to complexity in the Bitcoin Core software and causes problems for block relay efficiency when people start sending non-standard transactions direct to miners. Starting to move away from this divergence seems reasonable, but needs to be done carefully. We can likely never fully delete standardness rules but I understand the goal to reduce complexity here.

This debate should remain objective and technical. It’s being blown way out of proportion. Remember, the vast majority of Bitcoin Core devs deeply care about the long-term health of Bitcoin and have dedicated their careers to getting Bitcoin where it is today.

[cats with powerful impression 🐾 @catshealdeprsn]

When you care who you love and do your best to make them happy

[jack @jack]

delete all IP law

[cats with jobs 🛠 @CatWorkers]

Assistant window cleaner.