Thanks Derek. Much appreciated!

Reply to this note

Please Login to reply.

Discussion

wasn't aware it says all p tags. even original branle only included first 4 or so.

i guess astral isn't to spec cus now it allows you to edit the p tags yourself.

Yeah I find it odd. I'm not allowing the removal of the tag to the author of the note you're replying to, but I'm letting the others be removed. I don't see any reason not to. I wasn't including them at all until I saw that in the nip. Seems to me the only person that should be automatically tagged is the original author.

it probably to make sure others in the thread can get notifications if they want them..? bc otherwise its hard to get notified of a new reply

I can see that as the default behavior, but not requiring that they all remain tagged. I only noticed b/c I got a reply in my notifications that wasn't directed to me at all. I was further up the chain and still got a notification. I can see it becoming a real nuisance. I'll be introducing a Twitter-like option to not receive notifications of replies to a particular thread to prevent that. Might be a good idea for Astral too.

yeah i'll probably put in notification personalization, but by follows, pow, etc. but might be complicated to track down how far removed your post is from the reply, but identifying direct reply might be straightforward.

That would be awesome, because once you reply Jack you’re IN for a long ride of unrelated responses.

Oh. Speaking of threads. The first client to do proper threading of MASSIVE threads will win over 550+ Stackchainers. The current #Stackchain thread on nostr is very hard to follow and very broken.

The original Stackchain on Twitter has been going on for 5+ months and is probably the longest thread ever on Twitter at ~2600 replies, not counting all of the sidechains and offshoots.

On it 🫡

Initial debugging looking good :) Whole #stackchain on screen. I'll have to figure out some partial loading when it gets huuuge but shouldn't be a problem by the looks of it.

😂

That's why I'm using Twitter's method for threads. You see the first level replies only and have to click to see replies to that reply. I'm also going to implement a "see more replies" link after a fixed number of replies, also Twitter-like.

Yeah stackchain mining on nostr is slowed down by this problem. Takes a while to be sure the chain tip is where you think it is.

This has always been a problem. 😂