104
UK Google DeepMind employees vote to unionize over its AI defense deals
(www.businessinsider.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 May 2026
104 points (100.0% liked)
Technology
6770 readers
345 users here now
News community around technology, social media platforms, information technology and governmental policy surrounding it.
What doesn't fit here?
The core of the story has to be technology focused.
- If article mentions "AI" in a sentence and then talks about business economics that doesn't make it tech news.
- Gaming is too many layers removed from technology. There are many dedicated communities that are a better fit for it.
- Transporation is too many layers removed from technology. EVs while use many cool technologies have many dedicated communities that are a better fit for it.
- Entertainment is too many layers removed from technology. While sometimes it can fit here, business or cultural aspects of it are a better fit for dedicated communities.
- Cybersecurity. While it heavily focuses on technology, most of the time it's too technical for most people who are not already invested in it. Should be posted in a dedicated communities unless it has broader connection to other tech areas.
Post guidelines
Title format
Post title should mirror the news source title. If you don't like the title of article, look for an alternative source instead of editorializing it.
URL format
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
[Opinion] prefix
Opinion (op-ed) articles must use [Opinion] prefix before the title. Opinion articles refer to articles that their publisher doesn't explictly endorse.
Country prefix
Country prefix can be added to the title with a separator (|, :, etc.) if the news is from a local publisher who doesn't clearly mention the country.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
If someone is interested in moderating this community, message @brikox@lemmy.zip.
founded 2 years ago
MODERATORS
I find it a bit offensive that you assume Google employees can only comprehend the simplest language, and it's coincidentally the language handed to them from on high by Google themselves. (Ah. Dot ML.)
But let's assume you're correct, and engage in a little creativity to simplify employee complaints in order to make it have fewer loopholes.
12 fewer words, 4 fewer loopholes (preexisting surveillance, semi autonomous weapons, selective surveillance, foreign mass surveillance).
Google tech can be used for weapons and surveillance (and are) right now and without AI. If the union wanted that to be their line in the sand then their jobs would cease to exist
Do you just propose the union just adopt Google's exact stance on this? Are you willing to accept a weaker one? A much weaker one, perhaps? Where do you draw your lines?
I propose that the union membership itself knows a fuck a lot better than I do do I'm not gonna not pick specifics I don't personally like with THEIR negotiating position
You were just speaking on their behalf...
Newp
Who said "If the union wanted that to be their line in the sand then their jobs would cease to exist"?
Me. That was a statement of fact
Provide a citation from the union that knows better than you to back up your opinion, please
It's not an opinion to state that Google tech is already used in war
I've been in tech labor organizing for 8 years at this point. I know written documents matter pretty much nothing for organizing, let alone tech workers organizing. And yes, tech workers need a simple language.
The statement you've written is very good to argue on the internet, but it closes any avenue for picking winnable issues in the real world. If the original one sets a clear, achievable goal (canceling a new contract), the one you wrote prevents any kind of realistic demand and sets an unachievable goal for a newly formed union.
I guess we're moving on from the topic of employee understanding on to the topic of negotiation.
On concession: Do they really need to concede to Google talking point verbatim? Why not argue for three gaping loopholes instead of four? Why not add a fifth to smooth things over? Or (even better): in order to differentiate themselves from every AI company that has the same fake "red line" doctrine, they could omit it altogether.
because these statements are instrumental to building power. They are not a draft of a negotiation proposal. They are a galvanizing message for workers, not a formal demand. Without power, formal demands are pointless. To build power, clarity, concreteness and directness beats idealism, rigour and formalism every day.
Okay.... Guess we aren't talking about concessions or simplicity now... Moving on to a new point, 3/3?
If the statements aren't used for negotiation purposes, then they should be much clearer and not tow the Google line, right?
The formal "red line" doctrine is intentionally unclear and based on the idealist belief that AI will somehow become super powerful. Meanwhile a statement without big holes is more concrete, and less shaky wording makes it more direct.