Nostr Web Client

"It's my project and I can do what I want" can be both true and irrelevant. He can do what he wants to his project. But that doesn't mean he can prevent forks.

Getting nostr to where it is absolutely was difficult. But that doesn't make forking impractical now.

The core protocol can't change on a whim. If that happens tons of different clients break.

I remain skeptical of your claim.

Unhosted 1y ago

Would love to see more perspectives on this nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc

Reply to this note

Please Login to reply.

Discussion

Geek 1y ago

I wonder what nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp would say also.

semisol 1y ago

fiatjaf cannot unilaterally change the protocol

HoloKat 1y ago

I don’t understand the argument for why it’s not forkable … nostr consists of clients which implement NIPs and relays. Fiatjaf doesn’t control any implementations. Maybe he has the ultimate merge say (I don’t even know if this is true) but it’s up to clients what they wish to implement. And if enough devs decide they don’t like the direction, I don’t see why they couldn’t fork off and ignore FJ’s version …

But I don’t know anything so… I’ll be quiet now.