Feature Request: Instead of truncating, send the message in batches.

[KoxSosen]

I did some testing regarding #196 . The feature added in the PR seems to work, however from a users perspective truncating the message means that they lose everything after hitting the limit. This isn't ideal in case of discussions with regular messages exceeding the limit, as their writer loses all text with no way of getting it back.

My proposed solution, would be to instead, that for each time the limit is hit, create a new message, and send it in batches. For this feature, a configuration option with a delay would be appreciated, to avoid hitting possible rate limits set by the server because of sending way too many messages under a short period of time.

[superlou]

Sometimes on other clients when trying to respond quickly with a link to the perfect image in a fast-moving conversation, I've accidentally copy/pasted a base64 image instead of an image source URL. I then rightfully get kicked for flooding. If an excessively long message is entered, would it make sense to warn the user so they need to press enter twice or some mechanism? Maybe that's best as a separate feature.