Replies (47)
Nice!
Love it. π₯π₯π₯
Why is this better?
It follows the pattern of all other replies to other kinds. That makes kind:1 just for root short notes. This matches blogs, videos, literally all other events. Is it better? Perhaps not, but this keeps things more aligned. I
Why would we want to show replies to other kinds if we donβt want to support other kinds?
You could still hide those where the root event isn't a kind you wanted to show, keep it kind:1111 replies to kind:1 only for example.
I see. But why change? Still not sure whatβs the point t other than semantics
To follow how the protocol is implemented elsewhere. There's no QoL improvements.
π seems pointless if nothing is gained
its not if you're just making a kind1 client. in fact its worse because it fractures microblogging.
its not only pointless its actively harmful and weakens the protocol. keep kind1111 to comments on other stuff imo
I can already see kind 1111 on Jumble.
We have bigger problems to solve. Like, how to get people here and stick around.
nostr hard forking?
how many CLANS now ?
Algo is PRIMAL is TRASHSHIT worst that FB n X
Also, Amethyst.
Bloody hell. I just updated my personal client to kind 1111 replies to kind 1 notes because I thought there was consensus and I was being left behind.
Now I learn theres no concensus and I may have just cocked things up for myself?
Fake consensus π
Also, Noor Note.
Faster and more reliability in building threads, easier for new devs.
Consensus doesnβt exist on Nostr
You have few people in one camp
Some others in another camp
And then you have fiatjaf
also in his own camp
Kind 1111 fixes nothing for kind 1 use cases. Iβm wondering which one is worse, this or CLINK
It makes parsing and assembling threads easier. OK grandpas,less get u to bed ..
It's giving me headaches π©
I don't understand why we need kind1111 for other stuff comments either, kind 1 simply works and is better for discovery too.
Although I will not fight the community on this one, and my strategy of just supporting both has worked out well so far.
I like kind 1111 and it works great. (imo)
happy for u
Why break backwards compatibility? If clients have to show kind 1 replies anyway, why use 1111?
I wish. You still need backwards compatibility with kind 1.
Dude when are you gunna put damus on zapstore
There needs to be a transition period.
Only if everyone is unaligned. If they are aligned then 1111 is better.
This is just like tags on kind 0 instead of stringifies content.
Uniformity is better. Doesn't make sense that some older kinds and events just work differently than everything else because that's how it started. But it's a problem because to move in, you have to support both until nearly everyone is on board.
Nostr clients has a concensous problem. Maybe we can look for solutions to make some sort of concensous among clients.
i think
@Jumble still publishes replies as kind 1 though
yep. just confirmed that it does.
There is no end to the transition period. You will still have people wanting to look at replies from 2 years ago.
It makes absolutely no sense, all we did was break the only working part of nostr
Good point.
Therefore, we can either accept the legacy baggage, or add even more shit to βget rid ofβ the legacy baggage which will haunt us until Nostr dies whether we like it or not
Vibecoders donβt understand backwards compatibility
We're going to need an archival relay that captures and converts Ll the old K1 stuff...
I always forget what this discussion is about, and then I worry whether I need to change anything in my client, I think probably not though, oh dear oh dear.
At this point I'm just gonna sit back and see how things play out, then move. At the moment there's more risk of fragmentation the more I do so I'll just let the community get its collective shit together and wait and see.
Kind 1 works with everyone and is the original standard
The time will come, and if it doesnβt they donβt deserve it