When I moved to my own Mastodon instance, I applied the patch to increase the limit from 500 to 5000 characters, which basically all the small-scale instances do (and should really be configurable, but the devs are being obstinate).
-
When I moved to my own Mastodon instance, I applied the patch to increase the limit from 500 to 5000 characters, which basically all the small-scale instances do (and should really be configurable, but the devs are being obstinate).
I don't think I've exceeded 500 in the last few days yet. On Fosstodon, I often found 500 to be limiting but not oppressively so. But actually using all 5000 would be way too long for short form writing IMHO.
(460 characters)
-
When I moved to my own Mastodon instance, I applied the patch to increase the limit from 500 to 5000 characters, which basically all the small-scale instances do (and should really be configurable, but the devs are being obstinate).
I don't think I've exceeded 500 in the last few days yet. On Fosstodon, I often found 500 to be limiting but not oppressively so. But actually using all 5000 would be way too long for short form writing IMHO.
(460 characters)
@ryan totally agreed the limit should be configrable. i wrote about the obstinacy in https://privacy.thenexus.today/a-tale-of-two-prototypes-2/
-
@ryan totally agreed the limit should be configrable. i wrote about the obstinacy in https://privacy.thenexus.today/a-tale-of-two-prototypes-2/
@thenexusofprivacy At the very least, it seems now that the limit is consolidated to one place (MAX_CHARS in app/validators/status_length_validator.rb). I found guides from a few years ago where it was hardcoded in a half dozen different places. (No idea if this change was made in spite of the devs' desires, or was the byproduct of another refactor.)
-
@thenexusofprivacy At the very least, it seems now that the limit is consolidated to one place (MAX_CHARS in app/validators/status_length_validator.rb). I found guides from a few years ago where it was hardcoded in a half dozen different places. (No idea if this change was made in spite of the devs' desires, or was the byproduct of another refactor.)
@ryan progress is good! although hmm that also makes the implementation of being able to control it from the admin dashboard a lot easier so there's even less of an excuse ...
