home.social

#xdg — Public Fediverse posts

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

  1. If anyone needs a #CommodoreAmiga IFF ILBM image viewer for their #Wayland desktop (I use #Hyprland), I put one together as a nice self-contained #C application. It also has #nautilus and #XDG integration.

    github.com/tschak909/ilbmview

  2. If anyone needs a #CommodoreAmiga IFF ILBM image viewer for their #Wayland desktop (I use #Hyprland), I put one together as a nice self-contained #C application. It also has #nautilus and #XDG integration.

    github.com/tschak909/ilbmview

  3. If anyone needs a #CommodoreAmiga IFF ILBM image viewer for their #Wayland desktop (I use #Hyprland), I put one together as a nice self-contained #C application. It also has #nautilus and #XDG integration.

    github.com/tschak909/ilbmview

  4. If anyone needs a #CommodoreAmiga IFF ILBM image viewer for their #Wayland desktop (I use #Hyprland), I put one together as a nice self-contained #C application. It also has #nautilus and #XDG integration.

    github.com/tschak909/ilbmview

  5. If anyone needs a #CommodoreAmiga IFF ILBM image viewer for their #Wayland desktop (I use #Hyprland), I put one together as a nice self-contained #C application. It also has #nautilus and #XDG integration.

    github.com/tschak909/ilbmview

  6. It'll probably take another 20 years for to actually properly implement spec where cache, state, data and config are split in accordance with the spec.

  7. It'll probably take another 20 years for #firefox to actually properly implement #XDG spec where cache, state, data and config are split in accordance with the spec.

  8. It'll probably take another 20 years for #firefox to actually properly implement #XDG spec where cache, state, data and config are split in accordance with the spec.

  9. 🦅💩 Thunderbird: now with cutting-edge directory disorder! Who knew rediscovering an old #email client could lead to a groundbreaking new way to clutter your home? 📂✨ Apparently, the #XDG #changes are creating directories faster than you can say 'bug fix'. 🙄🚀
    thefoggiest.dev/2026/06/04/thu #Thunderbird #DirectoryClutter #TechInnovation #EmailClient #HackerNews #ngated

  10. 🦅💩 Thunderbird: now with cutting-edge directory disorder! Who knew rediscovering an old #email client could lead to a groundbreaking new way to clutter your home? 📂✨ Apparently, the #XDG #changes are creating directories faster than you can say 'bug fix'. 🙄🚀
    thefoggiest.dev/2026/06/04/thu #Thunderbird #DirectoryClutter #TechInnovation #EmailClient #HackerNews #ngated

  11. 🦅💩 Thunderbird: now with cutting-edge directory disorder! Who knew rediscovering an old #email client could lead to a groundbreaking new way to clutter your home? 📂✨ Apparently, the #XDG #changes are creating directories faster than you can say 'bug fix'. 🙄🚀
    thefoggiest.dev/2026/06/04/thu #Thunderbird #DirectoryClutter #TechInnovation #EmailClient #HackerNews #ngated

  12. 🦅💩 Thunderbird: now with cutting-edge directory disorder! Who knew rediscovering an old #email client could lead to a groundbreaking new way to clutter your home? 📂✨ Apparently, the #XDG #changes are creating directories faster than you can say 'bug fix'. 🙄🚀
    thefoggiest.dev/2026/06/04/thu #Thunderbird #DirectoryClutter #TechInnovation #EmailClient #HackerNews #ngated

  13. 🦅💩 Thunderbird: now with cutting-edge directory disorder! Who knew rediscovering an old #email client could lead to a groundbreaking new way to clutter your home? 📂✨ Apparently, the #XDG #changes are creating directories faster than you can say 'bug fix'. 🙄🚀
    thefoggiest.dev/2026/06/04/thu #Thunderbird #DirectoryClutter #TechInnovation #EmailClient #HackerNews #ngated

  14. For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: openwall.com/lists/oss-securit

    You might also want to read this article from last year: linuxjournal.com/content/when-

    cc @Seg

    #sandboxing #dbus #xdg #freedesktop #wine

  15. For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: openwall.com/lists/oss-securit

    You might also want to read this article from last year: linuxjournal.com/content/when-

    cc @Seg

    #sandboxing #dbus #xdg #freedesktop #wine

  16. For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: openwall.com/lists/oss-securit

    You might also want to read this article from last year: linuxjournal.com/content/when-

    cc @Seg

    #sandboxing #dbus #xdg #freedesktop #wine

  17. For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: openwall.com/lists/oss-securit

    You might also want to read this article from last year: linuxjournal.com/content/when-

    cc @Seg

    #sandboxing #dbus #xdg #freedesktop #wine

  18. For anyone interested in #Linux security, a good explanation of a way to escape from the #Flatpak sandbox has been posted to the oss-security mailing list today: openwall.com/lists/oss-securit

    You might also want to read this article from last year: linuxjournal.com/content/when-

    cc @Seg

    #sandboxing #dbus #xdg #freedesktop #wine

  19. new xdg-user-dir who dis :ablobcateyesflip:​

    completely upending my entire Home folder to accommodate it since it's so much better than having random crap strewn across a bunch of places

    #Linux #FOSS #xdg

  20. new xdg-user-dir who dis :ablobcateyesflip:​

    completely upending my entire Home folder to accommodate it since it's so much better than having random crap strewn across a bunch of places

    #Linux #FOSS #xdg

  21. new xdg-user-dir who dis :ablobcateyesflip:​

    completely upending my entire Home folder to accommodate it since it's so much better than having random crap strewn across a bunch of places

    #Linux #FOSS #xdg

  22. new xdg-user-dir who dis :ablobcateyesflip:​

    completely upending my entire Home folder to accommodate it since it's so much better than having random crap strewn across a bunch of places

    #Linux #FOSS #xdg

  23. new xdg-user-dir who dis :ablobcateyesflip:​

    completely upending my entire Home folder to accommodate it since it's so much better than having random crap strewn across a bunch of places

    #Linux #FOSS #xdg

  24. Me vuela la cabeza que todavía no tengamos más apoyo en nuestras herramientas para XDG base directories.

    Para los que no sepan que es esto, es un spec que define donde archivos deben de “vivir”. Se utiliza mucho para archivos de configuración en ambientes de *nix.

    Si están construyendo algo o mantienen un CLI, denle un vistazo. Consideren apoyar este spec.

    specifications.freedesktop.org

    #XDG #BaseDirSpec #FOSS

  25. Me vuela la cabeza que todavía no tengamos más apoyo en nuestras herramientas para XDG base directories.

    Para los que no sepan que es esto, es un spec que define donde archivos deben de “vivir”. Se utiliza mucho para archivos de configuración en ambientes de *nix.

    Si están construyendo algo o mantienen un CLI, denle un vistazo. Consideren apoyar este spec.

    specifications.freedesktop.org

    #XDG #BaseDirSpec #FOSS

  26. Me vuela la cabeza que todavía no tengamos más apoyo en nuestras herramientas para XDG base directories.

    Para los que no sepan que es esto, es un spec que define donde archivos deben de “vivir”. Se utiliza mucho para archivos de configuración en ambientes de *nix.

    Si están construyendo algo o mantienen un CLI, denle un vistazo. Consideren apoyar este spec.

    specifications.freedesktop.org

    #XDG #BaseDirSpec #FOSS

  27. Me vuela la cabeza que todavía no tengamos más apoyo en nuestras herramientas para XDG base directories.

    Para los que no sepan que es esto, es un spec que define donde archivos deben de “vivir”. Se utiliza mucho para archivos de configuración en ambientes de *nix.

    Si están construyendo algo o mantienen un CLI, denle un vistazo. Consideren apoyar este spec.

    specifications.freedesktop.org

    #XDG #BaseDirSpec #FOSS

  28. Me vuela la cabeza que todavía no tengamos más apoyo en nuestras herramientas para XDG base directories.

    Para los que no sepan que es esto, es un spec que define donde archivos deben de “vivir”. Se utiliza mucho para archivos de configuración en ambientes de *nix.

    Si están construyendo algo o mantienen un CLI, denle un vistazo. Consideren apoyar este spec.

    specifications.freedesktop.org

    #XDG #BaseDirSpec #FOSS

  29. CW: Fighting ID early verification

    This morning, I received a response to a post I made about Discord’s ID verification process. The post blamed governments for Discord’s actions. This is a pattern I see often. I replied to the reply. With #Flatpak and #XDG ‘s recent actions, I feel it’s worthwhile to post this separately and modified slightly.

    I advocate fighting our governments but that’s not what’s happening here. So far, there is no national law with a requirement that this type of invasive user IDing be done. Even if there were, Discord could sue the government. That’s one of the main ways these things get overturned since the very legislatures that implement these laws are unlikely to overturn them in a timely fashion without mass, nation disrupting action.

    So far, these actions have happened at the state level. Bluesky’s reaction to Mississippi’s law was to block visitors from the state of Mississippi. That was the right call. Discord should have done the same and sued the states implementing these laws.

    The fact that Discord chose to go out of their way to do something so bespoke, custom, and egregious hints that they were already working on it for other reasons entirely. Their whole modus operandi seems to be to gather as much user data as possible including for the purposes of develop AI models. I think it’s likely they built the systems they have specifically so they can market their solutions for identifying “underage” users. They want to be the ones selling this invasive tech to other companies. That’s way worse than merely proactively complying when they had so many other options to fight.

    We have to stop making excuses for the companies that are not merely complying in advance but positioning themselves to profit from future tyranny.

    In the case of Flatpak and XDG, they may not be preparing to profit from these laws but they certainly have more options than compliance with them.

    #Discord #IDVerification

  30. CW: Fighting ID early verification

    This morning, I received a response to a post I made about Discord’s ID verification process. The post blamed governments for Discord’s actions. This is a pattern I see often. I replied to the reply. With #Flatpak and #XDG ‘s recent actions, I feel it’s worthwhile to post this separately and modified slightly.

    I advocate fighting our governments but that’s not what’s happening here. So far, there is no national law with a requirement that this type of invasive user IDing be done. Even if there were, Discord could sue the government. That’s one of the main ways these things get overturned since the very legislatures that implement these laws are unlikely to overturn them in a timely fashion without mass, nation disrupting action.

    So far, these actions have happened at the state level. Bluesky’s reaction to Mississippi’s law was to block visitors from the state of Mississippi. That was the right call. Discord should have done the same and sued the states implementing these laws.

    The fact that Discord chose to go out of their way to do something so bespoke, custom, and egregious hints that they were already working on it for other reasons entirely. Their whole modus operandi seems to be to gather as much user data as possible including for the purposes of develop AI models. I think it’s likely they built the systems they have specifically so they can market their solutions for identifying “underage” users. They want to be the ones selling this invasive tech to other companies. That’s way worse than merely proactively complying when they had so many other options to fight.

    We have to stop making excuses for the companies that are not merely complying in advance but positioning themselves to profit from future tyranny.

    In the case of Flatpak and XDG, they may not be preparing to profit from these laws but they certainly have more options than compliance with them.

    #Discord #IDVerification

  31. CW: Fighting ID early verification

    This morning, I received a response to a post I made about Discord’s ID verification process. The post blamed governments for Discord’s actions. This is a pattern I see often. I replied to the reply. With #Flatpak and #XDG ‘s recent actions, I feel it’s worthwhile to post this separately and modified slightly.

    I advocate fighting our governments but that’s not what’s happening here. So far, there is no national law with a requirement that this type of invasive user IDing be done. Even if there were, Discord could sue the government. That’s one of the main ways these things get overturned since the very legislatures that implement these laws are unlikely to overturn them in a timely fashion without mass, nation disrupting action.

    So far, these actions have happened at the state level. Bluesky’s reaction to Mississippi’s law was to block visitors from the state of Mississippi. That was the right call. Discord should have done the same and sued the states implementing these laws.

    The fact that Discord chose to go out of their way to do something so bespoke, custom, and egregious hints that they were already working on it for other reasons entirely. Their whole modus operandi seems to be to gather as much user data as possible including for the purposes of develop AI models. I think it’s likely they built the systems they have specifically so they can market their solutions for identifying “underage” users. They want to be the ones selling this invasive tech to other companies. That’s way worse than merely proactively complying when they had so many other options to fight.

    We have to stop making excuses for the companies that are not merely complying in advance but positioning themselves to profit from future tyranny.

    In the case of Flatpak and XDG, they may not be preparing to profit from these laws but they certainly have more options than compliance with them.

    #Discord #IDVerification

  32. CW: Fighting ID early verification

    This morning, I received a response to a post I made about Discord’s ID verification process. The post blamed governments for Discord’s actions. This is a pattern I see often. I replied to the reply. With #Flatpak and #XDG ‘s recent actions, I feel it’s worthwhile to post this separately and modified slightly.

    I advocate fighting our governments but that’s not what’s happening here. So far, there is no national law with a requirement that this type of invasive user IDing be done. Even if there were, Discord could sue the government. That’s one of the main ways these things get overturned since the very legislatures that implement these laws are unlikely to overturn them in a timely fashion without mass, nation disrupting action.

    So far, these actions have happened at the state level. Bluesky’s reaction to Mississippi’s law was to block visitors from the state of Mississippi. That was the right call. Discord should have done the same and sued the states implementing these laws.

    The fact that Discord chose to go out of their way to do something so bespoke, custom, and egregious hints that they were already working on it for other reasons entirely. Their whole modus operandi seems to be to gather as much user data as possible including for the purposes of develop AI models. I think it’s likely they built the systems they have specifically so they can market their solutions for identifying “underage” users. They want to be the ones selling this invasive tech to other companies. That’s way worse than merely proactively complying when they had so many other options to fight.

    We have to stop making excuses for the companies that are not merely complying in advance but positioning themselves to profit from future tyranny.

    In the case of Flatpak and XDG, they may not be preparing to profit from these laws but they certainly have more options than compliance with them.

    #Discord #IDVerification

  33. CW: Fighting ID early verification

    This morning, I received a response to a post I made about Discord’s ID verification process. The post blamed governments for Discord’s actions. This is a pattern I see often. I replied to the reply. With #Flatpak and #XDG ‘s recent actions, I feel it’s worthwhile to post this separately and modified slightly.

    I advocate fighting our governments but that’s not what’s happening here. So far, there is no national law with a requirement that this type of invasive user IDing be done. Even if there were, Discord could sue the government. That’s one of the main ways these things get overturned since the very legislatures that implement these laws are unlikely to overturn them in a timely fashion without mass, nation disrupting action.

    So far, these actions have happened at the state level. Bluesky’s reaction to Mississippi’s law was to block visitors from the state of Mississippi. That was the right call. Discord should have done the same and sued the states implementing these laws.

    The fact that Discord chose to go out of their way to do something so bespoke, custom, and egregious hints that they were already working on it for other reasons entirely. Their whole modus operandi seems to be to gather as much user data as possible including for the purposes of develop AI models. I think it’s likely they built the systems they have specifically so they can market their solutions for identifying “underage” users. They want to be the ones selling this invasive tech to other companies. That’s way worse than merely proactively complying when they had so many other options to fight.

    We have to stop making excuses for the companies that are not merely complying in advance but positioning themselves to profit from future tyranny.

    In the case of Flatpak and XDG, they may not be preparing to profit from these laws but they certainly have more options than compliance with them.

    #Discord #IDVerification

  34. Hey @pid_eins was going to post to the XDG list but it seems dead over there. The link[1] to the Sound theme spec is dead and seems to have fallen to the wayside. As well as the default sound theme being a bit long in tooth. Is there planned work here or an updated specification somewhere. If not, i'd like to go ahead and clean this up while i'm trying to figure out wtf everything Gnome is doing with the sound spec right now. It could definitely use some love, thanks!

    [1]: 0pointer.de/public/sound-theme

    #gnome #freedesktop #xdg #soundspec

  35. Hey @pid_eins was going to post to the XDG list but it seems dead over there. The link[1] to the Sound theme spec is dead and seems to have fallen to the wayside. As well as the default sound theme being a bit long in tooth. Is there planned work here or an updated specification somewhere. If not, i'd like to go ahead and clean this up while i'm trying to figure out wtf everything Gnome is doing with the sound spec right now. It could definitely use some love, thanks!

    [1]: 0pointer.de/public/sound-theme

    #gnome #freedesktop #xdg #soundspec

  36. Hey @pid_eins was going to post to the XDG list but it seems dead over there. The link[1] to the Sound theme spec is dead and seems to have fallen to the wayside. As well as the default sound theme being a bit long in tooth. Is there planned work here or an updated specification somewhere. If not, i'd like to go ahead and clean this up while i'm trying to figure out wtf everything Gnome is doing with the sound spec right now. It could definitely use some love, thanks!

    [1]: 0pointer.de/public/sound-theme

    #gnome #freedesktop #xdg #soundspec

  37. Is there a CLI tool out there that'll show me the bytes in common across lots of files, and their offsets? I'm doing a bit of binary file format analysis, hoping to contribute some types into shared-mime-info for ZX Spectrum and Commodore emulation disk+tape+cartridge files. Trying to fix up some ".tap" and ".d80" name clashes with More Magic :blobcatspace: 🔄

    #ZXSpectrum #Didaktik #Commodore #Sinclair #Emulation #AskFedi #LazyWeb #RetroGamimg #RetroComputing #FuseEmulator #ViceEmulator #XDG

  38. Is there a CLI tool out there that'll show me the bytes in common across lots of files, and their offsets? I'm doing a bit of binary file format analysis, hoping to contribute some types into shared-mime-info for ZX Spectrum and Commodore emulation disk+tape+cartridge files. Trying to fix up some ".tap" and ".d80" name clashes with More Magic :blobcatspace: 🔄

    #ZXSpectrum #Didaktik #Commodore #Sinclair #Emulation #AskFedi #LazyWeb #RetroGamimg #RetroComputing #FuseEmulator #ViceEmulator #XDG

  39. Is there a CLI tool out there that'll show me the bytes in common across lots of files, and their offsets? I'm doing a bit of binary file format analysis, hoping to contribute some types into shared-mime-info for ZX Spectrum and Commodore emulation disk+tape+cartridge files. Trying to fix up some ".tap" and ".d80" name clashes with More Magic :blobcatspace: 🔄

    #ZXSpectrum #Didaktik #Commodore #Sinclair #Emulation #AskFedi #LazyWeb #RetroGamimg #RetroComputing #FuseEmulator #ViceEmulator #XDG