Misskey and Lemmy failed to accept a ca. 50,000-character post; CW: long (1,315 characters excluding markup), code blocks, non-Mastodon Fediverse meta
Artikel ansehen
Zusammenfassung ansehen
Okay, this is new.
I know that Misskey has a hard-coded limit of 3,000 characters for writing posts.
But I've just discovered that two Misskey instances and one Sharkey instance I'm connected to failed to accept
a post of mine tonight because it is too long. That post is a bit under 49,000 characters long. That is, both alt-texts included, it it is a bit over 50,000 characters long.
The post wasn't cropped. It was rejected entirely.
The delivery report lists this chopped-off error message for all three instances:
delivery rejected: 413 {"statusCode":413,"code":"FST_ERR_CTP_BODY_TOO_LARGE","error":"Payload Too Large","message":"ReSimilarly, lemmy.world rejected the post which wasn't even targetted at any community there with:
delivery rejected: 413 <html> <head><title>413 Request Entity Too Large</title></head> <body> <center><h1>413 Request Entity Too LarNow I'm wondering what the limit could be. I think I should pay attention to more delivery reports of longer posts.
The flagship instance misskey.io failed with a 403, so that might have been caused by internal issues.
At the same time, at least some Firefish instances did accept the post. Remember that Firefish is a Misskey fork.
#
Fediverse #
CharacterLimit #
CharacterLimits #
Misskey #
Sharkey #
Lemmy #
Long #
LongPost #
CWLong #
CWLongPost
