rewolf on Nostr: I really don’t want a single app for all nostr applications. Separating concerns ...

I really don’t want a single app for all nostr applications. Separating concerns seems right. But how would we route different event URIs to the right apps?

quoting note1f5p…c06y

We don’t expect standard note-focused clients to be understand all event kinds. But it’s common to want to share special events from within standard #nostr notes.

E.g. sharing a URI to a recipe I created on zap.cooking

Even if it just rendered it with the title, there’s no way to open it in the right client.

I wonder if we could build a Nostr router app that could be configured by the user to open preferred apps for a corresponding event kind.
Ideally we would have the event kind in the URI scheme so the router wouldn’t need to download the event first.

Then I could click a nostr:35000:neventabcdef21 URI and I could have the router configured to open it with zap.cooking and the same for other event kinds.

Is this a dumb idea?

#asknostr #nostrdev