I don’t know if Firefox is at fault. It could be Firedragon (the fork I’m using), it could be any of the desktop portals messing things up (looking at you, xdg-desktop-portal-gtk), it could be Arch Linux due to how packagers package each portal, it could be that I stepped on a landmine by switching from Sway to Hyprland - this is when the problem first occurred.
Firedragon’s (and the Firefox flatpak’s) output doesn’t say anything, nothing stands out in their logs, same goes for both Sway and Hyprland - for all I know XDG portals don’t even have standalone logs, they just dump error messages to stdout in my experience (which, again, have not been dumped).
I could send bug reports to everyone, and get told “this isn’t our problem, write a bug report to ${OTHER_SOFTWARE}”. But then, which logs do I provide? All of them? Sure, I can gather up logs and non-existent messages from several pieces of software, one of them being a glorified API.
It would have taken me a good hour to find the relevant data, find the correct places to write reports to, word things in a quasi-professional manner, all for a small chance for any of the developers of something to answer something that is not a variation of “can’t help you bro, your logs are anorexic”.
So, after reminiscing the days of writing Windows registry keys and seeing no results (by writing XDP hints all over the system AND rebooting), I took 10 minutes to vent and make a meme - NoScript was intefering with imgflip, otherwise I would have needed 3.
I could not, in fact, definitely have raised a bug report in the time it took me to make this.
jdk-openjdk vs jre-openjdk? archlinux.org mentions it, although the workaround it provides is fake news and also results in pacman complaining about conflicts.
I just removed stuff, abused pacman --nodeps and prayed that my backups would be sufficient to restore my inevitable fuckup (no fuckup happened, somehow). Try that at your own risk though…
(As it turns out, the cause was a previous attempt to get xdg-desktop-portal-termfilechooser to work - I’m just going to sneak this edit in here and go die in a corner or something)
If you had read carefully the beehaw.org TOS, you’d know there’s a fine-print clause that nominates you, personally, as the ambassador of all of its communities; everyone else is contractually obligated to upvote comments on your posts where you make fun of… uh, people who have had sex education or poor English speechcraft idk.
Blocking a community for a protest is irresponsible and undemocratic.
NSFWification
Using a feature that is explicitly baked into the platform is irresponsible and will harm people who chose to click/tap on NSFW content clearly marked as such, and probably voted for to appear in the subreddit children.