Few days ago I tried to explain a bit why having the compositor box in sidebar matter.
A moment later new nightly (2026-10-22) appeared. Now i’m stuck much more because as I understand the main reason to take compositor out of sidebar is that it needs to be larger.
What we can see in that nightly is more wasted space. :>
I’m using small laptop screen 1920×1080px here how it looks:
Really want more space in sidebar? Make it 600px wide (or better ake it coinfigurable 20-35% of the screen width) and put compositor there… it will still give more space for rest three (!) columns we know from mastodon-4.8
As I understand we are talking about user experience, and it is how to build UI to give users all tools they need in right place.
Deck interface called here advenced interface is as I understand adressed to users who are already well-established within the system. Perhaps we should take these users at their word when they say that, while some cleaning and refinement were indeed necessary, the interface was in principle very well thought out?
I’ve sketched out how the screen could be divided - in my view - so that the post editor fits into the sidebar. Next to the icons for the home screen and “explore” I’d include an icon for a panel containing various streams (local, global, custom, hashtags) and perhaps others. This provides more space for text and the editor, without obscuring anything.
What we have now (Mastodon v5.0.0-nightly.2026-11-17) looks nice but is it lack of space on sidebar for compositor still the case?
What about moving the version information to the place where tusky lives? Now we can have huge pace for compositor on sidebar! It is really convinient to have the compositor still open while browsing posts, and there is large place so… ?
There can be even more if you move channels and hashtags to separate panels and hide it under small icon between those 5 on top of sidebar, or maybe even better on side of explore and saved posts icons/links.
Hey @wariat, thanks for the sketches and for following each nightly so closely. It’s clear you’ve put real thought into this.
To make this easier for others to find and vote on, I’ve retitled the topic around the core problem: “Advanced Web Interface (Deck View): no room to write while keeping columns visible.” Your proposals for solving it, like a wider or adjustable sidebar and moving the version info, fit right here.
The streams panel and the separate hashtag and channel panels are their own requests. If you’d like them to get votes, please post each one as a new topic and link back here. More on why in our App Feedback Guidelines.
Separate panels for followed hashtags and custom feeds are part of this idea if we think about making more space on sidebar, but ok I’ll open new topic for this as IMO it will make it more usable in my opinion.
I understand why you’d like to put the Composer in the left-most column, like before. It allows for composing a post while browsing the other columns.
However
(1) putting a white input box in the left column is quite ugly (never seen that on other platforms) …
(2) you need to make the left column wider (or at least expandable by dragging) to fit a large enough Composer box …
(3) moving the server and software info to the right-column doesn’t seem like a clean solution …
No offense @wariat, but it just doesn’t feel right to me.
Why not make the Composer box dockable on top of the ‘Home’ column (taking like 20% of the column height)? Or if the user doesn’t like that: make it dockable on top of (20%) OR in the columns to the right? That way, the ‘content’ columns can be made wider (easier to view content and compose a post) and the left navigation panel can be kept smaller (mind you, I use vertical tabs in Firefox, which adds another ‘column’ to the left of the Mastodon interface).
To the UX team: in the current modal implementation (Mastodon v5.0.0-beta.1+pr-41738-336ed0f - already an improvement over earlier versions!), it would be useful to make the Composer’s input field expandable by dragging. See for example Reddit:
Things has changed with collapsible sidebar of v5.0.0-beta.1+pr-41754-9d7b2c3 but to not leave questions without answers and… future ideas in that little brainstorm at the last paragraph of this post.
Indeed, this isn’t something you often see on other platforms. For me, this is precisely why I’ve considered for long Mastodon’s interface to be far ahead of those other platforms – because the editor is always accessible, allowing you to compose a message while the rest of the interface remains fully functional.
In Mastodon 5 it is IMO wide enough, but where we are today with collapsible sidebar things changed…
Why? It is not something you have to have on hand all the time, and the “Tusky¹ panel” looks like perfect place.
BTW Tusky himself while standing right now on last panel from right side should look left on his kingdom not screen edge. And this is really important dear Mastodon Team!
¹ His name is Tusky right? If not, please excuse me Mr. Mastodon.
Now. The idea of placing the composer in the upper part of the main panel doesn’t seem perfect to me, but it is much better than what we have right now (almost everything is better :>) with composer floating over shaded interface (v5.0.0-beta.1+pr-41754-9d7b2c3 with collapsible sidebar).
So maybe, while sidebar is collapsible there is a place for composer in whole new column. NOT the switchable one (those with Tusky) but new/extra one opened while creating message on side of it. This way we can have editor opened all the time while creating message with normal access to rest of the UI. On small screen it will fit when sidebar is collapsed, on large screen it will be just the next column which appear when you click new post/reply button. The system of adding/removing column is ready, so it should not collide with anything. Is it a kind of solution?
“To the UX team: in the current modal implementation (Mastodon v5.0.0-beta.1+pr-41738-336ed0f - already an improvement over earlier versions!), it would be useful to make the Composer’s input field expandable by dragging.”
@TootMcToot smart idea! Out of scope for 5.0 but a reasonable request. Please add this as a separate topic so it doesn’t get lost in the weeds. See App Feedback Guidelines for more.
I’ll come back to this when I have more time, but one quick thing about the advanced view: remove scrollbar-gutter: stable from the html for it. It’s not the page that scrolls there, but the individual columns, so that gutter ends up being just ugly-looking wasted space. I can see the point for it in the single column layout case, but not for the multi-column one.
Sigh. Allowing it to be fully usable was a temporary measure while working to introduce a less usable alternative.
To clarify: I’m fine with the sidebar collapsing, though I rarely ever want to do that, scrolling is just less friction, I don’t have to click the tiny space of a button and the sidebar can go offscreen completely. Not being able to scroll it, collapsed or not, is something I don’t like.