Look at this.

Took him only 8 days to go from his proposal to changing Kind 01 feed single-handedly through a new software version. Effectively, a week.

Most devs hadn't even seen his proposal, yet, (and some still don't know what is going on!) and the others were still debating the best way to do this (thank you, at least someone cared) and BOOM! it was delivered. Discussion over. Everyone scramble to do likewise.

This is not okay.

nostr:note1uss2pucxgq9j6awjdw0ue9cknf74l0la5v90hadwqx5fm0hcyeasrmd4gn

Reply to this note

Please Login to reply.

Discussion

Some of our own devs only know about it because I contacted them personally, to inform them.

Wut? Huh? You must be mistaken, Leserin...

No, I'm afraid that this is not a joke.

Well, the joke is on us, I suppose.

This sounds like RFCs, W3C standards and most others. Pretty much all standards lag.

There's almost always **at least** one implementation that has been tested, they figure out what works well in practice and then write it up and submit it to the standards body.

I think that's generally fine. It becomes a problem when there's a near monopoly. When Google makes Chrome do something non-standard, convince web developers to quickly depend on it, and then users get mad when their other browsers don't work. Then others browsers implement the new thing, and at that point the standards body might as well accept it since it's already a defacto standard.

Maybe that's the case here, but I maintain that the problem is not that we have a free market of ideas where people can implement whatever they want, but that a single client has gotten enough sway to make everyone else feel compelled to immediately follow suit.

Yes, but that was my argument and why I'm asking npubs to move to other clients, if possible. Spread out more.

One client shouldn't be able to force changes on others, especially changes to Kind 01.

Kind 01 is holy.

This is the equivalent of Chrome changing the basic HTML tags, so that you can change the basic content of a webpage, by adding a second header and body tag that overrides the original header and body, but that new body content would only show on Chrome and everyone else would display the old one.

So that you have two completely different web pages, depending upon the browser.

Do you have any recommendations for Android?

When I search for "nostr" in F-Droid, exactly 1 nostr client shows up.

Freestr is fun, but very beta. Like the long-form display and the DM-first setup.

Primal Android is working well.

And I pulled Nostrudel out of my browser and onto my mobile startscreen. I've done that with Coracle, as well. Works like an Android-native app, then.

I'm not actually clear on why people don't use the web apps on mobile. Many mobile apps are just prepacked web apps, anyway, and then you skip the store step.

I just started using Yana today. It's compatible with Amber, the signing app. I used Nostros once long ago, and will be using it again soon.

Amethyst, you don't need F-Droid, you can use Obtainium to download and keep apps updated directly from the Github (and many other source), without trusting F-Droid.

We're looking for alternatives to Amethyst. That's the whole point of the thread.

"Onyx" is a fork of amethyst

Does it contain the breaking change he just implemented?

No. It doesn't contain that or any security filters it also hasn't been updated for months

👍🏻

When you download it, it doesn't even have a terms and condition to check off

Ok sorry I jumped in the middle. There are many alternative but none are as complete as Amethyst, and as you mention the edit function is super new and not really adopted yet, it needs time.

Nostrudel is much more complete than Amethyst.

Nostrudel is nice

it's confusing to me, nostter.app is so much simpler.

I use Nostter, as well.

Using Nostrudel on Spring browser is the best experience for me

Interesting. Haven't tried the Spring browser, yet.

F-Droid reports when apps have trackers. Obtainium does not.