Just make the best UX you can and try to get users, its a waste of time to constantly discuss how to interoperate. If you get a ton of users you win the discussion and become the standard by default without saying a word

Replies (31)

Interoperabilidade é fundamental para garantir soberania individual, pois permite aos usuários escolher suas próprias ferramentas sem lock-in.
And that's why nostr doesn't work. Primal. That's their entire business model, make the shittiest app but get the most users in order to force the rest of Nostr to centralise around them
JackTheMimic's avatar
JackTheMimic 5 days ago
The only caveat I make is kind designations because there are a few apps out there that use the wrong kinds and it fucks up my other apps when I use them. If you are making a new thing and have a new idea, just create a new kind to go along with that idea. Don't clog up already established shit with your novel approach.
This has pretty much always been a problem in every domain. I suspect that's why some industries have centralized standards boards. Obviously people mostly still have to choose to follow them, but of course it isn't going to work if it's just the wild west. I dont see how making it wilder is going to bring more users in. If all they use is your app because nothing works together, you might as well just run a server and fuck Nostr entirely.
That's not it, but something like that, I remember it had letters instead of numbers. This stuff is way beyond what I can understand to be honest
The mere fact y’all are still working through these Nostr matters tells me we’re on the right track. Never settling. 👊🏼
Yeah not all nostriches speak dev gobblydegook Just give them the apps they want lol fucking hell
Constant's avatar
Constant 5 days ago
this post is meaningless, you are not actually saying much of anything here because interpretation can go into any direction on any level. Are you saying you can just go ahead and build in proprietary server side stuff which by definition can't interoperate? Are you saying you can just take some kind/NIP and use it in a different way such that it breaks on every other client, and not interoperate in that way? Or are you simply saying that you can put some NIP/kind out there, carefully not using any number that is already in use, and claim that spot for that number with that feature/usecase simply by becoming dominant which already was the idea of how things work behind Nostr? Or do you mean all of those things? Something else?
Constant's avatar
Constant 5 days ago
oh, yeah, sure, i guess. Might help to get some feedback on things in case you missed something or someone genuinely has a better idea or addition.... But all of this was permissionless to begin with. Except NIP-01, leave that shit alone, and if you do adopt a standard, actually adopt it and don't mangle it.
The difference is at least in the examples you gave those are options that can be supported by different clients because in some ways, they are standard and probably just different ways of doing the same thing. You didn't invent kinds that only one client uses.