Conversation:
Notices
-
@roka As I remember, #AndStatus gets the limit from Mastodon's configuration...
Please try to go to AndStatus Settings -> Accounts -> Manage Accounts -> Select your account and then Reverify credentials.
Do you see updated toot length limit?
- AndStatus repeated this.
-
@andstatus Sadly it does not work, the limit still shows up as 500. I am on a Pleroma instance though, as I understand it exposes max post length with max_toot_chars property accessible from /api/v1/instance (which is what glitch-soc used.)
-
@roka Yes, really, this function is not implemented yet for #Mastodon. Will add ASAP and let you know.
-
@roka I added a feature to take a toot length limit from the instance's confirm (updates on "Reverify credentials")
Please check #AndStatus v.52.00 Beta https://github.com/andstatus/andstatus/issues/456
@thefaico@quitter.se
-
@roka I fixed this in v.52.01, please check
https://github.com/andstatus/andstatus/issues/456
-
@roka Looks like some deeper hardcoded limit in #AndStatus.
Than you for reporting - will fix this also. However I cannot test this 65535 characters anywhere: tried and failed to register at your instance...
-
@roka In the time of gigabytes given for free limiting a post even to 5000 characters looks unexplainable :-)
I think that moving from 140 characters to kilobytes of text may show the we are starting to use fediverse to discuss complex subjects, which don't fit in a paragraph...
XXX posts can live with 500 characters evidently, using all that space for their hashtags :-)