Nostr Web Client

It sounds like the way forward will be for new feature specs to explicitly define their comment types. Kind 1 or kind 1111 could be used as a baseline, with additional requirements added to support the needs of the intended feature.

The potential pitfall is that clients would have to reimplement basic comment support multiple different times for different feature sets, but I don't think that's necessarily such a problem. Nostr apps don't need a "global" feed that sucks up everything, nor does every client need to support most NIPs. Make more single-use clients.

Laeserin 1y ago

The problem is that there's no notification app, so the Twitter clones are the closest thing we have and everything that doesn't show up there doesn't get a response, because people can't go to 5 different apps, every day, to see if someone responded to something.

Like, if I go to GitWorkshop.dev and write an issue, neither of you nor anyone else responds. I have to tag someone on a Twitter clone or reply to the issue with a Kind 01 note tagging them. Then it shows up in their notifications and I have a chance.

Reply to this note

Please Login to reply.

Discussion

Laeserin 1y ago

Like, someone will go to an OtherStuff app, write a comment, close it, open Primal or whatever, and then replying to them in the OtherStuff is useless. It's now dead to them.

We have threads in app silos, just like with legacy systems.

MichaelJ 1y ago

Yeah a central notifications app that helps you jump between clients is one option, or else better notifications on OtherStuff apps.

Laeserin 1y ago

Where do the notifications go, tho? E-mail? 😂

If it doesn't show up in a Twitter clone client, it didn't happen.