export MANGOHUD=1;export VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json; qdbus org.kde.KWin /Compositor suspend;mangohud %command%;qdbus org.kde.KWin /Compositor resume

This turns on my install of MangoHud for performance tracking, specifies my nVidia card as the primary/only Vulkan driver to load (otherwise my Intel iGPU takes first priority and it fails), and temporarily disables KDE Plasma's compositor while the game is running to avoid an issue with VSYNC and really really delayed inputs.

The 'export MANGOHUD=1' covers Vulkan while 'mangohud %command%' covers OpenGL, as I understand it - you can actually still use these options in the default OpenGL renderer without issue.

I've used GOverlay to force Adaptive VSYNC for both OpenGL and Vulkan modes, and left VSYNC on in-game. With KDE Plasma's compositor running, it seems to do the whole 30 <-> 60 fps jump with changes in effort, while with it temporarily disabled, it can run at other framerates in between without noticeable tearing.

The vast majority of Fediverse (aka Mastodon, Pleroma, and other compatible software) instances, including the Mastodon flagship mastodon.social, have what I'd consider fairly reasonable rules + codes of conduct. Of course, open source tools are open, so anyone with the skills to put them together can do so, and it wasn't long before instances started sprouting up for 'free speech fans' at best, and wholly blatant Neo-Nazi & 'Alt-Right' at worst. These instances would sprout up, and deliberately target other instances with users who are LGBTQ2+ or racialised, and harass them with barrages of threatening messages, so instance administrators had to get into a game of whack-a-mole, suspending federation with a handful of these new instances a week to help protect their users from that kind of abuse.

One of the more 'interesting' things that happened was an alt-right social network called Gab forked a copy of the Mastodon (and Tusky - a popular Android client) codebase, and migrated to it, with the same kind of results.

By this point, instance admins were starting to get very suspicious of new systems connecting + trying to federate with them, checking the self-proclaimed rules + code of conduct pages, and in many cases making the move to suspend federation before the first interactions even happen. In some cases, there's nothing posted there at all, so you either dig deeper or give them the benefit of the doubt and let it slide, waiting for the potential first reports of abuse.

Here's where Purism gets involved: they, too, fork the Mastodon and Tusky codebases, to... put it behind a paywall as part of their paid service offering, Librem One. To a network of instances where people put in communal effort and run off of donations, that read a little weird, but hey, that's their call. Canonical, Red Hat, SuSE, etc. all charge for some of their offerings despite being open source, right?

Users start signing up for Librem One, getting their new account on the Fediverse, and... some of them start sending the same, targeted, hateful and abusive messages to other instances. Now, when this happens from an instance that you otherwise normally trust or at least want to give the benefit of the doubt to, you can use the built-in reporting feature to report a user's harassment to the instance admins - of both the sender and receiver - who can each opt to act; the receiving instance can suspend receiving messages just from the one offending account, for example, but when it becomes a pattern, the onus is on the sending instance - i.e., where the abusers have their accounts - to act. Basically, to moderate their own platform.

As more and more abusers realised they could spend a couple bucks on a Librem One account and gain access to their targets, more instances on the receiving end started reaching out to the admins on the Purism side to report them. When no answer was forthcoming, the follow up 'what gives?' led to an interesting exchange - Purism actively refused to moderate their instance, because these were paying users. No matter how detailed the reports, no matter how egregious the messages coming from their users, they were paying users, first and foremost, so aside from 'don't break our servers', there were basically no rules. Higher-ups at Purism doubled down on this messaging, so pretty much every instance I've interacted with started suspending federation with Librem One - their only recourse to stem the tide of abusive messaging coming from it, and have been extremely wary of Purism ever since.

Other little tidbits show up from time to time, like how their Marketing Director ragged on Mozilla for supporting RiseUp.net, saying they were supporting domestic terrorism, and then tried to backpedal when called out for it.