Cameron Builds

Introducing: Seemore's "Thread to Frame" Tool 👀

We teased this Monday, saw the demand, and decided to skip a beta and just freaking ship it.

It's as simple as...

1. Cast your thread
2. Input the warpcast url below
3. Cast the new url to display your frame!

Introducing: Seemore's "Thread to Frame" Tool 👀

We teased this Monday, saw the demand, and decided to skip a beta and just freaking ship it.

It's as simple as...

1. Cast your thread
2. Input the warpcast url below
3. Cast the new url to display your frame!

https://seemore.tv/creatortools/fcthreads/

weird internet kid. helping Creators with /seemore. yapping on /okbanger. curating in /creators and /cameron. dev + veteran + HBS. 
seemore.tv/cameron 🫡

For proper threading, should I:

A) submit subsequent messages (2, 3, 4, 5) as a reply to my first reply, or
B) submit subsequent messages as a reply to the message I'm originally replying to, or
c) submit subsequent messages as a reply to the preceding message (2 replies to 1, 3 replies to 2, etc.)?

/fieldway: eLearning on how to lead software teams.

CoinDesk Director of Product Management.

Casts are my own and don't represent anyone but me.

Right now I believe it has to be:
A. A new top level cast from you
B. The next cast as a reply to the top level one
C. The rest of the casts all replying to the previous one

And if you do 2 replies on your top level, we default to the longest chain

(i need to recheck the code though we shipped a lot last week haha)

So B replies to C, then C replies to B, then D, E, F, G, H, etc. all reply to C?

Ah, gotcha. So it's replies all the way down 👍

Sorry no - think recursive replies like classic bird app threading format