Friendly reminder that OpenRCT2 exists on PC, which is a source port of RCT2 but can effectively merge 1, 2, all of their expansions/addons, has support for custom content (coaster templates, scenarios, etc), and for even deeper modding through plugins.
Plus, games like RCT rarely work very well on controller.
Does the darkreader extension not work with it? That's what I use to auto force/generate dark mode on all sites. Works in mobile Firefox (and defivatives) as well.
Edit: Oh yuck! It kind of works, but just makes the yellow darker.
Well, I was thinking I could empower my users to solve their own problems, and just give them all domain admin.
unjerk
Probably should have put that in the OP, but I was trying to make a post that would be an easy setup for people to respond with horrible ideas like that.
Just another scheme to abstract away responsibility for systemic biases/oppression. Now you don't even have to take responsibility for your (potentially small) part in the end result, because you can just blame it on the computer!
Whatever happened to this 1979 IBM presentation?
I take it to mean that the people pushing requirements for a program/system, the people implementing it, and the people utilizing it all hold a certain measure of responsibility for what is done with it.
My "most dangerous" creation is automation for certain employee onboarding and separation tasks, relating to their network sign in account and email. It is entirely triggered by data from our HR/payroll system, making the HR and each person's manager responsible for the input and results.
The only part that "makes decisions" that might differ from the input is the "sanitizing" of names for email address generation. I use a .Net library built into Windows to "normalize" accented characters like ΓΆ.
I'm comfortable leaning on Microsoft's "normalization" procedure. Better than rolling my own for an edge case that is rare at my workplace. End-users can assign their own "preferred name" in the HR system, and HR can modify the "legal name" values as needed. Lastly, anyone can request their email address to be changed to just about whatever they want at our helpdesk's discretion.
Employee separation processing happens at end of day, with a manual process that HR can kick off for "high risk" ones that must be immediate (like security escorted someone out). There is a metric shit ton of planning put into the aging off of different parts of the employee data, with considerations for short contract renewal gaps, ability to pull critical data from separated accounts within a reasonable timeframe (and with appropriate approvals), and various legal requirements we're beholden to.
Fun fact for separation calls through Teams from HR to remote workers: a user who has been disabled in AD and Entra, who has had their Azure/Entra/365 access tokens revoked, and whose password has been changed... can continue an active video/voice call in teams that started before they were "locked out". They can't access or create any other text chats, file sharing, or even the text chat for the existing call though. Makes it easy for HR to have access removed during the call. The user will still have access to any local content on their machine for as long as they stay logged in, but it's at least something (especially combined with a default block on USB storage to help prevent data exfiltration). Please test yourself before relying on this though, as Microsoft changes shit with Azure daily.
Anyway... the point is, this is shit I thought out, along with a ton of other considerations. I know for certain how my code reacts to things, and I am comfortable with all the potential outcomes even when things go wrong.
When shit goes wrong with it, I openly and clearly point out where it's an issue with input data from HR. When it is a problem with the code, I openly and clearly take responsibility as I wrote the code. I never go "it's the computer's fault". Even if it is some problem with Microsoft's code I hook into, it is my fault for not fully understanding what I told the code to do.
I truly have a hard time comprehending just how comfortable all these people are with the black box nature of AI, especially for such important things like fucking tenant screening.
I wonder how much extra compute it would take to run images through a QR code reader as part of filtering. Resolve the destination.
But then that would confirm that they hit a valid email if they track the image being loaded from their server/cdn.
That's an entirely different situation though, in security and risk.
It's an expected communication confirmed through a secondary channel (The server most likely verbally informed you of the QR code to access the menu). You can confirm that it is from the proper source (unless you distrust the server to have not modified it).
Beyond that, I've never been at a restaurant with menu by QR that did not also have their menu independently verifiable/accessible through their site, meaning you can get the information yourself independently.
All modern phone QR code readers clearly display the code's content, so you can review before following the link. (Not unique to your restaurant situation, but still should be said)
On top of all that, this identified the emails as spam. Unless you don't want the menu, this wasn't.
Data usage to load a link to a PDF with a max of four pages is absolutely negligible.
So to be clear: Don't be an ass to serving staff. They don't set their workplace's policies. If it bothers you that much, stay the fuck home.
Lol, that's one hell of an edge case!
Hahaha, don't underestimate jank ass vendor systems. My workplace has at least one business critical thing using SOAP. We've been spinning our wheels on deprecating the damn thing for three years.
SLEEPER AGENT ACTIVATION BY MEME CONFIRMED
Prisoner 2460206451! You're no one. Lol. Your time is up and your time is up and I'm Javert! You know what that means.
It means I'm freeeeeee~eeeeeee~eeee^eeeee^.
No.
Every time I get reminded of Le Mis I hear this youtube poop in my head and start giggling.
I think I'm just in denial that absolutely everyone involved with the creation and use would want this outcome, or be too dense as to not see this result coming from a mile away.