New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove the toot character limit entirely #1446
Comments
Misclicked. Assigning @Gargron so he can explain what his reasoning is |
Isn't this a constraint of GNU Social anyway? |
Mastodon is a micro-blogging platform. If there wasn't a character limit, it would just be a blogging platform. This would also be very easily abused, even with collapsible posts, as it it could affect server load. An important design principle is that every post is roughly the same height, which creates a good UX. While some instances do modify their code to change the character limit, this is not officially supported because equality of service is one of the principles of how Mastodon decentralization is intended to work. Using one instance should be roughly the same as another when it comes to the software. |
Thank you, marking this wontfix and closing then |
Thank you @yiskah for explaining. Mental itch satisfied. |
Can Someone guide on how to increase limit to 600 Please? |
Edit the following files app/javascript/mastodon/features/compose/components/compose_form.js |
@Laurelai Thank you, I have already modified those files to 600 but no luck. |
Search for every instance of "500" in those files then change them to "600" then run RAILS_ENV=production bundle exec rails assets:precompile |
@Laurelai I have done but it seems to be an error:/home/mastodon# RAILS_ENV=production bundle exec rails assets:precompile [!] There was an error parsing from /home/mastodon/Gemfile:4-------------------------------------------source 'https://rubygems.org'
------------------------------------------- |
Please assist! |
@Shreewebs you have a typo somewhere.. run |
Why is there a character limit?
Surely there must be a better way of getting people to cut to the chase, or getting that "brief exchange" user experience than arbitrarily limiting the number of characters.
Toot length regulation should be a social issue; it shouldn't be the software that regulates how long your toots are. However it might be good to hide the bulk of toots that are longer than your screen (and perhaps indicate to the user that they are really going on and on and that most of their toot will be hidden. Soft limits are good.
And don't forget the zero-one-infinity rule:
The text was updated successfully, but these errors were encountered: