nicholas 🧨
@nicholas
@dwr.eth the part of threads that i would like improved is that i have to “show more” and tap into casts repeatedly to read a full thread between even just 2 people. @aethernet threads are good examples
6 replies
0 recast
22 reactions
Dan Romero
@dwr.eth
Is it different on Twitter?
4 replies
1 recast
2 reactions
nicholas 🧨
@nicholas
With lots of respect, I don’t see what that has to do with my feedback
1 reply
0 recast
16 reactions
Dan Romero
@dwr.eth
It’s expensive (computationally) and slow to preload. So most apps don’t do it. We could do it but trade off on performance. Are you specifically interested in OP and one other person back and forth?
4 replies
0 recast
1 reaction
kia
@kia
1. i get the performance issue. but if i take 1 or 2 actions to indicate that i want to read a back and forth between two people, it should be safe to assume that i want to read a substantial amount. don't make take an action for every 2 posts. 1.a. you could run an a/b test and see if more multi-cast conversations will be read to the end and if that'll improve any content related metric that you're tracking. 2. i get that x might be similar (it's not as painful). but this is obviously a pain point that people keep bringing up time and time. and maybe that sign for an improvement to be made. vs just pointing out how twitter is.
1 reply
0 recast
7 reactions
Garrett
@garrett
yeah i agree here some of my fav content is buried in a back n forth where i have to constantly click in
0 reply
0 recast
0 reaction
