that is not a good excuse. using kind 1 just because all apps support them just forces social apps to have to keep filtering out different kinds of replies
I already had enough issues in noStrudel dealing with kind 1 replying to long form posts. now they are going to reply to everything? and im going to have to filter them out just to show the timeline?
Kind 1 notes will eventually be deprecated even by generic social feed clients in favor of structure.
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.
agreed, although "reimplement basic comment support" isn't really accurate. in the case of noStrudel I have generic comment thread components and I simple switch the kind depending on what they are commenting on
Yeah, but that's already enough work to make most client devs totally freak out.
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.
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.
