Please report back or don’t because you’ll be asleep

every time I watch this one video about fractals I fall asleep

I can’t get through even like three minutes it’s incredible

on that note good night probably

I was really frustrated and upset the other day because of things I'd heard in the news and dumb stuff that the government is doing.

@tbone told me to go and pat the goats.

It's impossible to be angry when you are patting a goat 🐐

The greatest cryptography is analogy.

If you have a god-like computer, you can "break" all cryptography, since it's all objective.

Analogies are subjective and you can't "break" them if you don't have the key.

That's why ancient/old analogies survived until today.

The wise ones used to communicate in analogies so they wouldn't get burned alive by the church some hundred years ago or be murdered by the local establishment thousands of years ago.

Brisket is right. If you don't know what you are doing, consultant an electrician. And it is different to something like a toaster which only ever runs for a few minutes at a time and is always supervised.

All part of the education!

I'm In AU.

I have a workshop that I am hoping is on its own circuit. I need to do a bit of testing.

Going to be interesting and educational that is for sure.

Would do ice cream or whipped cream.

I like my custard frozen!

the main cost is that it turns the frogs gay

Datum gateway is consuming a ton of memory on my node. Anyone else experiencing the same? I realise it’s labeled as a beta. #AskNostr

You're drawing lines as well?

🤣

Magic day today man.

Did you touch some grass?

You can tell yourself life is amazing, it sucks, or anywhere in between.

Whatever you choose, you’re right.

Always remember you create the reality you live in.

Much love all.

Why I'm for loosening the OP_RETURN limits ⏎

- In practice, OP_RETURN is already unconstrained: see Carman's OP_RETURN bot or Portland's Slipstream.

- Encoding arbitrary data via OP_RETURN is far more responsible than doing so in witness data, as it's 4x more costly.

- OP_RETURNs are prunable and do not pollute the UTXO set, making them vastly preferable to faux outputs that burden every node indefinitely.

- Mining non-standard transactions that bypass mempools undermines decentralized transaction propagation, disrupts fee estimation, and increases block propagation latency (especially when compact block construction fails due to missing transactions).

- This latency disproportionately impacts smaller miners and encourages direct submission to large, well-connected players, widening the profitability gap and increasing centralization.

- Layer 2 protocols are especially sensitive to fee miscalculations, making transparent and measurable fee behavior essential to their reliability.

While I share the distaste many have expressed toward tokens, inscriptions, and BitVM (when used as a casino), I care deeply about minimizing harm to bitcoin’s base layer. Allowing larger, standardized OP_RETURNs is a pragmatic step in that direction.