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

#Vim 9.2 : l'éditeur de texte légendaire s'offre #Wayland et le standard #XDG. 34 ans après sa première version, Vim prouve qu’il reste un pilier incontournable de l’écosystème #opensource.
https://goodtech.info/vim-9-2-release-support-wayland-standard-xdg/
Vim 9.2 est là : plus moderne et plus propre ⌨️

Wayland, XDG et complétion floue : la nouvelle version de Vim apporte des fonctionnalités attendues depuis des années. Votre terminal va vous remercier.

Goodtech
nice! For nvi users, no patch needed just add to your shell profile:

export EXINIT='source ~/.config/nvi/nexrc'

EXINIT is the standard ex/vi init variable, works across nvi and traditional vi implementations.

Just make sure ~/.nexrc and ~/.exrc don't exist, otherwise nvi reads those first and ignores EXINIT. #Vim #nvi #XDG

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]: http://0pointer.de/public/sound-theme-spec.html

#gnome #freedesktop #xdg #soundspec

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  🔄

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

Firefox 147 Will Support The XDG Base Directory Specification

A 21 year old bug report requesting support of the XDG Base Directory specification is finally being addressed by Firefox

#Firefox 147 Will Support The #XDG Base Directory Specification

A 21 year old #bug report requesting support of the XDG Base Directory specification is finally being addressed by Firefox. The Firefox 147 release should respect this XDG specification around where files should be positioned within #Linux users' home directory.
https://www.phoronix.com/news/Firefox-147-XDG-Base-Directory

Firefox 147 Will Support The XDG Base Directory Specification

A 21 year old bug report requesting support of the XDG Base Directory specification is finally being addressed by Firefox

i was about to quickly implement a system tray icon for one of my projects. thought it would be a swift task. turned out things are pretty grim on this one. #gtk dropped the support for system trays in v4, and all other libraries are either outdated or broken (haven't tried qt, but it is too heavy for this small task). ended up writing my own solution.

so, this baby talks with dbus directly, no other dependencies, single-file clib, zig wrapper, mit, works in every environment that supports the freedesktop standard!

https://github.com/charlesrocket/libstray

#dbus #c #zig #xdg

GitHub - charlesrocket/libstray: System tray icons via D-Bus

System tray icons via D-Bus. Contribute to charlesrocket/libstray development by creating an account on GitHub.

GitHub

AFAIK the work on native messaging for flatpaks (and snaps) is done so that KeePassXC and KeePassXC Browser could finally talk to each other again. But I could not find out what's still missing. Does my OS need an update of the xdg portals? Do the browser vendors need to support the portal? Currently, it's Zen and Vivaldi which are sandboxed. Or is it the browser extension or KeePassXC itself?

#keepassxc #flatpak #gnome #xdg