#Feature Request - option to send messages longer than single message character limit

[dualhammers]

Since GNU Nano has no visualization of character count it's easy to go over the character limit without realizing it. It also makes it difficult to figure out where in a message to split the character count.

Being able to have tut intelligently split the message at the character limit and send subsequent sections as threaded replies would be a wonderful addition.

[RasmusLindroth]

This would be a nice feature, but it doesn't seem like other clients are doing this. My concern is that splitting the message at the "right" place will be difficult. But in the new release I've included how many characters you have left till you reach the limit. You still has to quit your editor, so I agree the problem still exists.

[mmahmoudian]

I suggest if this feature (which imho is super handy and useful and all mastodon clients should implement it) is implemented, it would be almost critical to be able to define the characters to connect the threads. I propose having two strings in the config file, one for the end of a toot that is not the last toot in the thread, and one for the beginning of the toots that are not the first toot in a thread. For instance I personally use "👇🏼🧵" and "☝🏼🧵" since people usually boos the toot that they think is critical, but their followers will not given proper context, so having the indicators are critical imho.

[Oblomov]

My concern is that splitting the message at the "right" place will be difficult.

One possibility could be to allow the user to specify where to split the long messages. The app can still verify that the chunks don't overflow the server's character count (before posting), and allow the user to go back to editing in the overflow case.

Of course if multi-post thread posting is supported, it would be ideal if there was a way to add media, CWs etc at later posts in the thread too. I've been working on adding a similar feature to toot (which I've been using so far), using YAML-style metadata before each chunk.

[omnivagant]

The aerc email client, also written in go, use a couple of lines above and below your editor, to show you things like what server you're connected to and parts of the email header, perhaps tut could do something similar? Then you could at least occationally write to your temporary toot file and have tut show the character count without you having to exit and re-enter the editor.