Hubzilla delivery report revealed that Misskey and the Forkeys refuse to accept 26,000-character posts; CW: long (1,300 characters), Fediverse meta, non-Mastodon Fediverse meta, character limit meta
Artikel ansehen
Zusammenfassung ansehen
I've recently sent a post with 26,000+ characters. The delivery report tells me that every last *key instance had problems with it.
They often rejected it entirely with an error 413. (
delivery rejected: 413 {"statusCode":413,"code":"FST_ERR_CTP_BODY_TOO_LARGE","error":"Payload Too Large","message":"Re)
This means that Misskey and the Forkeys have a hard limit not at 50,000 characters as I previously thought, but at 25,000 characters, 20,000 characters or even lower, and they refuse to accept any incoming objects that are longer. I mean, I know that Mastodon has a 100,000-character limit that acts the same, and I think I've read that so have Pleroma and Akkoma, but
that limit has to be ridiculously low. Essentially, I can barely send virtual world pictures with sufficient image descriptions out to Misskey and the Forkeys.
Of course, this stays largely unnoticed because there are only so many users in the Fediverse who a) write posts that grow that long and b) have access to delivery reports for their own posts. Another advantage of being on Hubzilla.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
CharacterCount #
CharacterLimit #
CharacterLimits #
Mastodon #
Pleroma #
Akkoma #
Misskey #
Forkeys #
Firefish #
Iceshrimp #
Sharkey #
Catodon #
Hajkey
