If you work with a database and are asked to alter the table structure to comply in advance for citizenship or gender categorizations it's really important to NOT do it.
"The governor is concerned about all this stuff they want us to update our record keeping so we store both gender AND biological sex."
"We need fields to store the country of origin of people's parents."
If you don't have the power to rebuff this yourself, ask for help. At minimum ask for help online anonymously.
like this
reshared this
myrmepropagandist
in reply to myrmepropagandist • • •Depending on your job you probably have in the past made compromises. Maybe to keep your job. Maybe to survive. This is a bright line. If you are asked to be the one to update the table don't let it be your fingers typing those changes.
If you can't just say "No I won't do that." Stall, run away, feign incompetence. Just don't let it happen.
I suspect this might be where the rubber hits the road first for us around here.
Nothing has changed. You do not have to do it. It is not even ordained.
like this
Glowing Cat of the Nuclear Wastelands and Doug Nix like this.
reshared this
M.S. Bellows, Jr., The Witch of Crow Briar, Pseudo Nym, The Doctor, Lazarou Monkey Terror 🚀💙🌈, Daniel 🏳️🌈 Jilg, Andres S, Aaron, Michał "rysiek" Woźniak · 🇺🇦, your auntifa liza 🇵🇷 🦛 🦦, Keira (She/Her), Shannon Prickett, Cainmark Does Not Comply 🚲, May Likes Toronto, Limnobotanik, Solarbird, spiegelmama, Aral Balkan, Jayne 🇪🇺🏳️🌈, Vincent 🦾 🤖 and annajayne 🏳️⚧️🙏🏳️🌈 reshared this.
myrmepropagandist
in reply to myrmepropagandist • • •like this
Glowing Cat of the Nuclear Wastelands and Doug Nix like this.
reshared this
Steve Easterbrook, AleAvila3k, M.S. Bellows, Jr., Daniel 🏳️🌈 Jilg, Geoff Berner, Aaron, Debbie Goldsmith 🏳️⚧️♾️🇺🇦⧖, your auntifa liza 🇵🇷 🦛 🦦, Keira (She/Her), TayFoNay🍿🇺🇦, Pollinators, Lazarou Monkey Terror 🚀💙🌈, Shannon Prickett, Cainmark Does Not Comply 🚲, May Likes Toronto, Limnobotanik, mcc, Kevin Russell, apocalypselog, Aral Balkan, CaveDave and Cycling Stu reshared this.
myrmepropagandist
in reply to myrmepropagandist • • •I know someone who rebuffed such a request. Boss was apologetic "it's what the higher ups want, oh *I* think it's a lot of nonsense, but I don't want us to be out of step ... blah blah"
It was proposed to them in sheepish way. They said it would be a lot of work, not add anything of value, and most important they would not do it. It didn't come up again.
Fascism can be the work of zealots, but there are also many sheepish middle management helping hands who "don't even believe in this really"
like this
Glowing Cat of the Nuclear Wastelands and Doug Nix like this.
reshared this
myrmepropagandist, John Mark ☑️, PJChris 🇨🇦, Paul Cantrell, Deborah Hartmann Preuss, pcc, Daniel 🏳️🌈 Jilg, The Doctor, Geoff Berner, Aaron, Glowing Cat of the Nuclear Wastelands, Eric Lawton, Debbie Goldsmith 🏳️⚧️♾️🇺🇦⧖, your auntifa liza 🇵🇷 🦛 🦦, Sally Strange, Shannon Prickett, Cainmark Does Not Comply 🚲, May Likes Toronto, Limnobotanik, Hylke 🍵, Elyse M Grasso, Dave Howcroft and annajayne 🏳️⚧️🙏🏳️🌈 reshared this.
myrmepropagandist
in reply to myrmepropagandist • • •With the sheepish ones just letting them know you won't do it, (that it crosses the bright line) can make them back off some of the time.
This can be very scary and if you are thinking "but I could be fired" I understand that. Ask for help. Talk about it outside of work or with people you trust. Don't go looking for an excuse to comply and not feel bad about it. If you do you should feel bad.
Find a way to NOT do it instead.
like this
Glowing Cat of the Nuclear Wastelands and Doug Nix like this.
reshared this
myrmepropagandist, The Doctor, Daniel 🏳️🌈 Jilg, Aaron, May Likes Toronto, mekkermuis, Limnobotanik and annajayne 🏳️⚧️🙏🏳️🌈 reshared this.
myrmepropagandist
in reply to myrmepropagandist • • •I'm honestly just psyching myself up for if I need to do this kind of thing again. I might.
It's the whole "we're just doing it to go along with what's happening now" ethos that I think might hold the most little victories for us.
So many terrible things happen because of people just going along with a bunch of little bad things that come together into a much more ugly and unstoppable bad thing.
Doug Nix likes this.
reshared this
Guy LeCharles Gonzalez, Ms. Que Banh, Kenneth John Bardsley, Pseudo Nym, Aaron, Solarbird, Eric Lawton, Debbie Goldsmith 🏳️⚧️♾️🇺🇦⧖, Limnobotanik, Kim Possible and Ω 🌍 Gus Posey reshared this.
Coach Pāṇini ®
in reply to myrmepropagandist • • •Doug Nix likes this.
clarkiestar reshared this.
Maggie Maybe
in reply to myrmepropagandist • • •I love that this energy is back, shit if I had known the resistance would come back immediately this hard I would have voted for Trump myself.
I don’t know how long it will take for people to stop spreading disease for Trump’s economy but maybe we can do that tomorrow?
Doug Nix likes this.
Mer-fOKxTOwl
in reply to myrmepropagandist • • •Doug Nix likes this.
ಚಿರಾಗ್ 🌹✊🏾Ⓥ🌱🇵🇸 (he/him)
in reply to myrmepropagandist • • •Matt Hamilton
in reply to myrmepropagandist • • •Doug Nix likes this.
Kenneth John Bardsley
in reply to myrmepropagandist • • •David Mitchell
in reply to myrmepropagandist • • •Doug Nix likes this.
Aaron reshared this.
PhDog
in reply to myrmepropagandist • • •We're here for you. We won't just LET each other be Eichman.
@futurebird
Doug Nix likes this.
PhDog
in reply to myrmepropagandist • • •There is a legendary problem in US government graph analytics/entity alignment circles called the "Maria Gomez Problem."
When you have a bunch of records (e.g. financial transactions, phone calls, etc.) It's important to keep track people across them, even when. The records store slightly different information (that's entity alignment). So one DHS analyst, working on SA cartels, aligned everyone named "Maria Gomez." The system Palintir built for them had no way to undo it.
@futurebird
Doug Nix likes this.
Stefan Edward Jones
in reply to myrmepropagandist • • •You've probably seen the Simple Sabotage Manual by now, but just in case:
gutenberg.org/files/26184/2618…
There's a whole section on fucking up things through bureacracy.
The Project Gutenberg eBook of Simple Sabotage Field Manual, by Office of Strategic Services
www.gutenberg.orgArto Koistinen
in reply to Stefan Edward Jones • • •I wonder what the original writers would have thought if they’d known their work would one day be used to thwart a fascist government in the US.
Doug Nix likes this.
Aaron
in reply to myrmepropagandist • • •Doug Nix likes this.
Aaron
in reply to Aaron • • •Doug Nix likes this.
🇨🇦🇩🇪🇨🇳张殿李🇨🇳🇩🇪🇨🇦
in reply to Aaron • • •Irenes (many)
in reply to myrmepropagandist • • •Chris Snazell
in reply to myrmepropagandist • • •by way of inspiration:
In the 70s, a bunch of workers in East Kilbride 🏴 grounded half of Chile's air force after Pinochet's coup. For 4 years they refused to fix the engines for Chile's Hawker Hunter aircraft.
There's a documentary about it "Nae Pasaran":
scottishdocinstitute.com/films…
Nae Pasaran - Feature - Scottish Documentary Institute
Scottish Documentary InstituteKees van Malssen reshared this.
Lúmëcolca
in reply to myrmepropagandist • • •Kim Possible
in reply to myrmepropagandist • • •I want people to challenge these folks on every lie, every distortion, every act of malice, every obfuscation, never letting up, not for one second, not now, not in the future, not ever.
They do not get to be comfortable in the performance of their acts of evil and cruelty, no matter how minor their trangressive behavior may seem to others. Get in their faces, speak up in public, stand up, push back, speak out, without ceasing.
Ω 🌍 Gus Posey reshared this.
patter
in reply to myrmepropagandist • • •katzenberger 🇺🇦
in reply to patter • • •@patterfloof
For your eBook reader:
gutenberg.org/ebooks/26184
@futurebird
Simple Sabotage Field Manual by United States. Office of Strategic Services
Project GutenbergRobert [KJ5ELX]
in reply to myrmepropagandist • • •Rachel Rawlings
in reply to myrmepropagandist • • •Trump's already threatening to take away my student loan cancellation in addition to my civil rights. I'm not afraid of a mere employer.
(I've also been successful in the past here about refusing things that felt uncomfortable from an infosec, moral, or "that's where my grandfather died" perspective.)
The Witch of Crow Briar
in reply to Rachel Rawlings • • •Rachel Rawlings
in reply to The Witch of Crow Briar • • •The Witch of Crow Briar
in reply to Rachel Rawlings • • •Maggie Maybe
in reply to myrmepropagandist • • •Andy Wootton
in reply to myrmepropagandist • • •Patrick McLaughlin
in reply to myrmepropagandist • • •Dawdle.
Delay.
Sabotage it.
(Fuck it up so that it will have to be redone when they find it’s inadequate and doesn’t work. Try to make it harder to fix than it would have been to do in the first place — even better, not worth trying to fix.)
Eric Lawton
in reply to myrmepropagandist • • •Daniel Brotherston
in reply to myrmepropagandist • • •Also, learn lessons from these middle managers. If you aren't empowered to say no, then use their strategies for avoiding things you don't want to do, create processes to function as obstacles, create arbitrary requirements that work as obstacles.
E.g., "Oh sure, I can do that no problem, I just need you to fill out this project intake form."
"Oh definitely, that's a great, form, I can't help but see that you left this section blank, unfortunately I'm going to need you to fill in the section explaining the strategy for rollback in the case of emergencies."
"I'd love to help you with this, but unfortunately our technical standards require us to justify all changes using this scoring point system."
Etc., etc.,
We've spent decades watching this bullshit be used to obstruct, delay and defer progress, we can use the same tactics to obstruct, delay, and defer anti-progress. It won't work as well, because fascists don't care about following the rules, but there's enough people who don't want to think of themselves as fascists around that it will still be effective.
reshared this
Shannon Prickett, Deborah Hartmann Preuss, pcc and Aaron reshared this.
rob
in reply to Daniel Brotherston • • •@danbrotherston Yes, this. And ask for clarifications on minute details. Once they make a decision on all of those, find a new detail to ask about. Say that you've realized in testing that in order to implement this, you need to address [complicated tech debt] first.
Basically, when push comes to shove, draw the bright moral line, but if you're in a position to sabotage things without getting caught, do that, too.
Future Sprog
in reply to Daniel Brotherston • • •Also, get those exceptions in writing, in an email, in Slack, printed off and taken home.
In 2030 when you’re dragged in front of the court to explain your role in the Torment Nexus you can show you delayed as much as you could but it was forced on you.
@danbrotherston @futurebird
DougMerritt (log😅 = 💧log😄)
in reply to Daniel Brotherston • • •Nice. Perhaps you could write a field manual about this!
@pineywoozle ‘s #3WordNote
in reply to myrmepropagandist • • •myrmepropagandist
in reply to @pineywoozle ‘s #3WordNote • • •That goose meme
"what kind of 'step' do you 'not want to be out of'?"
"What Kind Of Step!!"
@pineywoozle ‘s #3WordNote
in reply to myrmepropagandist • • •Gerbrand van Dieyen
in reply to myrmepropagandist • • •scary stuff to think about. Reminds me of a medical application that used a binary field to store gender.
Best practice for any data is to use a single char field. Takes the same amount of space and saves you a lot of trouble later.
kern
in reply to myrmepropagandist • • •web.archive.org/web/2020022517…
The CIA removed their WWII workplace sabotage manual from their website but you can still find it on archive dot org
reshared this
Deborah Hartmann Preuss, pcc, Solarbird, Elyse M Grasso and Dendan Setia (Nins) reshared this.
Andy Wootton
in reply to myrmepropagandist • • •reshared this
Democracy Matters, Eric Lawton and -rb reshared this.
Sascha
in reply to myrmepropagandist • • •These kind of lists always remind me of the so called "pink lists" containing names and addresses of homosexuals. These lists were gathered by the German police in the beginning of the last century.
With the rise of the Nazis, these lists became a life-threatening burden for the women and men on them.
The rise of the Nazis was paved above all by the fact that ordinary people turned a blind eye.
So, ordinary people can prevent the rise of fascists.
Aaron reshared this.
Resistor McResistanceFace
in reply to myrmepropagandist • • •Michał "rysiek" Woźniak · 🇺🇦
in reply to myrmepropagandist • • •this!
Also, if you are being forced to do this, ask for this request/order *on paper* (or at least in writing).
I have been asked, at the eve of my IT career, to do a slightly unethical thing. I refused, but was told I have to do this anyway. I said: fine, but I would like this on paper, including the acknowledgement of my concerns.
It was never spoken of again, and never implemented. I kept my job, never had any grief from the higher ups about it either.
Paper trail is power.
2something likes this.
reshared this
Paul_IPv6, nen, your auntifa liza 🇵🇷 🦛 🦦, Andres S, Callalily, Dave Rahardja, Lazarou Monkey Terror 🚀💙🌈, Richard Bairwell, Cainmark Does Not Comply 🚲, Poul-Henning Kamp, decibyte and Kat O’Brien reshared this.
Raven667
in reply to Michał "rysiek" Woźniak · 🇺🇦 • • •Adam Shostack
in reply to Michał "rysiek" Woźniak · 🇺🇦 • • •Michał "rysiek" Woźniak · 🇺🇦 reshared this.
I Thought I Saw A 2
in reply to Michał "rysiek" Woźniak · 🇺🇦 • • •Michał "rysiek" Woźniak · 🇺🇦
in reply to I Thought I Saw A 2 • • •@ithoughtisawa2 sure. But they can do that regardless of the paper trail.
The paper trail provides you with a CYA policy. If they issue such an unethical directive and then try to blame it on you, you have something to prove you were pushing back against it.
"The more paper, the cleaner the arse", as they used to say in the Soviet Union.
Misuse Case
in reply to Michał "rysiek" Woźniak · 🇺🇦 • • •2something likes this.
reshared this
Michał "rysiek" Woźniak · 🇺🇦, myrmepropagandist, Callalily, your auntifa liza 🇵🇷 🦛 🦦 and Cainmark Does Not Comply 🚲 reshared this.
myrmepropagandist
in reply to Misuse Case • • •@MisuseCase @rysiek
Totally although I think a big reason why this is so important is that it is the kind of thing that can compromise your immortal soul. (Even if you don't think you have one.)
Cainmark Does Not Comply 🚲 reshared this.
Coach Pāṇini ®
in reply to myrmepropagandist • • •☝️💯🔥
but you can call me the fediverse squick
in reply to myrmepropagandist • • •Cainmark Does Not Comply 🚲
in reply to Misuse Case • • •Best advice I had from the best boss I ever had was: Save everything. Every email, every letter, every post-it note. Never volunteer for anything. Make sure your job is spelled out and nothing gets quietly added (got monumentally screwed on the last part when they refused to fill back necessary full time positions).
A post-it note signed by the person who was trying to get me into trouble for doing what they specifically asked me to do worked wonders.
Michał "rysiek" Woźniak · 🇺🇦 reshared this.
Maggie Maybe
in reply to Misuse Case • • •@MisuseCase YES. Absolutely and the way I used to do this without sounding accusatory or aggressive as I would just make a joke about ADHD and I might forget before I even get back to my desk so please send an email.
And if they don’t I just forget before I get back to my desk. And for real, sometimes it wasn’t even on purpose.
2something likes this.
Dark Phoenix 🇺🇦🇨🇦🇬🇱🇵🇦🇵🇸🏳️🌈
in reply to Michał "rysiek" Woźniak · 🇺🇦 • • •Maggie Maybe
in reply to Michał "rysiek" Woźniak · 🇺🇦 • • •@rysiek this is a good idea because when I was suspicious of something I was told to do I actually forwarded that email to my home email, because if I get fired tomorrow I don’t have access to my work email and if I get arrested in six months I’m not going to be able to prove someone else told me to do it (it wasn’t a crime, just sayin’) and IT called my supervisor to tell her I sent the email to my home.
I worked in the mortgage department of a credit union so I thought it would be much more suspicious and problematic if I was printing papers and then squirreling them away into my bag, but I was very very wrong. Lesson learned lol
Sassinake! - ⊃∪∩⪽
in reply to myrmepropagandist • • •Jo-stands on guard, elbows up.
in reply to myrmepropagandist • • •myrmepropagandist reshared this.
Boots Chantilly
in reply to Jo-stands on guard, elbows up. • • •Wulfy
in reply to myrmepropagandist • • •I call that attitude "Driving the cattle-box trains to the death camps"
Ordinary railway workers.
Doing ordinary jobs.
Because "if they didn't do it, someone else would."
Rich
in reply to myrmepropagandist • • •[Edit] How to slow down software dev.
- Ask for complete and clear requirements before you can do any work.
- Take the time to do exhaustive estimates of how long it will take.
- Come up with multiple different implementations.
- Ask the architecture team to review the implementations.
- Request input from the platform team.
- Make sure to get buy-in from all the stakeholders.
- Schedule meetings at inconvenient times, if the team is in multiple time zones make sure that someone will suffer.
- Schedule meeting times without checking calendars first forcing people to ask for (later) reschedules.
- Create a comprehensive QA plan with a full regression test-suite.
- Setup meetings with the UI team to define an API to use the new functionality.
- Use the full iterative UX design process, sketches with feedback, mockups with feedback, UX testing on prototypes.
- Do the first implementation based on incomplete or misunderstood requirements so that rework is required.
Antonio Picornell 🏳️🌈
in reply to myrmepropagandist • • •Seachaint
in reply to myrmepropagandist • • •reshared this
Debbie Goldsmith 🏳️⚧️♾️🇺🇦⧖ reshared this.
hex
in reply to Seachaint • • •Paul Cantrell
in reply to myrmepropagandist • • •David Mitchell reshared this.
Jeremy Kahn
in reply to Paul Cantrell • • •@inthehands
Add fields "genre" (Fr) and "genus" (Latin), set defaults to "dystopian surveillance horror" and "Homo" respectively, argue from etymology
It's a very specific kind of work-to-rule for linguists
Krzysztof Sakrejda
in reply to Paul Cantrell • • •Court Cantrell will not comply
in reply to myrmepropagandist • • •David Mitchell reshared this.
DivideByMcSquankException
in reply to myrmepropagandist • • •schrotthaufen
in reply to myrmepropagandist • • •Siobhan Muir
in reply to myrmepropagandist • • •Alex von Kitchen
in reply to myrmepropagandist • • •There are a few things to consider when updating an existing database:
Are you going to archive the old information, or just add new variables? The second option is simpler but leads to bloat and is harder to document
Are the new data equivalent to old variables, or do you need to collect new data about clients? Might need to discuss this with frontline staff about how new data collection affects their workload. Are you going to allow missing values in the system for client who don't want to update their information, or refuse service to them?
What are the security requirements for this new data? Specific to this situation; do you need the parent's consent to record information about them, or is that something you can legally do with just the child's permission? Does information about assumed gametes count as medical information? That usually has different security rules.
Might want to check with legal
Speaking of legal stuff in this situation; there are likely to be challenges to all this. Is it worth changing all this and then changing it all back? Wha
... show moreThere are a few things to consider when updating an existing database:
Are you going to archive the old information, or just add new variables? The second option is simpler but leads to bloat and is harder to document
Are the new data equivalent to old variables, or do you need to collect new data about clients? Might need to discuss this with frontline staff about how new data collection affects their workload. Are you going to allow missing values in the system for client who don't want to update their information, or refuse service to them?
What are the security requirements for this new data? Specific to this situation; do you need the parent's consent to record information about them, or is that something you can legally do with just the child's permission? Does information about assumed gametes count as medical information? That usually has different security rules.
Might want to check with legal
Speaking of legal stuff in this situation; there are likely to be challenges to all this. Is it worth changing all this and then changing it all back? What are the consequences for collecting this information now if things get reverted
Accuracy: how are you going to validate all this data? What are the security and data retention obligations imposed by recording additional validation information? Do you impute missing values, and if so what degree of error is acceptable?
What level of accuracy is needed here generally?
What are the exact definitions of these items, and do those definitions cause legal or implementation problems? If you're allowing non-response do those collecting the information (staff, UI designers) have to tell people it's an optional item? Does making it optional have legal consequences under these orders?
Any expected PR consequences for all this?
Just generally; do you need this information? Can't leak it if you don't collect it in the first place, so data that doesn't exist is the best for security. It's also space efficient and easy to document (who maintains the database documentation? better include them)
And remember to document any decisions and get the minutes signed off by everyone that's affected
mega
in reply to myrmepropagandist • • •yes opposition may not always be easy but you can just fail.
Not even via incompetence. You can take your time looking at the requirements and make a highly optimized implementation (for the sake of performance) that is difficult to get right and even more difficult to fix your data once you got it wrong.
Alternatively you can build a highly expressive solution where the extensibility causes all relevant queries impossible to answer (because different teams used different names).
🇨🇦🇩🇪🇨🇳张殿李🇨🇳🇩🇪🇨🇦
in reply to myrmepropagandist • • •Don't feign incompetence. BE incompetent. Be incompetent in plausible ways that leads to massive data loss.
Oopsie.
Sorry.
I'll try to do better next time.
Scott 🏴😷
in reply to myrmepropagandist • • •myrmepropagandist
in reply to Scott 🏴😷 • • •𝓐𝓷𝓭𝔂𝓣𝓲𝓮𝓭𝔂𝓮 𓀤
in reply to myrmepropagandist • • •If you MUST add such fields, maybe you could "accidentally" set them up so those IN the database can change their own entries.
@futurebird
Simon Lucy
in reply to myrmepropagandist • • •As this would require in most cases data to populate these fields this would seriously compromise the stability of the database.
We need a study on how this data is to be collected and verified and all of the possible cases such as unknown data, refusal to provide data and insufficient verification.
We will also need policies and procedures covering this and any liability we may incur in inadvertent incorrect data and its application in other systems.
Gehennam
in reply to myrmepropagandist • • •Matt Hodgkinson
in reply to myrmepropagandist • • •Rich Puchalsky ⩜⃝
in reply to myrmepropagandist • • •Yes. If anyone wants historical reading, this goes all the way back to punch cards:
en.wikipedia.org/wiki/IBM_and_…
book by investigative journalist Edwin Black
Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)jhamby
in reply to Rich Puchalsky ⩜⃝ • • •@richpuchalsky Thanks, I was scrolling through the replies and hoping someone had already mentioned IBM and the Holocaust. Such an important book for everyone to read.
There's a particular aspect of the book that this thread reminded me of: France was much better at noncompliance than the Netherlands, which is why a larger % of French Jews than Dutch Jews survived. Being sticklers for rules is normally an admirable national trait, but not when it's compliance with evil.
Urzl
in reply to myrmepropagandist • • •irelephant likes this.
hex
in reply to myrmepropagandist • • •"but how do I get away with that?"
openculture.com/2024/11/the-ci…
Discover the CIA's Simple Sabotage Field Manual: A Timeless Guide to Subverting Any Organization with "Purposeful Stupidity" (1944)
OC (Openculture.com)irelephant
in reply to myrmepropagandist • • •Jennifer Em likes this.
Jennifer Em reshared this.
Solidaires Informatique
in reply to myrmepropagandist • • •meldanor
in reply to myrmepropagandist • • •And then in the migration there will be an error resulting in a costly rollback and downtime and a few weeks of debugging.
Do this a few times and no product manager will try it again.
cobalt
in reply to myrmepropagandist • • •[ˈɹæ.ɹɪ]
in reply to myrmepropagandist • • •Daniel T 🌻
in reply to myrmepropagandist • • •as an old DB guy who cares very much about this, life can be much easier if you have European clients.
Gender of any sort is one of those fields your company *does not need*, it's merely traditional to include it.
So you can use that to note that under GDPR it's best if you don't collect it at all
James O'Malley
in reply to myrmepropagandist • • •First, read en.wikipedia.org/wiki/Weapons_…
My strategy is usually some variation of the following (parenthesis is your excuse if caught):
1) Silently don't do it. say yes, and then just don't do it (forgot).
2) Do it, but don't update the front end to comply (oops, oversight)
3) Do it, update the front end, but then don't maintain it until it silently breaks (oversight, forgot, update must have broken it)
4) Do it, but then after a month or so, remove it, or send the data to /dev/null (oh, you still needed that?)
5) Store the data as a hash or some obfuscated string (for privacy), and then "lose" the index (I don't know how that happened!)
Never say no. Just demure. Yes, yes, tomorrow, I'll get to it, don't worry... and then just go what we call in Puerto Rico, "brazos caídos" fallen arms or limp arms.
book by James C. Scott
Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)James O'Malley
in reply to myrmepropagandist • • •They will never come back to you. This stuff is so complicated and difficult to track. In an ideal world, management has PERFECT vigilance over all aspects of a project, but this has never been the case in my own experiences.
It also works at the country/nation level too! Weapons of the Weak was introduced to me by my anthropologist partner and it's changed how I deal with the world.
Space Catitude 🚀
in reply to myrmepropagandist • • •Or, you know...
"We can implement that, yeah, but it's more complicated than it first appears."
"The field lengths aren't really clear, and we'll need to get those right before invest in migrating this entire database."
"I've scheduled a meeting with a group of experts to outline how we can study the problem and get stakeholder input on the correct model to use in our database."
Let it snow....
Jes Wolfe
in reply to myrmepropagandist • • •StarkRG
in reply to myrmepropagandist • • •PKPs Powerfromspace1
in reply to myrmepropagandist • • •myrmepropagandist
in reply to PKPs Powerfromspace1 • • •Read the responses to my post from everyone here, there are many exciting ideas for people with all levels of power in these situations.
And really if you say "oh OK when I can get to that" then do a bunch of other things and make a big deal about that and never get to it can also work.
They may just forget about it.
Future Sprog
in reply to myrmepropagandist • • •Also it’s a real good time for software engineers and DBAs to require:
- full design documents
- approval from the product owner
- prioritisation at the next quarterly product meeting
- (accidentally forget about the ticket)
- user stories
- test evidence
- sign off from correct product owner
- PR approval before merge
- unit tests
- full test coverage
- approved change paperwork
- (sorry missed the change window)
- downstream sign off
It’ll take at least 5 years to add that.
@futurebird
Patrick McLaughlin
in reply to myrmepropagandist • • •Nicole Parsons
in reply to myrmepropagandist • • •Changes to data gathering practices are an early warning sign...
en.m.wikipedia.org/wiki/IBM_an…
theguardian.com/world/2002/mar…
cepr.org/voxeu/columns/fiscal-…
en.m.wikipedia.org/wiki/Judenv…
IBM 'dealt directly with Holocaust organisers'
Oliver Burkeman (The Guardian)TheJaySunday
in reply to myrmepropagandist • • •Patrick McLaughlin
in reply to myrmepropagandist • • •You can practice malicious incompetence. All while superficially complying.
I *absolutely* affirm refusing to do it, but if you are pretty sure that they’ll just get someone else to do it, or you’re really trapped and can’t afford to refuse (and quit/be fired), then become incompetent.
Slow.
Make stupid errors. Especially ones that cause damage and/or are hard to undo. Build on top of fundamental errors. Sabotage. Delay. Obfuscate. Be a cunning little non-compliant weasel.
Caitlin McCann
in reply to myrmepropagandist • • •Sam Easterby-Smith
in reply to myrmepropagandist • • •Enola Knezevic
in reply to Sam Easterby-Smith • • •Sam Easterby-Smith
in reply to Enola Knezevic • • •Markus Redeker
in reply to myrmepropagandist • • •Sensitive content
René Carmille (en.wikipedia.org/wiki/Ren%C3%A…) was a French statistician during the German occupation in WW2. When ordered to prepare a list of Jewish people for deportation, he and the people of the department he headed worked as slowly and obstructively as possible, so that the report was delayed by at least two years.
Carmille was finally caught, also because of other Résistance activities, and died in a concentration camp. May he be well remembered.
(“However, the police did not need Carmille's files. They organized raids and deportations from their own manual files.” — Yes, but we never know which effect our actions will have. If they are good, we should do them anyway.)
comptroller general of the French Army and member of French Resistance (1886-1945)
Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)reshared this
myrmepropagandist, Femme Malheureuse, Clifton Royston and Shannon Prickett reshared this.
David Penfold
in reply to myrmepropagandist • • •gunstick
in reply to myrmepropagandist • • •Klongeiger
in reply to myrmepropagandist • • •INIT_6
in reply to myrmepropagandist • • •Jackie 🍉
in reply to myrmepropagandist • • •Lightfighter
in reply to myrmepropagandist • • •MPFantod
in reply to myrmepropagandist • • •Mark Dunne
in reply to myrmepropagandist • • •“I’m concerned about how this interacts with our CCPA/GDPR obligations, do we have sign off from legal/security/our chief compliance officer and a plan to update our policy and process documents?”
Realistically only relevant at a certain size of company, but a fine way to slow things down. And has the advantage of being a correct thing to ask!
Doug Nix likes this.
CaptMorgan
in reply to myrmepropagandist • • •Mikołaj Hołysz
in reply to myrmepropagandist • • •I haven't thought of this before, but this will cause so much IT chaos.
Many people in the US have non-US-issued documents that have a gender on them, and the US government needs to have accurate knowledge of what those documents say (regardless of whether it considers what they say to accurately reflect reality).
Meanwhile, those same people may also have US-issued documents, and those documents will also have a "gender-looking thing" on them. The US government also needs accurate knowledge of what those documents say.
For some people, the value on the US-issued documents will no longer be allowed to match the value on the non-US-issued documents, therefore the question of "but should I expect 'male' or 'female' when this person shows us their ID" will no longer be answerable by a single database field.
Private organizations will also be affected by this, as many will need to separate "gender, as in what the person is expected to have when showing us ID" versus "what this person actually wants to get addressed by."
European organizations already have
... show moreI haven't thought of this before, but this will cause so much IT chaos.
Many people in the US have non-US-issued documents that have a gender on them, and the US government needs to have accurate knowledge of what those documents say (regardless of whether it considers what they say to accurately reflect reality).
Meanwhile, those same people may also have US-issued documents, and those documents will also have a "gender-looking thing" on them. The US government also needs accurate knowledge of what those documents say.
For some people, the value on the US-issued documents will no longer be allowed to match the value on the non-US-issued documents, therefore the question of "but should I expect 'male' or 'female' when this person shows us their ID" will no longer be answerable by a single database field.
Private organizations will also be affected by this, as many will need to separate "gender, as in what the person is expected to have when showing us ID" versus "what this person actually wants to get addressed by."
European organizations already have this problem (this is compounded here by the lack of a 'title' concept and European burreaucracies that makes gender changes extremely difficult for many).
myrmepropagandist
in reply to Mikołaj Hołysz • • •@miki
OK but what I'm saying is making that separate is facilitating this attempt at change.
Attempt. It's not done yet. No one should comply with any of it.
Uli Kusterer (Not a kitteh)
in reply to myrmepropagandist • • •Also, even if you find you can’t safely refuse doing such work, you can at least try to make it obvious.
Add it to the documentation, include it in the release notes, add a switch to turn it off that may be noticed, inform user forums of the existence of these features to give them the option to complain.
Depending on what precisely you're working on, there are small ways in which you might be able to give others in a more safe situation the information/tools they need to do more.
Jenny 🏳️🌈 🔜 FOSSGIS
in reply to myrmepropagandist • • •Sphinx of Black Quartz
in reply to myrmepropagandist • • •Tech workers asked to enable fascism should realize deliberate, plausibly-deniable incompetence can be a very powerful form of sabotage. Just sayin'.
en.wikisource.org/wiki/Simple_…
Simple Sabotage Field Manual/Specific Suggestions for Simple Sabotage - Wikisource, the free online library
en.wikisource.orgreshared this
Hugs4friends ♾🇺🇦 🇵🇸😷 and Jennifer Em reshared this.
RudiPf
in reply to myrmepropagandist • • •en.m.wikipedia.org/wiki/1943_b…
attack on Nazi occupation forces by Dutch resistance
Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)Galbinus Caeli 🌯
in reply to myrmepropagandist • • •Scott Miller 🇺🇦 🇺🇸
in reply to myrmepropagandist • • •Philip Mallegol-Hansen
in reply to myrmepropagandist • • •If it’s too risky to say no outright, I bet most engineers instinctively already know: There are ways to effectively kill a project without breaking the rules (Because we spend so much time fighting *against* that very force ordinarily):
Insist on CAB approvals. Make sure all stakeholders are in agreement about the details. Did we get sign off from legal?
Before you know it, following the rules to a tee makes it impossible for anything to get done.
Jeff C. 🇺🇦
in reply to myrmepropagandist • • •I left a job I loved on my own volition for a much, MUCH smaller reason. A line in the sand so infinitesimal by comparison it is only barely worth mentioning.
This should be an easy decision by any technologist.
reshared this
Shannon Prickett reshared this.
Oregon Wine Woman
in reply to myrmepropagandist • • •I am Jack's Lost 404
in reply to myrmepropagandist • • •Not unrelated: kolektiva.social/@Hex/11386679…
hex
2025-01-21 14:24:11
Not unrelated: kolektiva.social/@Hex/11386679…
hex
2025-01-21 14:24:11
Regine
in reply to myrmepropagandist • • •This thread might be helpful in camouflaging non-compliance: kolektiva.social/@Hex/11386679…
hex
2025-01-21 14:24:11
This thread might be helpful in camouflaging non-compliance: kolektiva.social/@Hex/11386679…
hex
2025-01-21 14:24:11
Jennifer Em likes this.
Thomas Sturm
in reply to myrmepropagandist • • •@ansuz Agree enthusiastically to make those changes to prevent somebody else from actually doing it, then begin to implement the most complex version of the changes with many subtle flaws.
Document extensively, but use dueling systems with broken cross-links.
Don’t invite one different stakeholder to meetings on a rotating basis.
Update most but not all test systems to the latest beta of the OS.
Use intriguing exotic char encodings for some tables.
Mr. Lance E Sloan (IRL) 👤
in reply to myrmepropagandist • • •myrmepropagandist
in reply to Mr. Lance E Sloan (IRL) 👤 • • •@sloanlance
On these issues of helping to build human dislocation, segregation and discrimination machines there is a tendency for the actors to rationalize and externalize their responsibility for violence. A tendency to say “since we all benefit from these monstrous systems it’s not my fault.”
But to help build a new intake shaft for a factory that chops up humans is not excusable. To design it, to shape it? No. That is where we all need to say “no further I will not.”
reshared this
myrmepropagandist, Cthulku and Amro has been reshared this.
Mr. Lance E Sloan (IRL) 👤
in reply to myrmepropagandist • • •What if the development is not intended for discrimination or segregation?
Obviously, if a project is specifically intended to HELP PREVENT bigotry and aid the people for whom the data is collected, that would be a good thing. What about projects that are clearly not inhumane, but their aid to people is ambiguous? What is the harm in those projects collecting this data?
myrmepropagandist reshared this.
myrmepropagandist
in reply to Mr. Lance E Sloan (IRL) 👤 • • •@sloanlance
My response, not expert, is that the road to hell is paved, consider with *what*. If you think your data collection could cause harm, even if you don’t know how can you talk to multiple people who are in the group who could be harmed (not just one!) if it’s non-citizens or trans people or POC can you get advice from someone with skin in the game who might notice what you could miss?
Mr. Lance E Sloan (IRL) 👤
in reply to myrmepropagandist • • •Thank you for the kind, reasoned response. I'll keep your advice in mind.
In fact, thank you to almost everybody who responded to me. Everybody except the one person who compared me to #convictedFelon #DonaldTrump and when I called them out on it, escalated the hate with ad hominem attacks.
I hoped I wouldn't see that kind of behavior after I migrated away from Twitter/X.
Jeremy
in reply to myrmepropagandist • • •reshared this
myrmepropagandist and No Gods , no Masters! RESIST reshared this.
Aquarius
in reply to Jeremy • • •Amro has been
in reply to Mr. Lance E Sloan (IRL) 👤 • • •Never is an absolute
You respond to a post that starts with "If" 🤷🏻♀️
Mr. Lance E Sloan (IRL) 👤
in reply to Amro has been • • •Doug Nix likes this.
Walrus 🏴
in reply to myrmepropagandist • • •Hella
in reply to Walrus 🏴 • • •A dropped table/database is usually easy to restore from backup. Tampered data is less easy to detect.
Doug Nix likes this.
Walrus 🏴
in reply to Hella • • •If they even have backups, of course.
Hella
in reply to Walrus 🏴 • • •Orgs with this type of data do backups. The question is, if they have *working* and tested backup.
Frank Heijkamp
in reply to Hella • • •Christian Kent
in reply to myrmepropagandist • • •And an associated reminder that the number of countries of birth of parents is INFINITE
Just as an example, both my parents were born in countries that don’t exist anymore if you go by their common names; but if you want formal state names, in one case you’d have to look up things like the Weimar Republic. And that’s an easy one to add to the drop-down list. I haven’t even gone into generations who have died yet, because it grows exponentially after that.
Endless validation …