Mastodon: 500 characters, Misskey: 3k characters, (streams): 65k or 24M characters; CW: long (over 1,600 characters), Fediverse meta, non-Mastodon Fediverse meta, quote-post
Artikel ansehen
Zusammenfassung ansehen
TIL that (streams) has a defined character limit of 24 million characters, but until now, the database limits the size of the object to a bit over 65,000 characters. The latter limit is being raised for new installations, and existing servers can raise that limit, too.
That's over 130 vs 48,000 Mastodon toots or more than 20 vs 8,000 Misskey notes.
Mind you, (streams) counts characters differently from Mastodon. Links aren't always 23 characters, they're as long as the URL plus the link code. The embedding code for in-line images, image URLs and alt-text included, is part of the post text. In general, all BBcode/HTML/Markdown counts into the character count. I'm not sure whether titles and summaries add to the overall character number, but at 24 million characters, that shouldn't make a difference.
Unfortunately, I no longer have the delivery report of the one time I exceeded the 65,000 character limit so I don't know how (streams) handles longer posts from outside.
The long post triggered something we haven't seen before... we allow the post body to be up to 24M, but the obj is capped at 65K. This was acceptable a year ago, but with conversation containers we put the entire post body into the object when sending a collection activity. So you're getting capped at 65K. You can change the item.obj column in the database and make it 'mediumtext'. I'll put this in the install database schema for new installs.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
QuotePost #
QuoteTweet #
QuoteToot #
QuoteBoost #
CharacterLimit #
CharacterLimits
