{{tag>featured}}
====== Post length and character limit: how long is too long? ======
The post length limit on Infosec.Exchange is 11,000 characters. This is possible because [[about:infosec_exchange|Infosec.Exchange runs]] on the [[faq:mastodon:glitch_soc|glitch-soc]] fork of [[faq:mastodon:|Mastodon]].

The standard Mastodon post limit is much lower at 500 characters, which is still longer than Twitter at 280, but shorter than Facebook at 33,000.

<div tip>With an 11,000 character limit, you could share the whole of the Project Gutenberg translation of War and Peace in a little over 300 posts, but don't.</div>

===== Don't force people to scroll past your wall of text =====

It's fine to write longer posts, but if they're longer than a few hundred characters, put them behind a [[faq:post_share:content_warning_how_to_use|Content Warning]] so people don't have to scroll past your giant wall of text. Repeated or egregious use of too-long posts may collide with [[rules:05_no_spam_no_excessive_promotion|Rule #5]].

===== Some other instances may not support long posts =====
Instance Admins have a certain amount of control to deploy their instances as they see fit, so the advice here is based on very limited testing.

If a member of Infosec.Exchange were to publish a toot in excess of the 500 character limit applied to another instance it will appear in the other instance trimmed with a ''Read more >'' notice after several hundred characters. When selected the toot appears in full, as per normal.

If posting at this length, one [[faq:post_share:content_warning_when_to_use|ought to use]] a [[faq:post_share:content_warning_how_to_use|Content Warning]] to avoid forcing users to hit a wall of text. If done, the toot will appear appropriately truncated.

This was tested with messages sent from Infosec.Exchange to another, non [[faq:mastodon:glitch_soc|glitch-soc]]-based instance with a 500 character limit.