Conversation

Notices

1. Embed this notice
   Back to the Alan (alan@blimey.social)'s status on Tuesday, 26-Sep-2023 10:27:29 JST Back to the Alan

   • Alex Gleason

   @alex I’m on Soapbox v3.2.0-72065ff and despite setting a character limit of 5,000 in the backend, I’m only able to post to a limit of 500. This has never been an issue with Soapbox before. Any idea what could be limiting me?

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 26-Sep-2023 10:27:28 JST Alex Gleason

     in reply to
     @alan We only read from configuration.statuses.max_characters now. Looks like your api only has max_toot_chars. Wasn't this the one where you switched to Akkoma? Open an issue. Wasn't aware modern backends still don't expose the new value.
   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 26-Sep-2023 10:50:43 JST Alex Gleason

     in reply to
     @alan max_toot_chars is the unofficial name for the field. The official name is configuration.statuses.max_characters. I changed Soapbox to read the new value without realizing Akkoma still renders the old value.
   • Embed this notice
     Back to the Alan (alan@blimey.social)'s status on Tuesday, 26-Sep-2023 10:50:51 JST Back to the Alan

     in reply to

     • Alex Gleason

     @alex You’re right, I’m using Akkoma. However, the Mastodon front end shows/allows the correct amount of characters so if it was a read error, the error would be present in all front ends..?

   • Embed this notice
     Alex Gleason (alex@gleasonator.com)'s status on Tuesday, 26-Sep-2023 12:30:23 JST Alex Gleason

     in reply to
     @alan Yes. You updated the frontend. If you want things to stay the same, don't update.
   • Embed this notice
     Back to the Alan (alan@blimey.social)'s status on Tuesday, 26-Sep-2023 12:30:24 JST Back to the Alan

     in reply to

     • Alex Gleason

     @alex Is that a recent thing? It’s always works before….