4) You know what I'd like to see? Threads. 🧵 That's something real writers often really like.

But the guy who wants to build it for me is now busy trying to figure out tweet forks. šŸ¤¦šŸ»ā€ā™€ļø

Reply to this note

Please Login to reply.

Discussion

define what you mean by Threads

Threads somehow are a huge blindspot for devs.

It was the n°1 reason why I liked Twitter.

I don't know 1 client that displays them properly, let alone incentives their creation on the "New Post" screen.

nostr:nevent1qvzqqqqqqypzp22rfmsktmgpk2rtan7zwu00zuzax5maq5dnsu5g3xxvqr2u3pd7qyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qqsxuhux83rxtxmn5duqpefmzt092mmkpc0vypcp54rv0hplj0smhpcnq785p

They gave us tweet-forks instead.

And now, they're like, "Please, clap."

Me personally I'm a threads hater... It's basically just a blog post split into > 20 different chunks. The reading experience on Twitter was terrible unless you used TwitLonger to turn it back into a continuous text again.

Nostr has long form content which obviates the need to do this in the first place. Having the thread as a single article in markdown with headlines and such is about 1000x more pleasant to read IMHO.

You can just have an option to read it, either way. šŸ¤·ā€ā™€ļø

The goal of threads is to allow people to interact with specific parts of a longer entry, and to encourage writers to think in concise ideas.

šŸ’Æ

Take away those limits and you remove the high signal great threads typically have.

Displaying them as a actual threads also offers the most efficient ways of interacting and sharing.

However you choose read them, if that's your main goal, is up to you (especially on an open protocol).