The *one* thing I've found troublesome about setting up Mastodon so far is the char limit; it's not a vital change, sure, but I *really* don't like being told my single paragraph is too short in the middle of a rant and having to split it into multiple sections just so it "looks nice" in the UI.

There was a PR to implement a char limit variable (github.com/tootsuite/mastodon/) a while ago - but is there any drawback to it other than "the way our UX is designed"? Because I'm really not getting it.

Follow

The UX can be changed, right? Use short media by default, provide an alternative (some form of "expand" button, like in gmail's compose interface?) for longer posts... same with how articles work in Hometown (github.com/hometown-fork/homet).

And besides, "the fediverse" doesn't bend to Mastodon's UX. Other software & instances (like writefreely.org/) already use long-form posts - and IMO Mastodon that should support them. Otherwise, it's bad UX.

Also, char limits are bad UX.

@james yeah, the thing is, mastodon in several cases supports content (like longer text and even formatted text) but just chooses to limit it for it's own users. I think it's important to remember that Eugene _wants_ it to be twitter, so if that's the place he's coming from, that influences where the software will go. I'm personally loooking for a AP feed reader, that I can also easily publish and extend.

Sign in to participate in the conversation
Horrific.Dev

A group of individual developers and enthusiasts with a focus on independent services, software, and technology.