Avatar
brianco
e8c1ca03a46d97184bfcd9125a5c9674a867bd1beaebe47c77d4eaec6c5ee874
permissionless product development. live and let live✌️

Watched The Godfather Part II again last night on Netflix. One of the best scenes and quotes of the movie:

Michael Corleone: Now, soldiers are paid to fight; the rebels aren't.

Hyman Roth:

What does that tell you?

Michael Corleone:

It means they could win.

1.4.3 (15) 👀

I would never use Amethyst Sky at this point. Definitely getting Mastodon benevolent dictator for life vibes combined with the paternalistic features like auto banning. No thanks.

I don’t think we are talking about the same thing. My comment was about expecting that every client is going to support every type of content. Maybe that wasn’t your point.

It is also the case that clients already implement things differently and have used NIPs in ways that break existing content implementations in other clients.

Some developers are going to be more interested in collaboration and ensuring the ecosystem is healthy than others.

I understand your perspective, but I think this is probably not possible. It isn’t the case now and will become even less so as more features emerge. It will be impossible for every client to offer all of the content types available on every other client. There will be a core set of content that social clients are expected to support, but there will be many clients that take a specific approach to features and content.

Nobody would be able to manage their product roadmap by playing whack-a-mole with other developers and their priorities. Even more so if some developers are not interested in signaling their roadmap or coordinating new features or changes.

What is crucial is that core features that have been rolled out across clients continue to work and that developers don’t unilaterally break things that have worked in a specific way.

Are people using direct messaging on nostr? We built support for it in Akawin Deck but pulled it out because of the metadata issue. Just curious what the argument is for clients including it when that issue still exists.

1.43 (10) 👀

Though, building an Android version is looking like something worth considering now.