
Currently it’s a bit cumbersome to create a Twitter post containing of a couple of Tweets - like a thread.
It’d be awesome to be able to define whole thread in a single text area presented in the “Create” view instead of trying to do that with follow-up comments view. It’s hard to manually split the text and do all the stuff.
You could inspire with a experience of Typefully.app where you can simply split a longer text to multiple tweets with doubled new line.

Upvoted this! Chirr’s implementation is also a source of inspirtation.

This was suggested two years ago! WOW
Full screen mode while drafting twitter threads ( check hypefury for the same functionality )


Same for telegram please. the limitation of messages for text posts are 2000chars. media captions 1000.



Wonderful convenient solution!

I note that making threads for Mastodon defaults to my default language for each post, instead of the expected behaviour, which is to follow the set language in the first post of the thread.

Also, I’m still unable to paste pictures or drag them in any threaded posts as I am able in the first post. I can only use the upload button which can be cumbersome.

Third point of feedback, while just playing around with it: while writing threads, I often just come up with an extra point that I want to insert. This is impossible. If you want to add an extra point, you’ll have to delete all posts in thread and readd them. The desired behaviour would look like this:
Existing thread: 1 - 2 - 3 - 4 - 5
Added extra point: 1 - x - 2 - 3 - 4 - 5
This should just be possible by adding an extra threaded post at any point in the thread.

Why would I move to a new layout that appears to have reduced funcationality?

Hi @Michael Denny , any specific feature you’re missing? We have only added new functionalities without removing any. Please let us know here or via chat/email ([email protected]). Thank you.

Update
This is what we have planned this quarter to further improve threads in Publer:
Please let us know if we’re still missing something.
Thank you!

Consider a “dogfooding” approach to the API. If your own app was using your own API to deliver new features, your API would always provide new features instead of exposing the feature being an afterthought… I have just discovered that the web interface do have a thread creation tool… It is just not exposed in the API… this is sad because, I would use the thread creation from API… in the web, it is useless to me. If you want to look at the best dogfooding approach that I know, look at Kraken crypto exchange. Their own app are built on top of the API