The only correct response to "Does kink belong at Pride?" is "Are you a cop?"
I don't have a problem. I can stop buying the same top in different colours whenever I want.
of course you have blue hair and pronouns and a kubernetes cluster
✨ You have come across a wandering shop! ✨
You may pick one bundle of treasures to aid you on your adventure. Choose carefully!
⏳⌛️
Ah, wise choice. What will you do with them, I wonder.
🔁 Boost to send me on to other wayward travelers! 🌬️ May our paths cross in the future!
Options: (choose one)
θΔ ⋐ & ∞
I know others have said it, but I want to reiterate that no cops belong at pride.
That includes queer cops and cops out of uniform.
No cops at pride, period!
ugh, the state of gui toolkits on linux is just sad
the nice:
qt4 is thankfully gone for good
afaict, qt5 => qt6 is not a difficult upgrade, and UIs tend to be fairly consistent between the two, so there’s nothing to complain about there
qwidget apps generally feel pretty decent
the not nice:
gtk2 can’t die fast enough (gimp 
)
gtk4, despite being filled with cool tech, is somehow a huge regression from gtk3, again
the default theme is different and afaict they’ve just removed theming support entirely 
qtquick creates another rift in UI consistency
despite KDE’s best efforts to create a compatibility layer for qstyle, there are unfixable impedance mismatches which cause problems with some themes 
e-fucking-lectron 
at this point we’re basically competing with windows for how many GUI toolkits will “coexist” on a single platform
xdg pls harmonize this shit thanks
Publicly available container images are very similar to USB drives you find in the parking lot. They are meant to be downloaded and run in production.
runescape gives you a shark plush if you complete the 2024 pride seasonal quest. losing my mind rn
hi, hello, I finally bring to you: a write-up/paper/whatever you want to call it of how the Windows servicing stack works and how desktop Windows images are assembled by Microsoft's build systems, in turn exposing a very big part of the mechanisms behind the OS installation process
this has been in the works for months now, and I'm so glad to have finally finished documenting this unnecessarily overengineered mess of a package management system.
would not have been possible without the help of several others.
![section of a paper I authored titled "Windows Component-Based Servicing Overview", documenting a part of the initial foundation image generation phase:
The main gist of the whole assembly process boils down to three important factors: the Windows Componentization Platform (and the main CBS servicing stack), the Windows foundation image, containing the absolute dependencies needed to build the image, and the aforementioned component and update package manifests (including the raw component binaries).
Windows foundation images are created by respectively calling C++ functions "Create New Windows" and "Create New Offline Store" in the servicing stack library "WCP.dll", short for the Windows Componentization Platform:
[Code blocks for functions related to Windows foundation image generation.]
(Disclaimer: As of Windows 10 Anniversary Update. These functions’ variables may have been changed in later Windows NT versions.)
Microsoft uses a tool officially dubbed the Trusted Installer Client Console to build the Windows image, which would call these functions in a separate tool and then perform the staging process. The foundation image may be placed inside of a virtual hard disk image that will contain the actual OS image. Further servicing operations made after initial neutral image staging process will eventually resort to image servicing operations made through automation by passing commands over to the Deployment Image Servicing and Management Tool.](/proxy/post_attachment/1527/7d9d7a8d6b.png "section of a paper I authored titled \"Windows Component-Based Servicing Overview\", documenting a part of the initial foundation image generation phase:
The main gist of the whole assembly process boils down to three important factors: the Windows Componentization Platform (and the main CBS servicing stack), the Windows foundation image, containing the absolute dependencies needed to build the image, and the aforementioned component and update package manifests (including the raw component binaries).
Windows foundation images are created by respectively calling C++ functions \"Create New Windows\" and \"Create New Offline Store\" in the servicing stack library \"WCP.dll\", short for the Windows Componentization Platform:
[Code blocks for functions related to Windows foundation image generation.]
(Disclaimer: As of Windows 10 Anniversary Update. These functions’ variables may have been changed in later Windows NT versions.)
Microsoft uses a tool officially dubbed the Trusted Installer Client Console to build the Windows image, which would call these functions in a separate tool and then perform the staging process. The foundation image may be placed inside of a virtual hard disk image that will contain the actual OS image. Further servicing operations made after initial neutral image staging process will eventually resort to image servicing operations made through automation by passing commands over to the Deployment Image Servicing and Management Tool.")
fuck medical gatekeeping
i was told i need to complete celeste farewell before they could prescribe me hrt
what the fuck????
Tired: being personally fediblocked
Wired: being personally blocked by a national IT system
(the image is depicting my account, just my account, being blocked)
RE: https://fedi.bapril.pl/objects/9763ac2f-fbcc-4133-bdf9-788933b2b7de