#i3wm — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #i3wm, aggregated by home.social.
-
More #NetBSD thoughts:
I'm an #i3wm / #sway or #KDE #Plasma guy. I tried #OpenBSD's default wm for about a minute, but it was just too jarring for me. I also used #cwm for a while, and it's actually nicely configurable, but I eventually reverted to i3 on OpenBSD. I haven't tried Sway yet, but #Wayland's supposedly working in "Fish Linux" now. ;)
But #ctwm? Look, it's pretty ancient, and it's not a totally perfect fit for my worfklow, but I'm actually kinda diggin' it!
It's also probably the most attractive default GUI of any of the BSDs, considering that obsd gives you a pretty loud bright red or bright blue titlebar motif-looking thing (not knocking motif, just the primary color choice), and #FreeBSD gives you (checks notes) no GUI by default. XD
ctwm isn't quite as flexible as i3/sway, but it's just configurable enough to keep me coming back and tinkering away at it. The way the warpring function (alt+tab, in other words) works is pretty obtuse (only moving forward or backward in the window list, never re-ordering based on recency), but once I learned how to exclude windows (X11 classes or window titles) from the warpring, it became a ton more usable.
I also figured out how to enable active titlebar highlight (it drives me nuts when that's disabled or very subtle, how do you even not understand that basic tenet of usability?) and even how to assign an xpm image to the titlebar so it looks pretty.
Fun stuff!
I should post another screenshot. ;)
-
More #NetBSD thoughts:
I'm an #i3wm / #sway or #KDE #Plasma guy. I tried #OpenBSD's default wm for about a minute, but it was just too jarring for me. I also used #cwm for a while, and it's actually nicely configurable, but I eventually reverted to i3 on OpenBSD. I haven't tried Sway yet, but #Wayland's supposedly working in "Fish Linux" now. ;)
But #ctwm? Look, it's pretty ancient, and it's not a totally perfect fit for my worfklow, but I'm actually kinda diggin' it!
It's also probably the most attractive default GUI of any of the BSDs, considering that obsd gives you a pretty loud bright red or bright blue titlebar motif-looking thing (not knocking motif, just the primary color choice), and #FreeBSD gives you (checks notes) no GUI by default. XD
ctwm isn't quite as flexible as i3/sway, but it's just configurable enough to keep me coming back and tinkering away at it. The way the warpring function (alt+tab, in other words) works is pretty obtuse (only moving forward or backward in the window list, never re-ordering based on recency), but once I learned how to exclude windows (X11 classes or window titles) from the warpring, it became a ton more usable.
I also figured out how to enable active titlebar highlight (it drives me nuts when that's disabled or very subtle, how do you even not understand that basic tenet of usability?) and even how to assign an xpm image to the titlebar so it looks pretty.
Fun stuff!
I should post another screenshot. ;)
-
More #NetBSD thoughts:
I'm an #i3wm / #sway or #KDE #Plasma guy. I tried #OpenBSD's default wm for about a minute, but it was just too jarring for me. I also used #cwm for a while, and it's actually nicely configurable, but I eventually reverted to i3 on OpenBSD. I haven't tried Sway yet, but #Wayland's supposedly working in "Fish Linux" now. ;)
But #ctwm? Look, it's pretty ancient, and it's not a totally perfect fit for my worfklow, but I'm actually kinda diggin' it!
It's also probably the most attractive default GUI of any of the BSDs, considering that obsd gives you a pretty loud bright red or bright blue titlebar motif-looking thing (not knocking motif, just the primary color choice), and #FreeBSD gives you (checks notes) no GUI by default. XD
ctwm isn't quite as flexible as i3/sway, but it's just configurable enough to keep me coming back and tinkering away at it. The way the warpring function (alt+tab, in other words) works is pretty obtuse (only moving forward or backward in the window list, never re-ordering based on recency), but once I learned how to exclude windows (X11 classes or window titles) from the warpring, it became a ton more usable.
I also figured out how to enable active titlebar highlight (it drives me nuts when that's disabled or very subtle, how do you even not understand that basic tenet of usability?) and even how to assign an xpm image to the titlebar so it looks pretty.
Fun stuff!
I should post another screenshot. ;)
-
More #NetBSD thoughts:
I'm an #i3wm / #sway or #KDE #Plasma guy. I tried #OpenBSD's default wm for about a minute, but it was just too jarring for me. I also used #cwm for a while, and it's actually nicely configurable, but I eventually reverted to i3 on OpenBSD. I haven't tried Sway yet, but #Wayland's supposedly working in "Fish Linux" now. ;)
But #ctwm? Look, it's pretty ancient, and it's not a totally perfect fit for my worfklow, but I'm actually kinda diggin' it!
It's also probably the most attractive default GUI of any of the BSDs, considering that obsd gives you a pretty loud bright red or bright blue titlebar motif-looking thing (not knocking motif, just the primary color choice), and #FreeBSD gives you (checks notes) no GUI by default. XD
ctwm isn't quite as flexible as i3/sway, but it's just configurable enough to keep me coming back and tinkering away at it. The way the warpring function (alt+tab, in other words) works is pretty obtuse (only moving forward or backward in the window list, never re-ordering based on recency), but once I learned how to exclude windows (X11 classes or window titles) from the warpring, it became a ton more usable.
I also figured out how to enable active titlebar highlight (it drives me nuts when that's disabled or very subtle, how do you even not understand that basic tenet of usability?) and even how to assign an xpm image to the titlebar so it looks pretty.
Fun stuff!
I should post another screenshot. ;)
-
More #NetBSD thoughts:
I'm an #i3wm / #sway or #KDE #Plasma guy. I tried #OpenBSD's default wm for about a minute, but it was just too jarring for me. I also used #cwm for a while, and it's actually nicely configurable, but I eventually reverted to i3 on OpenBSD. I haven't tried Sway yet, but #Wayland's supposedly working in "Fish Linux" now. ;)
But #ctwm? Look, it's pretty ancient, and it's not a totally perfect fit for my worfklow, but I'm actually kinda diggin' it!
It's also probably the most attractive default GUI of any of the BSDs, considering that obsd gives you a pretty loud bright red or bright blue titlebar motif-looking thing (not knocking motif, just the primary color choice), and #FreeBSD gives you (checks notes) no GUI by default. XD
ctwm isn't quite as flexible as i3/sway, but it's just configurable enough to keep me coming back and tinkering away at it. The way the warpring function (alt+tab, in other words) works is pretty obtuse (only moving forward or backward in the window list, never re-ordering based on recency), but once I learned how to exclude windows (X11 classes or window titles) from the warpring, it became a ton more usable.
I also figured out how to enable active titlebar highlight (it drives me nuts when that's disabled or very subtle, how do you even not understand that basic tenet of usability?) and even how to assign an xpm image to the titlebar so it looks pretty.
Fun stuff!
I should post another screenshot. ;)
-
Всё, что вы настроили в Linux, можно было не настраивать
Я использую Linux 15 лет. Ну, то есть как использую: первые года три я его настраивал, а не использовал. Это разные вещи, и мне понадобилось позорно много времени чтобы это понять. Сейчас у меня Fedora. Из коробки. С GNOME. Почти без кастомизации. Я набираю в ней код, сижу в браузере, иногда монтирую видео для внутренних демок. Всё работает. Пятнадцать лет назад я бы от такого описания плевался. Как это «из коробки»? А где i3? Где polybar? Где 400 строк .vimrc? Где кастомный скрипт на баше который при подключении второго монитора переключает раскладку DPI и температуру цвета? Ну вот, нету. И ничего не сломалось.
https://habr.com/ru/articles/1044236/
#linux #gnome #i3wm #dotfiles #fedora #продуктивность #прокрастинация #оконный_менеджер #тайлинг #окружение_рабочего_стола
-
@Tom Cole It is available everywhere AFAIK.
But: The convenient black "Alt" button in the corner is exclusive to Mastodon's Web interface plus maybe a few phone apps that have adopted it since. Technically speaking, a UI element to show alt-texts is completely unnecessary because alt-text is only a stand-in for the image itself, for when the image cannot be seen for whichever reason. The alt-text as an extra source of information is a purely Mastodon thing where people use it to expand their meagre 500-character limit by up to another 6,000 characters.
Just about everywhere else in the Fediverse, there is no button for showing alt-texts. That's also because there's nowhere in the Fediverse where people really need alt-texts to write around their tiny character limits, so that alt-texts can be what alt-texts are literally everywhere outside of Mastodon: a stand-in for the image and nothing more than that.
The normal way in the Fediverse (and other social networks and social media) for sighted people to access an alt-text is by moving the mouse cursor upon the image and hovering in there, and the alt-text pops up. The alt-text is thetitletag at the same time. This has been the case on Mastodon before, I think, version 4.4 as well. I guess Mastodon changed that because just about everyone on Mastodon is on phones, and you don't have a mouse cursor on a phone, so you have to long-press on the image which is a not very intuitive thing to do.
Here on Hubzilla where I'm commenting from right now, the alt-text still is thetitletag as well. In order to read an alt-text, the mouse cursor has to be hovered above the image. And Hubzilla has no alternative to its Web interface, only different themes for the Web interface. There is no phone app, at least none worth speaking of.
Also, on Hubzilla, we don't need to use alt-texts to write around character limits. Our character limit is 16,777,215, and that's the maximum size of the database field for the message text. Actually, on Hubzilla, alt-texts are included in these over 16 million characters as opposed to separate data fields. Thus, sighted Hubzilla users have no use for alt-texts whatsoever. Thus, there's no reason to make opening alt-texts easier (as if that was Hubzilla's only UI issue). Thus, there's no "Alt" button, and there will never be one.
It's just about the same just about everywhere else from Misskey (hard-coded 3,000 characters) to Akkoma (configurable 5,000 characters) to Friendica (same limit as Hubzilla) to (streams) and Forte (over 24 million characters) to pure long-form blogging stuff like WordPress, Ghost, Write Freely and Plume.
Now I ask you: What are people supposed to do whose both hands had to be amputated due to some accident? Or people with deformed hands who can neither use a smartphone nor a computer mouse nor a trackball nor any other pointing device on a computer? Who operate their computer with e.g. a headpointer, a plastic stick strapped to their forehead with which they poke the keys on their computer? And who are in the Fediverse, but not on Mastodon? How are they supposed to open an alt-text with only a keyboard as an input device?
Or how about people with a severe tremor? Who have big troubles moving a mouse cursor over an image and then keeping it there because it keeps slipping away? Who probably operate their computers via the keyboard and only the keyboard, too?
Or, a wholly different example, how about those who use Linux with a super-minimalist, keyboard-only tiling window manager? Who do have a GUI (albeit a very frugal one), who do use graphical Web browsers, but who deliberately, intentionaly, do not have any kind of pointing device? Who, nonetheless, are ten times faster with only keyboard shortcuts than you and me are with a mouse? How are they supposed to move a mouse cursor over an image without a mouse?
This is something that many Mastodon users don't know:- Not all Fediverse frontends have an "Alt" button.
- "Alt" buttons make no sense in the non-Mastodon Fediverse. In the non-Mastodon Fediverse, the character limits are so high that nobody has to use alt-texts to write around them. Expanding the character limit with alt-texts is a 100% Mastodon-only thing that simply doesn't translate to places with thousands or millions of characters and never will.
- There are other disabilities out there than visual impairments and neurodivergence. Even in the Fediverse.
- Not everyone in the Fediverse uses a pointing device of whichever sorts.
Oh, and there's one more thing: Misskey and its various forks (Sharkey, Iceshrimp-JS, CherryPick etc.) all have a character limit of 512 for alt-texts. They should enforce it the same way as Mastodon enforces its 1,500-character limit for alt-texts, namely by truncating longer alt-texts. This is bad enough already.
However, they all have the same nasty bug that still hasn't been fixed yet AFAIK: Instead of truncating longer alt-texts, they delete them. So if you describe your image in an alt-text of more than 512 characters, users on Misskey, Sharkey & Co. will never know that your image is supposed to have an alt-text. Instead, they may think that you were too lazy to describe your image. And if you use the alt-text to explain your image in over 512 characters, this explanation will never reach users on Misskey, Sharkey & Co.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #i3 #i3wm #Disability #A11y #Accessibility -
@victorhck ¡De simple nada! Yo ni siquiera tenía idea de que se pudiera hacer.
Pero me surge la duda: ¿esto interfiere en las combinaciones de teclas de los programas que están corriendo? Si es así, solo valdría en escritorios vacíos, ¿no?
#i3wm #novato