Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
faq:post_share:post_length_character_limit [2022/11/12 05:45] – removed - external edit (Unknown date) 127.0.0.1 | faq:post_share:post_length_character_limit [2024/05/01 19:44] (current) – [Don't force people to scroll past your wall of text] Corrected the link discrepancy (text says rule 5, link says rule 7). Checked with Jerry, should referr to Rule #5. Addjusted accordingly. onion | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{tag> | ||
+ | ====== 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: | ||
+ | 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' | ||
+ | |||
+ | ===== Don't force people to scroll past your wall of text ===== | ||
+ | |||
+ | It's fine to write longer posts, but if they' | ||
+ | |||
+ | ===== 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 '' | ||
+ | |||
+ | If posting at this length, one [[faq: | ||
+ | |||
+ | This was tested with messages sent from Infosec.Exchange to another, non [[faq: |