home.social

#i3 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #i3, aggregated by home.social.

  1. Jupiter Rowland @[email protected] ·
    @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 the title tag 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 the title tag 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
    #cwimagedescriptionmeta #imagedescriptionmeta #imagedescriptions #imagedescription #cwfediversemeta #fediversemeta
  2. Jupiter Rowland @[email protected] ·
    @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 the title tag 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 the title tag 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
    #cwimagedescriptionmeta #imagedescriptionmeta #imagedescriptions #imagedescription #cwfediversemeta #fediversemeta
  3. Jupiter Rowland @[email protected] ·
    @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 the title tag 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 the title tag 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
    #cwimagedescriptionmeta #imagedescriptionmeta #imagedescriptions #imagedescription #cwfediversemeta #fediversemeta
  4. Jupiter Rowland @[email protected] ·
    @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 the title tag 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 the title tag 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
    #i3 #a11y #i3wm #long #cwlong #alttext
  5. Jupiter Rowland @[email protected] ·
    @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 the title tag 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 the title tag 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
    #cwimagedescriptionmeta #imagedescriptionmeta #imagedescriptions #imagedescription #cwfediversemeta #fediversemeta
  6. vermaden @[email protected] ·

    I have seen Omarchy Linux ... but for some reason I missed Omfreebdy FreeBSD based alternative.

    I personally use X11 and prefer it over Wayland - but I now know that Omfreebdy comes with X11 version as well.

    Great to see such option available.

    omfreebdy.dba.wtf/

    #freebsd #x11 #i3 #omarchy #omfreebdy

    #freebsd #x11 #i3 #omarchy #omfreebdy
  7. vermaden @[email protected] ·

    I have seen Omarchy Linux ... but for some reason I missed Omfreebdy FreeBSD based alternative.

    I personally use X11 and prefer it over Wayland - but I now know that Omfreebdy comes with X11 version as well.

    Great to see such option available.

    omfreebdy.dba.wtf/

    #freebsd #x11 #i3 #omarchy #omfreebdy

    #freebsd #x11 #i3 #omarchy #omfreebdy
  8. vermaden @[email protected] ·

    I have seen Omarchy Linux ... but for some reason I missed Omfreebdy FreeBSD based alternative.

    I personally use X11 and prefer it over Wayland - but I now know that Omfreebdy comes with X11 version as well.

    Great to see such option available.

    omfreebdy.dba.wtf/

    #freebsd #x11 #i3 #omarchy #omfreebdy

    #freebsd #x11 #i3 #omarchy #omfreebdy
  9. vermaden @[email protected] ·

    I have seen Omarchy Linux ... but for some reason I missed Omfreebdy FreeBSD based alternative.

    I personally use X11 and prefer it over Wayland - but I now know that Omfreebdy comes with X11 version as well.

    Great to see such option available.

    omfreebdy.dba.wtf/

    #freebsd #x11 #i3 #omarchy #omfreebdy

    #omfreebdy #omarchy #i3 #x11 #freebsd
  10. vermaden @[email protected] ·

    I have seen Omarchy Linux ... but for some reason I missed Omfreebdy FreeBSD based alternative.

    I personally use X11 and prefer it over Wayland - but I now know that Omfreebdy comes with X11 version as well.

    Great to see such option available.

    omfreebdy.dba.wtf/

    #freebsd #x11 #i3 #omarchy #omfreebdy

    #freebsd #x11 #i3 #omarchy #omfreebdy
  11. randomized @[email protected] ·

    New blog post: tools i use - part 1 in x

    randomized.hadoly.fr/2026/05/2

    #sysadmin
    #linux
    #fedora
    #it
    #i3

    #sysadmin #linux #fedora #it #i3
  12. randomized @[email protected] ·

    New blog post: tools i use - part 1 in x

    randomized.hadoly.fr/2026/05/2

    #sysadmin
    #linux
    #fedora
    #it
    #i3

    #sysadmin #linux #fedora #it #i3
  13. randomized @[email protected] ·

    New blog post: tools i use - part 1 in x

    randomized.hadoly.fr/2026/05/2

    #sysadmin
    #linux
    #fedora
    #it
    #i3

    #sysadmin #linux #fedora #it #i3
  14. randomized @[email protected] ·

    New blog post: tools i use - part 1 in x

    randomized.hadoly.fr/2026/05/2

    #sysadmin
    #linux
    #fedora
    #it
    #i3

    #i3 #it #fedora #linux #sysadmin
  15. Germany @[email protected] ·

    The new BMW i3. Second model of the Neue Klasse.

    As the second model in the Neue Klasse, it represents a technological quantum leap into a new era.…
    #Germany #DE #Europe #EU #Europa #BMW #3Series #BMWi #i3 #Sedan
    europesays.com/germany/22326/

    #sedan #i3 #bmwi #3series #bmw #europa
  16. Hacker News @[email protected] ·

    My I3-Emacs Integration

    khz.ac/software/i3-integration

    #HackerNews #I3 #Emacs #Integration #EmacsConfig #Productivity #SoftwareDevelopment

    #hackernews #i3 #emacs #integration #emacsconfig #productivity
  17. Hacker News @[email protected] ·

    My I3-Emacs Integration

    khz.ac/software/i3-integration

    #HackerNews #I3 #Emacs #Integration #EmacsConfig #Productivity #SoftwareDevelopment

    #hackernews #i3 #emacs #integration #emacsconfig #productivity
  18. Hacker News @[email protected] ·

    My I3-Emacs Integration

    khz.ac/software/i3-integration

    #HackerNews #I3 #Emacs #Integration #EmacsConfig #Productivity #SoftwareDevelopment

    #hackernews #i3 #emacs #integration #emacsconfig #productivity
  19. Hacker News @[email protected] ·

    My I3-Emacs Integration

    khz.ac/software/i3-integration

    #HackerNews #I3 #Emacs #Integration #EmacsConfig #Productivity #SoftwareDevelopment

    #softwaredevelopment #productivity #emacsconfig #integration #emacs #i3
  20. Hacker News @[email protected] ·

    My I3-Emacs Integration

    khz.ac/software/i3-integration

    #HackerNews #I3 #Emacs #Integration #EmacsConfig #Productivity #SoftwareDevelopment

    #hackernews #i3 #emacs #integration #emacsconfig #productivity
  21. Lett Osprey :v_pan: :v_enby: 🍉 :therian: @[email protected] ·

    After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.

    I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.

    The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.

    I had to force myself to use i3 for several days to get used to the difference, but that paid off.

    Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.

    #kde #cosmic #gnome #sway #i3
  22. Lett Osprey :v_pan: :v_enby: 🍉 :therian: @[email protected] ·

    After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.

    I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.

    The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.

    I had to force myself to use i3 for several days to get used to the difference, but that paid off.

    Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.

    #gnome #sway #i3 #kde #cosmic
  23. Lett Osprey :v_pan: :v_enby: 🍉 :therian: @[email protected] ·

    After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.

    I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.

    The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.

    I had to force myself to use i3 for several days to get used to the difference, but that paid off.

    Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.

    #kde #cosmic #gnome #sway #i3
  24. Lett Osprey :v_pan: :v_enby: 🍉 :therian: @[email protected] ·

    After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.

    I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.

    The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.

    I had to force myself to use i3 for several days to get used to the difference, but that paid off.

    Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.

    #cosmic #kde #i3 #sway #gnome
  25. Lett Osprey :v_pan: :v_enby: 🍉 :therian: @[email protected] ·

    After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.

    I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.

    The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.

    I had to force myself to use i3 for several days to get used to the difference, but that paid off.

    Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.

    #gnome #sway #i3 #kde #cosmic
  26. Emy 🍉 🌱 :artix: @[email protected] ·

    Jajajaja recuerdo mi pánico la primera vez que me pasó esto :blobcatpats:
    #i3 #i3wm

    #i3 #i3wm
  27. Emy 🍉 🌱 :artix: @[email protected] ·

    Jajajaja recuerdo mi pánico la primera vez que me pasó esto :blobcatpats:
    #i3 #i3wm

    #i3 #i3wm
  28. MaddieM4 @[email protected] ·

    Finally fixed #dmenu to launch scripts from my `~/bin` correctly.

    The issue is that my home directory is an import from my previous Pop!OS install, but currently running on CachyOS, and there's some differences of implicit assumptions between the two. The short version is that I was missing a `~/.xsession` file containing:

    ```
    #!/bin/sh
    . ~/.profile
    ```

    I already had a `~/.profile` that worked correctly, but it wasn't being executed during X11 login, so I had the system default `$PATH` but nothing user-specific. I also needed to delete my `~/.cache/dmenu_run` so it would recompute my path-available executables. Now I can properly launch Zen browser, and a wrapped version of Signal that actually uses the correct credential wallet, when using #i3.

    I'll probably have to figure out similar fuckery again if I ever get #sway to work on my graphics card.

    #dmenu #i3 #sway
  29. MaddieM4 @[email protected] ·

    Finally fixed #dmenu to launch scripts from my `~/bin` correctly.

    The issue is that my home directory is an import from my previous Pop!OS install, but currently running on CachyOS, and there's some differences of implicit assumptions between the two. The short version is that I was missing a `~/.xsession` file containing:

    ```
    #!/bin/sh
    . ~/.profile
    ```

    I already had a `~/.profile` that worked correctly, but it wasn't being executed during X11 login, so I had the system default `$PATH` but nothing user-specific. I also needed to delete my `~/.cache/dmenu_run` so it would recompute my path-available executables. Now I can properly launch Zen browser, and a wrapped version of Signal that actually uses the correct credential wallet, when using #i3.

    I'll probably have to figure out similar fuckery again if I ever get #sway to work on my graphics card.

    #dmenu #i3 #sway
  30. MaddieM4 @[email protected] ·

    Finally fixed #dmenu to launch scripts from my `~/bin` correctly.

    The issue is that my home directory is an import from my previous Pop!OS install, but currently running on CachyOS, and there's some differences of implicit assumptions between the two. The short version is that I was missing a `~/.xsession` file containing:

    ```
    #!/bin/sh
    . ~/.profile
    ```

    I already had a `~/.profile` that worked correctly, but it wasn't being executed during X11 login, so I had the system default `$PATH` but nothing user-specific. I also needed to delete my `~/.cache/dmenu_run` so it would recompute my path-available executables. Now I can properly launch Zen browser, and a wrapped version of Signal that actually uses the correct credential wallet, when using #i3.

    I'll probably have to figure out similar fuckery again if I ever get #sway to work on my graphics card.

    #dmenu #i3 #sway
  31. MaddieM4 @[email protected] ·

    Finally fixed #dmenu to launch scripts from my `~/bin` correctly.

    The issue is that my home directory is an import from my previous Pop!OS install, but currently running on CachyOS, and there's some differences of implicit assumptions between the two. The short version is that I was missing a `~/.xsession` file containing:

    ```
    #!/bin/sh
    . ~/.profile
    ```

    I already had a `~/.profile` that worked correctly, but it wasn't being executed during X11 login, so I had the system default `$PATH` but nothing user-specific. I also needed to delete my `~/.cache/dmenu_run` so it would recompute my path-available executables. Now I can properly launch Zen browser, and a wrapped version of Signal that actually uses the correct credential wallet, when using #i3.

    I'll probably have to figure out similar fuckery again if I ever get #sway to work on my graphics card.

    #sway #i3 #dmenu
  32. CDE Universitat de València @[email protected] ·

    Instrumento de Inversiones en Innovación Interregional (#I3). Subvenciones a proyectos. Línea 2a de Inversiones en Innovación Interregional. Convocatoria de propuestas I3-2026-INV2a. Fecha límite: 12 de septiembre de 2026 | W3 Oportunidades de financiación y convocatorias de propuestas 13 de mayo de 2026 #AyudasUE links.uv.es/xYhueY7

    #i3 #ayudasue
  33. CDE Universitat de València @[email protected] ·

    Instrumento de Inversiones en Innovación Interregional (#I3). Subvenciones a proyectos. Línea 2a de Inversiones en Innovación Interregional. Convocatoria de propuestas I3-2026-INV2a. Fecha límite: 12 de septiembre de 2026 | W3 Oportunidades de financiación y convocatorias de propuestas 13 de mayo de 2026 #AyudasUE links.uv.es/xYhueY7

    #i3 #ayudasue
  34. CDE Universitat de València @[email protected] ·

    Instrumento de Inversiones en Innovación Interregional (#I3). Subvenciones a proyectos. Línea 1 de Inversiones en Innovación Interregional. Convocatoria de propuestas I3-2026-INV1. Fecha límite: 12 de septiembre de 2026 | W3 Oportunidades de financiación y convocatorias de propuestas 13 de mayo de 2026 #AyudasUE links.uv.es/ii70Hhm

    #i3 #ayudasue
  35. CDE Universitat de València @[email protected] ·

    Instrumento de Inversiones en Innovación Interregional (#I3). Subvenciones a proyectos. Línea 1 de Inversiones en Innovación Interregional. Convocatoria de propuestas I3-2026-INV1. Fecha límite: 12 de septiembre de 2026 | W3 Oportunidades de financiación y convocatorias de propuestas 13 de mayo de 2026 #AyudasUE links.uv.es/ii70Hhm

    #i3 #ayudasue
  36. Dekks Herton @[email protected] ·

    @lispi314

    T1200 ~ 4/5 years old

    But the big thing is i'll be back on #i3

    #i3
  37. Dekks Herton @[email protected] ·

    @lispi314

    T1200 ~ 4/5 years old

    But the big thing is i'll be back on #i3

    #i3
  38. Dekks Herton @[email protected] ·

    @lispi314

    T1200 ~ 4/5 years old

    But the big thing is i'll be back on #i3

    #i3
  39. Dekks Herton @[email protected] ·

    @lispi314

    T1200 ~ 4/5 years old

    But the big thing is i'll be back on #i3

    #i3
  40. Dekks Herton @[email protected] ·

    @lispi314

    T1200 ~ 4/5 years old

    But the big thing is i'll be back on #i3

    #i3
  41. Milka64 @[email protected] ·

    Dites-moi les @ergonautes, depuis que je suis passé full ergol, je ne me sens plus trop à l'aise avec mes raccourci pour I3wm. Des conseils à me donner ? Des exemples peut être ?
    #ergol #i3 #ergonautes

    #ergol #i3 #ergonautes
  42. Milka64 @[email protected] ·

    Dites-moi les @ergonautes, depuis que je suis passé full ergol, je ne me sens plus trop à l'aise avec mes raccourci pour I3wm. Des conseils à me donner ? Des exemples peut être ?
    #ergol #i3 #ergonautes

    #ergol #i3 #ergonautes
  43. Milka64 @[email protected] ·

    Dites-moi les @ergonautes, depuis que je suis passé full ergol, je ne me sens plus trop à l'aise avec mes raccourci pour I3wm. Des conseils à me donner ? Des exemples peut être ?
    #ergol #i3 #ergonautes

    #ergol #i3 #ergonautes
  44. Suomi @[email protected] ·

    europesays.com/fi/241285/ Jopa 900 km toimintamatka – BMW i3 vie sähköisen 3-sarjan uudelle tasolle #BMWI3 #Business #Economy #FI #Finland #Finnish #i3 #NeueKlasse #Suomi #Talous

    #talous #suomi #neueklasse #i3 #finnish #finland
  45. Magyarország @[email protected] ·

    europesays.com/hu/90650/ Elkészült a kétmilliomodik elektromos BMW #BMW #eladás #ElektromosAutó #HU #Hungarian #Hungary #i3 #ix3 #Magyar #Magyarország #mérföldkő #Science #Science&Technology #Technológia #Technology #Tudomány #TudományésTechnológia #villanyautó

    #villanyauto #tudomanyestechnologia #tudomany #technology #technologia #science
  46. wpltyps219129 @[email protected] ·

    Japan diary, day151

    I restore my old old laptop, Lenovo S21e, NetBSD + i3 + drawterm.
    I couldn't install 9front to emmc of this.
    There might be better ways to do this, but for now, I can use an old machine like a 9front terminal (^_^).

    #netbsd
    #i3
    #drawterm
    #9front

    #netbsd #i3 #drawterm #9front
  47. wpltyps219129 @[email protected] ·

    Japan diary, day151

    I restore my old old laptop, Lenovo S21e, NetBSD + i3 + drawterm.
    I couldn't install 9front to emmc of this.
    There might be better ways to do this, but for now, I can use an old machine like a 9front terminal (^_^).

    #netbsd
    #i3
    #drawterm
    #9front

    #netbsd #i3 #drawterm #9front
  48. Sebastian :coffefied: @[email protected] ·

    In the spirit of #SmartHome tinkering and looming amount of video recorded, I’ve been thinking about building a home NAS.

    The hardware costs an arm and a leg these days, but I still have an old #MSI mainboard with some shitty #Intel #i3 CPU AND there’s 2 sticks of 4G and 2G DDR3 RAM.

    I’m still missing everything else - a case (preferably 1U and appropriate CPU cooler), power supply, decent low profile GPU and the glorious nail to this shitty coffin - hard drives…😂

    And there’s energy bill…🤡

    #smarthome #msi #intel #i3
  49. Sebastian :coffefied: @ssamulczyk ·

    In the spirit of tinkering and looming amount of video recorded, I’ve been thinking about building a home NAS.

    The hardware costs an arm and a leg these days, but I still have an old mainboard with some shitty CPU AND there’s 2 sticks of 4G and 2G DDR3 RAM.

    I’m still missing everything else - a case (preferably 1U and appropriate CPU cooler), power supply, decent low profile GPU and the glorious nail to this shitty coffin - hard drives…😂

    And there’s energy bill…🤡

    #smarthome #msi #intel #i3
  50. Sebastian :coffefied: @[email protected] ·

    In the spirit of #SmartHome tinkering and looming amount of video recorded, I’ve been thinking about building a home NAS.

    The hardware costs an arm and a leg these days, but I still have an old #MSI mainboard with some shitty #Intel #i3 CPU AND there’s 2 sticks of 4G and 2G DDR3 RAM.

    I’m still missing everything else - a case (preferably 1U and appropriate CPU cooler), power supply, decent low profile GPU and the glorious nail to this shitty coffin - hard drives…😂

    And there’s energy bill…🤡

    #smarthome #msi #intel #i3