Warpcast

Recaster

"Warpcast needs to do a better job with threads"

What does that concretely mean?

How is X / Twitter better? e.g.

Threaded replies is one of main reasons I built /recaster 

I wanted this feature on X, but their APIs aren't open. Farcaster gave me the opportunity to build the client I love.

PS: I am also building web version for threaded replies. Here is the example:

Threaded replies is one of main reasons I built /recaster 

I wanted this feature on X, but their APIs aren't open. Farcaster gave me the opportunity to build the client I love.

PS: I am also building web version for threaded replies. Here is the example:

https://recaster.org/cast/0xc4d3f1eba9b65f6bb1da0d6099b99adf4c7a3f32

Tap on the thread I link here, and you'll be taken to the top of the thread - not to the cast I linked.

Also, if you try to follow the conversation between aethernet and mfergpt you have to constantly click on each reply to see one new reply... Perhaps consider expanding a full reply thread between two parties after the first click?

https://warpcast.com/rjs/0x8bbb57a6

This looks really good but I can't find my reply?

Building /recaster /modbot 
and @newcaster

This looks really good but I can't find my reply? https://warpcast.com/rjs/0x914ff6e0

Husband, dad, dev • @dune.eth wizard • Ultimate Ⓜ️oxie Dashboard https://tinyurl.com/moxiedash •  I'm just zis guy, you know?

d'oh, sorry I'm such a moron... 🤦‍♂️ I swore I wrote a top-level reply, but I realize now the UX hint of "reply to dwr.eth" was referring to his reply not the top-level cast

oh I got inspired, I need allow people fold parent casts like hacker news.

Yup I use that a lot! They also have "next" but I find it too easy to get lost of I use that -- the 'collapsed' state acts as a "read" flag