Content pfp
Content
@
0 reply
0 recast
0 reaction

Dan Romero pfp
Dan Romero
@dwr.eth
"Warpcast needs to do a better job with threads" What does that concretely mean? How is X / Twitter better? e.g.
37 replies
2 recasts
77 reactions

phil pfp
phil
@phil
Rather than give you a grand theory, here’s some specific UX feedback: “show more” shouldn’t collapse “the main thread” Deciding what is the main thread is a thorny problem (I’d be happy to chat about it, since I’ve spent a lot of time thinking about this in the context of email threads), but here’s a specific example. Clicking into this sub-reply is clearly an extension of a conversation between two participants. Yet, it’s hidden underneath two subsequent “show more” buttons. These should automatically be expanded if there are no other branching threads.
1 reply
0 recast
4 reactions

Dan Romero pfp
Dan Romero
@dwr.eth
thanks, this is helpful.
1 reply
0 recast
1 reaction

Edward H. Carpenter pfp
Edward H. Carpenter
@ehcarpenter
Concur with Phil, and here (unlike X) it's hard for me to see/know who's going to "see" my comment - adding screenshot for example: I'm replying to you, but referencing Phil's comment, but I'm not sure if this comment will show up in @phil 's notifications unless I tag him myself (as I just did) Ideally, I think the default should be that the thread author and anyone in the direct line of a conversation in the thread should be notified, and the UI should highlight that... This is because good threads can "branch" - and some people might want to tie branches together. I.e., this is a comment reinforcing Phil's note, I might want to also refer to Erica's ( @heavygweit ) observation that Twitter is not necessarily the benchmark for excellence - in fact, I'd be tempted to say a great exercise would be to try to design a thread system from scratch, without the "distraction" of other platforms. Birds were the standard for flight, and a lot of time was wasted by humans trying to emulate them
0 reply
0 recast
0 reaction