@hongminhee@fosstodon.org @thisismissem@hachyderm.io thanks both!

@mmorschel Habe ich kein Problem mit, das du dir #Gnome gönnst. Ich habe das sehr oft versucht, aber das Konzept halte ich persönlich für völlig falsch.Aber, das schöne an Linux, wir können es uns aussuchen. Auf der Arbeit werde ich zu diesem M$ Schrott gezwungen.

@herrorange Thank you!

@juse keep in mind that hiding toolbar buttons away behind overflow menus broadly decreases usage of formatting tools. It's not necessarily a bad thing, but something to consider. Also when tools are dynamically drawn (e.g. on hover over some highlighted text), that breaks accessibility guidelines. a11y isn't why we had a toolbar, although it coincidentally does satisfy accessibility constraints. I am all for a more streamlined view, and perhaps the default composer isn't there yet, but I also very much dislike UIs that constantly shift elements in and out depending on UI state. A clean visual field is my preference, and static toolbar buttons, despite taking up space, still work for me.

@silverpill@mitra.social that line item is in regards to our effort (mainly @darius@friend.camp's!) to get the Mastodon devs on board with relaxing their rather strict validation for non-note objects (basically, no html at all, leading to implementors all sending as:Note). We're starting to make some progress!

@kainos looks like you put those widgets in your global container. Try moving them to categories.tpl