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

Closed
fallerOfFalls opened this Issue Apr 10, 2017 · 11 comments

Comments

Projects
None yet
7 participants
@fallerOfFalls
Copy link

fallerOfFalls commented Apr 10, 2017

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:

Zero-one-infinity is a design rule-of-thumb that is often ignored - usually to the detriment of the project.
Simply stated: You will either need zero of a thing, one of a thing, or an arbitrary number of the thing.
Programmers and architects ignore this at their own peril. Arbitrary fixed limits are a CodeSmell. --WikiWikiWeb


  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.

@wxcafe wxcafe added the question label Apr 10, 2017

@wxcafe wxcafe assigned wxcafe and Gargron and unassigned wxcafe Apr 10, 2017

@wxcafe

This comment has been minimized.

Copy link
Contributor

wxcafe commented Apr 10, 2017

Misclicked. Assigning @Gargron so he can explain what his reasoning is

@alexgleason

This comment has been minimized.

Copy link
Contributor

alexgleason commented Apr 11, 2017

Isn't this a constraint of GNU Social anyway?

@yiskah

This comment has been minimized.

Copy link
Contributor

yiskah commented Apr 11, 2017

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.

@wxcafe

This comment has been minimized.

Copy link
Contributor

wxcafe commented Apr 11, 2017

Thank you, marking this wontfix and closing then

@wxcafe wxcafe added the wontfix label Apr 11, 2017

@wxcafe wxcafe closed this Apr 11, 2017

@fallerOfFalls

This comment has been minimized.

Copy link

fallerOfFalls commented Apr 12, 2017

Thank you @yiskah for explaining. Mental itch satisfied.

@Shreewebs

This comment has been minimized.

Copy link

Shreewebs commented Sep 4, 2018

Can Someone guide on how to increase limit to 600 Please?

@Laurelai

This comment has been minimized.

Copy link

Laurelai commented Sep 4, 2018

Edit the following files

app/javascript/mastodon/features/compose/components/compose_form.js
app/validators/status_length_validator.rb

@Shreewebs

This comment has been minimized.

Copy link

Shreewebs commented Sep 5, 2018

@Laurelai Thank you, I have already modified those files to 600 but no luck.
Can you please suggest some other solution?
OR is there any service that needs to be restarted?

@Laurelai

This comment has been minimized.

Copy link

Laurelai commented Sep 5, 2018

Search for every instance of "500" in those files then change them to "600" then run RAILS_ENV=production bundle exec rails assets:precompile

@Shreewebs

This comment has been minimized.

Copy link

Shreewebs commented Sep 5, 2018

@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 Gemfile: no implicit conversion of Symbol into Integer. Bundler cannot continue.

from /home/mastodon/Gemfile:4

-------------------------------------------

source 'https://rubygems.org'

ruby '>= 2.3.0', '< 2.6.0'

-------------------------------------------

@Shreewebs

This comment has been minimized.

Copy link

Shreewebs commented Sep 6, 2018

Please assist!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment