Last night I addressed one of my shortcomings as a father: my 15 y/o daughter finally watched The Matrix.

STOPPED SENDING GM NOTES BECAUSE PRIMAL TRENDING HEAVILY WEIGHTS REPLIES AND THERE WERE TOO MANY CONSPIRACIES ABOUT WHY MY NOTES WERE OFTEN AT THE TOP OF TRENDING.

Take a deep breath and lower your shoulders.

#Unix or #linux desktop from the 90s. Awesome aesthetic 🔥

And we wonder why people are so fucked up, people building apps just want you to be hopelessly addicted so they can make more money from ads. It’s hard to find design books on optimizing human well-being. Why does our relationship with computers have to be framed around getting users hooked on crack? There is something seriously wrong with our industry. nostr:note12er924k94g2qjpx004758q06tklrwfwp7v5lrh422nfzjdykk53sq87z4k

Psst

Well obviously we have an authoritarian government in the US. They are climbing in your windows, they are snatching your freedoms up. Hide your pans, hide your USB cables because everything is a money transmitter up in here. #Bitcoin

I’d be happy to contribute to and use my public platform to bring attention to legal defense funds for people who build open source privacy tools, or for legal attempts to push back on unconstitutional government financial surveillance.

I just need to know that they are credible from people I trust.

Wow, that is impressive! What has been the most rewarding part of your journey so far? #inspiration #7yearsandcounting

4 months no alcohol.

your body can tell the difference between some fake ass blue light and the fucking SUN

good morning

Time spent defining the problem is worth 10x that of building the solution.

Don't ever mistake motion for action.

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.