@chucker @davemark The biggest one is that you limit toots to 500 characters even though qoto.org (the instance I use) supports 65535 character toots.

But the second biggest one is that the timeline jumps around so it is much too easy to loose your place. It is impossible to read the Public timeline, but even in your home timeline, as new messages come in it jumps ahead. This behavior alone is enough to make me never use #Mastonaut. If I am reading a toot and I get called away and then come back an hour later or a day later or a week later, I want it to still be on the last toot I read, and allow me to scroll up and down from there. If you are not touching the mouse or the keyboard, the timeline should never move on the screen for any reason, and especially not as new toots come in. Most #Mastodon clients get this wrong to some degree but Mastonaut is the worst I have found for this problem.

Other things I would like to see are the ability to quote all or a portion of the original toot in a reply, the ability to edit toots after they have been sent (in case you make an error), and the ability to see a list of all the #hashtags you are following and to add or remove from that list. But the first two things I mentioned above are the things that really turned me off about Mastonaut.

@Lunatech thanks for answering

1) toot limit: does the preference not work for you? (It’s in the Accounts tab, I think)

Also, I think qoto is on an old version of Mastodon. As soon as they switch to 4.x, Mastonaut 1.6 will be able to fetch the limit from the API. https://docs.joinmastodon.org/entities/Instance/#max_characters

2. Yep, timeline/scrolling behavior needs work.

@chucker Oh, yes the preference works, I had just never found that before. Thanks for mentioning that!

@chucker @davemark Oh one other thing I forgot, when displaying images in the timeline if they are not a specific aspect ratio you chop off the tops and bottoms of the image. I cannot begin to express how irritating that is. I know some #Mastodon instances do that too, and it sucks. I wish there was a option that would either let you display the full image or a thumbnail, but even if it's a tumbnail I don't want the top and bottom of the image cut off unless maybe it is ridiculously tall compared to the width (maybe not let a 1 px wide by 100000 px high image display, but don't chop of the top and bottom of normal portrait images!).

@Lunatech yes, the forced aspect ratio has been pointed out by a few people, and I’ll be making that optional in some future release