I am a DevOps meat popsicle. Opinions are my own and not my employers. Also @docwho76@infosec.exchange on Mastodon

Seattle WA, US
Joined February 2008
Docwho is in Seattle. retweeted
Why is this so funny to me
188
1,090
170
7,967
498,382
Docwho is in Seattle. retweeted
❤️😂Liquid Death for this. Probably the funniest video you’ll see all weekend. Jason Kelce!!!!
13
80
7
269
12,883
Docwho is in Seattle. retweeted
BREAKING: White House lawyers are warning that if a blue wave occurs in the midterms, the stress of being investigated, impeached, and turned into a lame duck on the global stage could give Donald Trump a heart attack or stroke.
118
4,035
15
45,862
2,097,952
Docwho is in Seattle. retweeted
tl;dr United States government rules it may be legal to possess CSAM (Child Pornography) if it's AI generated Dawg, last week the United States Seventh Circuit Court of Appeals made a decision which will unironically change the way CSAM (Child Pornography) is handled in the United States. Under United States v. Anderegg, Anderegg was charged with distribution and possession of Child Pornography. Anderegg used Stable Diffusion AI to generate hyper-realistic depictions of children having sex. While charged with CSAM, Anderegg appealed the decision and argued it was not possession of CSAM because the "children" in the images were not "real" children. Rather, Anderegg and his attorneys argued that it is not illegal to possess obscene material which does not harm anyone. The courts official ruling: By 1969 ruling of Stanley v. Georgia, you are protected by the United States First Amendment to privately possess obscene material in one's home. Hence, because the images are completely computer generated, and no actual child was used to create the pornography, the United States government cannot constitutionally criminalize someone's private possession of those obscene images in their home under this statute
193
235
99
2,601
182,817
Docwho is in Seattle. retweeted
If only there was a way to avoid this o.O
59
295
35
4,344
182,896
Docwho is in Seattle. retweeted
PICARD: Data, shields up DATA: Brilliant! Shields can reduce damage we sustain. Not immunity. Not hubris. Just prudence. It's not precaution—it's strategy. [camera shakes] WORF: HULL BREACHES ON NINE DECKS DATA: Here's what happened: you told me to raise shields, and I didn't
295
4,745
178
49,557
1,406,665
Docwho is in Seattle. retweeted
Pov: Chicken firewall for network security
28
59
3
745
28,983
Docwho is in Seattle. retweeted
This is what my brain hears when someone is trying to explain math, card games, board games, rules of any kind, or cryptocurrency.
110
104
19
729
39,735
Docwho is in Seattle. retweeted
Golden Retriever wearing a hat went viral devouring a full hot dog at the ballpark. Dude was in heaven
755
10,386
705
158,783
11,227,244
Docwho is in Seattle. retweeted
Wow...this is great 🤣🤣
66
520
59
1,586
54,138
Docwho is in Seattle. retweeted
AI is amazing. I am extremely pro-AI 1. It has lowered the barrier of entry for programmers, resulting in hundreds upon hundreds of slop applications vulnerable to everything. This is job security. 2. AI influencers keep saying AI is going to destroy cybersecurity. This is good. AI influencers don't understand the size and scope of cybersecurity, they think it's just smashing a keyboard and making cat noises. This makes people less likely to enter our field, making us more valuable, making us more money. It's job security. Keep telling people cybersecurity is dead. 3. It's given us a new area of research: AI security 4. It's made task automation easier with slop Python scripts. In summary, cybersecurity is dead. DO NOT try to work in this field. It's all over. Cybersecurity has been solved!
107
340
28
4,677
152,846
Docwho is in Seattle. retweeted
"According to reporting by Bloomberg, about half of the data centers slated to open in the US in 2026 will either face delays or outright cancellations."
40
213
25
2,563
78,140
Docwho is in Seattle. retweeted
IS 👏 IT 👏 WAR 👏
272
9,952
378
48,548
1,181,732
Docwho is in Seattle. retweeted
👀 🤔
963
16,772
637
110,531
4,892,184
Docwho is in Seattle. retweeted
Repost and get a suprise
21
116
5
576
30,924
Docwho is in Seattle. retweeted
Now I'm pregnant.
38
135
11
2,291
241,791
Docwho is in Seattle. retweeted
i love dns it always works great for me 👄✨ video was created by the luminary genius @citiesbydiana
107
1,236
66
11,311
498,906
Docwho is in Seattle. retweeted
I recut the Melania trailer shot for shot with AI to replace her with Miss Piggy. I don't know if this was a good idea, but I did it.
1,151
3,930
486
23,965
834,157
Docwho is in Seattle. retweeted
I work at Slack. We tell employees their DMs are private. And they are. Mostly. Look, when we say "private" we mean private between you and the person you're messaging. And your admin. And HR. And legal. And whatever compliance tool your company bought. And the export logs. And the backup systems. And anyone with a court order. But other than that, totally private. We're very clear about this in our documentation. Page 47. Section 12. Subsection C. Paragraph 8. The part nobody reads before they trash-talk their manager at 11pm. Here's what employees don't understand. When you delete a message, you're just deleting it from your view. The message still exists. In exports. In backups. In the retention policy. It's like closing your eyes and thinking you're invisible. The data belongs to the company, not you. We say this right in our terms. Workspace owners control everything. They decide how long messages are stored. Sometimes it's 30 days. Sometimes it's forever. Hope you didn't say anything spicy in 2019. Enterprise customers get extra features. Full message exports. Metadata tracking. Who messaged whom. When. How often. Communication patterns. It's for "compliance." It's for "legal needs." It's for "regulatory requirements." It's definitely not for micromanagement. We're very careful to explain that admins can't see messages in real-time. They have to formally request an export. Fill out some forms. Click some buttons. Maybe wait an hour. Very high barrier. Almost impossible to abuse. The key takeaway is simple. Treat Slack like work email. Not like WhatsApp. Not like Signal. Just because it looks like a chat app doesn't mean it works like one. If a message could cause trouble when HR reads it, don't send it. This is empowering employees with knowledge. If you wouldn't say it in the break room with your manager behind you, don't type it in Slack. That's privacy. Informed privacy. Enterprise-grade informed privacy.
114
494
92
3,822
617,351