I don't think forking, per se, is the solution. Instead, innovate, try new things, and try to play nice with other Nostr clients as much as you can. Breaking compatibility destroys what momentum Nostr as a movement has.
Discussion
i think a unified relay/client project is what will crack the userbase problem... the interop is generally mediocre at best out there still, and clients are very hit and miss from one to the next as to what features actually work properly, and it varies because of relays as well
Can you expound on that a bit? Are you saying relays and clients should be developed in parallel, or should the relay live in the client?
The latter solution ends up being peer-to-peer, with the associated problems.
i think the client and the relay should be developed as an integrated unit, then the features are going to work reliably, and it lets you shrink the feature set targets down so they get implemented systematically
also, for business use case, good interop is basically essential between clients and relays
there is a definitely discord between the "universal social network protocol" stream of development that gives you the outbox model, and the business use case of isolated subnetworks that don't get contaminated with the general open network
I completely agree with that. For business cases, the client and relay should be a paired set.
A group chat app would have to be something like that. Interop lets you open the door to let in events from the global network, but not every client needs to see every event.
exactly... this means a mostly private team chat, slack style, can have a public facing forum side as well, that isn't just specific to a website or client as well, though the internal version is paired because it's mission critical