#threads #nostrdesign
Discussion
Feels a bit overwhelming. Personally I don’t need to see who reacted what. Showing zaps might work
Yeah, I know I'm walking a fine line with this. And Id actually like a zap-only approach. But that would make it a bit too incompatible with other clients.
Or maybe that's not a problem actually. Gonna think this through a bit more.
It's quite annoying that threads still suck in most clients.
I see a lot of talk but nobody tackled this. We gonna get edit your mom’s popsicle before we gonna get threads 😂
uh. lots of threads on #coracle i don't know what client you are using... amethyst i suppose, or what?
Coracle doesn't have threads at all.
It shows my comments on my own post last (in chronological order), has huge indentation (preventing going more than like 6 layers down) and is one of the least info-dense apps out there with all the whitespace. Which is great for many other use cases, but not for threads.
threads are a general UI problem as a whole... the best implementations i've ever seen use revealer buttons, and from a back-end perspective they consume huge amounts of memory tracking the tree structure (not to mention the iteration cost)
my suggestion from many years loving this kind of feature is that it needs to be a very specific client that you use just for this one feature
Which client is this one in the picture?
