Avatar
Mike Brock
b9003833fabff271d0782e030be61b7ec38ce7d45a1b9a869fbdb34b9e2d2000
Unfashionable.

I wonder if there will be a #TwitterFiles episode on how Twitter decided to censor Narendra Modi's political opponents, after an apparently private conversation between Musk and Modi.

If I knew, I'd already have placed some investment bets. All I know is that variables never hold constant over time.

It is far more of mean-spirited place these days.

I think Tesla is at pretty high risk of being "Blackberry-d". They're clearly the market leader, and they clearly have the potential to becoming overwhelmingly dominant for a long time in EVs, self-driving and energy storage, given some of their technological and manufacturing process advantages. But you might have said that about Research in Motion in 2005.

As a Tesla shareholder (yes, I still am), I'm pretty concerned that their Technoking is more a liability than an asset, given his decision to dedicate himself to a nonsense culture war.

They risk being caught flat-footed by someone else's "iPhone moment".

I'd say Tim Berners-Lee functions as a decent example of a benevolent dictator at the W3C on the pure standards side. At some point, the ecosystem may simply see better game theory in having someone serve as tie-breaker to avoid the decay you're talking about.

Replying to Avatar fiatjaf

How being "flexible" can bloat a protocol (a somewhat absurd example, but you'll get the idea):

Iimagine some client decides to add support for a variant of nip05 that checks for values at /.well-known/nostr.yaml besides /.well-known/nostr.json. "Why not?", they think, "I like YAML more than JSON, this can't hurt anyone".

Then some user makes a nip05 file in YAML and it will work on that client, they will think their file is good since it works on that client. When the user sees that other clients are not recognizing their YAML file, they will complain to the other client developers: "Hey, your client is broken, it is not supporting my YAML file!".

The developer of the other client, astonished, replies: "Oh, I am sorry, I didn't know that was part of the nip05 spec!"

The user, thinking it is doing a good thing, replies: "I don't know, but it works on this other client here, see?"

Now the other client adds support. The cycle repeats now with more users making YAML files, more and more clients adding YAML support, for fear of providing a client that is incomplete or provides bad user experience.

The end result of this is that now nip05 extra-officially requires support for both JSON and YAML files. Every client must now check for /.well-known/nostr.yaml too besides just /.well-known/nostr.json, because a user's key could be in either of these. A lot of work was wasted for nothing. And now, going forward, any new clients will require the double of work than before to implement.

I think this is how you ultimately get benevolent dictator models in open source and open standards. Linus Torvalds, for instance.

Totally. I've been beating this drum for a year! And look, I get that Elon is not alone. I know that Tim Cook isn't going to come out tomorrow and slam Xi Jinping, and the truth is, I didn't expect Elon to do it either.

What really gets under my skin, is that Elon claims he's in it for free speech and "not the money" and that he's a "free speech absolutist", when it's obviously not true! He's compromising these supposed values every day!

If Tim Cook started saying he believed in free speech without compromise, as Elon has done, I'd immediately start calling him out on China, too! And actually, I have called Tim Cook out on China, but you get my point: https://twitter.com/brockm/status/1598040467492724736?s=20&t=9RGkZb94mBZrsJTrG_V1YQ

From what I can tell, Elon scores 0/3 on this test. Which may work building cars, batteries and rockets. It doesn't work when you're trying to be the steward of social interactions.

How not to be a hypocrite and be a person of high integrity.

1. Say what you mean.

2. Mean what you say.

3. If you change your mind, or realize you were wrong, say so.

The end.

Re: Elon carrying Modi's censorship water. What I said about this back on Oct 4th.

I do hope I helped you in some way better understand the MWI, though!

I probably won't be able to read through this stuff until the weekend. But I will!

Nostr makes me miss my coding days. Don't grow up, kids!

What if part of a legislature was elected by popular vote, and part of legislature was selected by lottery? Just spit-balling, here.

If you're doing write-behind, you're *not* doing that. You're having a persisting thread consume the ring-buffer with its own tail to avoid any contention on the network relaying.

Routing new events. I'd leave the latter to some established DB technology line Postgres, InnoDB or MongoDB. I'm not going to do justice to the amount of engineering that's already gone into those.

What is the best/fastest Nostr relay software? I keep having this idea pop into my head that I could make an insanely efficient implementation of Nostr relay using segmented ring buffers, with contention-free writing, and using a write-behind scheme for note persistence. It's possible something has done something more clever.