I once had a conversation with a reasonably well-followed "influencer" in the bitcoin space. Not a "top-tier podcaster" type but still one of the "cool kids." I was empassioned that the best way we can win as bitcoiners isn't just to post about it and "educate" but also to take our own productivity and store as much of it as possible in the bitcoin protocol.

The response I received was disappointing, (paraphrashing) "I disagree. This is the best asymetric bet out there today but there is still risk that we're wrong. I have a reasonable allocation to bitcoin but I am not a maximalist."

This voice is still out there today, posting a lot of bitcoin content - both on X and here on NOSTR - representing themselves like a maximalist. Their content rings empty knowing that they are not "all in" and still have a level of hedging to the legacy system and are (in my opinion) posting mostly for their own personal success rather than the success of the bitcoin protocol.

There would be a benefit to more true maximalists having the platform that many of these pseudo-types have carved out for themselves. Wrestling with navigating the transition from the legacy system is real (I am not a "get on zero" maximalist) but we need more 50%+ allocation types getting follows and being a bigger piece of the conversation.

I wonder how many people run their webpages on bare IPs, with no domain names whatsoever.

If you are going to tell me "dont go left" then you had better point me to the right or you are just part of the problem.

Yeah, basically trust the collectiv mind. What do you mean you haven't heard of Coldcard? You don't know this device?

LinkedIn following in the Twitter's KYC footsteps, and raising the stakes with the gov ID verifications.

Soft verification boosts for now.

How do we know that the random number generator in a Coldcard is legit and working as intended? Or any other HW device for that matter?

It seems to work fine... on mainstream browser engines and hipster shitcoding platforms like NodeJS. Everyone who wants to live more frugally is left out.

Bad taste in programming languages is something that led Nostr to use WebSockets instead of normal TCP sockets in the first place, introducing huge bloatware layers on all sides.

But again, this choice also come from someone who believes there are no other version control systems than Git and no other Git hostings than GitHub...

Nostr is a giant shit show. The fact that our software interoperates at all is a miracle and probably just a temporary anomaly. Given enough time, the relentless breaking changes being made to published NIPs will eventually break everything.

Linux succeeded because "WE DO NOT BREAK USERSPACE". For nostr to succeed, changes must "NOT BREAK EXISTING IMPLEMENTATIONS". There shouldn't be any exceptions to that EVEN IF THE IMPLEMENTATION WAS NON-COMPLIANT.

Pay close attention to Linus right here:

> Are you saying that pulseaudio is entering on some weird loop if the

> returned value is not -EINVAL? That seems a bug at pulseaudio.

Mauro, SHUT THE FUCK UP!

It's a bug alright - in the kernel. How long have you been a

maintainer? And you *still* haven't learnt the first rule of kernel

maintenance?

If a change results in user programs breaking, it's a bug in the

kernel. We never EVER blame the user programs. How hard can this be to

understand?

Linus doesn't want to break pulseaudio EVEN THOUGH pulseaudio was doing the wrong thing.

It seems like every week I find a NIP that I've coded for has changed. This last week I think it happened three times already. Sometimes it's a small change and I quickly update my code. But I can't read all the PRs, and I'm afraid dozens of small changes have slipped past my notice. Gossip is probably now incompatible with multiple other implementations which happen to have implemented different versions of the same NIPs (some older, some newer).

Even if we didn't have any breaking changes, the simple fact that different software implements different optional NIPs itself presents to end users like broken software. Why does it work in Damus but not Amethyst? Why does it work in Amethyst but not Coracle? That is an even harder problem to solve.

But let's at least solve the easier problem and stop changing NIPs. If you don't like a NIP make a new one, don't break the current one. Even if you think the current one sucks balls and should have never happened. Even if you think there aren't many implementations out there.

#Bitcoin ETFs broke $3 BILLION net inflows in just one month.

It took the Gold ETF 2 years to do that.|

#Bitcoin  is now the 10th largest asset in the world by market capitalization, surpassing giants such as JPMorgan, Berkshire Hathaway, Tesla, and Visa

one of the most pleasant things you do as a programmer is removing unnecessary code

it's almost as good as taking a dump after needing to hold it for a while until you get home

#devstr

who the fuck dreamed up the "gossip model"

#asknostr

because fuck them, fuck them in the arse

seriously, how am i supposed to test a relay i'm building when no client actually respects the fucking NIP 65????

uh, think about it you fucking numbskulls

The inflators usually blame producers and the weather.