Some more info on the hack and impact: https://krebsonsecurity.com/2026/03/iran-backed-hackers-claim-wiper-attack-on-medtech-firm-stryker/
Their employees had Intune running on their personal phones and computers which got wiped. Great reminder to never mix work and personal devices.
A bunch of people today had their phones wiped and eSIM deleted from their personal phones because they hooked it up to their corporate intune, which got hacked: https://krebsonsecurity.com/2026/03/iran-backed-hackers-claim-wiper-attack-on-medtech-firm-stryker/
In addition to letting the website owner know about the issue, I would reach out to Troy Hunt with your evidence, so the data can be loaded into Have I Been Pwned and the affected people notified.
That seems like a broad generalization, and for specialized software that requires newer hardware, you’d expect to find the rate of bitflips crashes much lower than 10%. You could argue that since Firefox is supported on older operating systems, longer than the support lifetime of the OS [1], it’s likely Firefox is being used specifically to get the last bit of life out of the hardware before it gets trashed.
It’s a sauna on a boat. She’s out in the middle of nowhere with some dude she barely knows. You know, she looks around and what does she see? Nothin’ but open ocean.
Wasn’t this the plot of South Park episode where Kyle’s dad was exposed to be a shitposter on an alt account. Life imitates art.
I think the lack of author attribution on this article is a hit of AI. Clicking on other articles, they do list the author and don’t have a fake interview tone Question and Answer tone to them.
What is up with the writing style of this article?? Seems like AI Slop, but it’s worse than usual. The Verge article has more details and isn’t written poorly. Check it out and not The Guardian.
This is the archive link for the Microsoft guide: https://archive.is/D9vEN
Regarding the USA point, from the article, there are many indications that the site was founded by someone from Russia:
But in October 2025, the FBI sent a subpoena to domain registrar Tucows seeking “subscriber information on [the] customer behind archive.today” in connection with “a federal criminal investigation being conducted by the FBI.” We wrote about the subpoena, and our story included a link to Patokallio’s 2023 blog post in a sentence that said, “There are several indications that the [Archive.today] founder is from Russia.”
This is the link to the 2023 blog post: https://gyrovague.com/2023/08/05/archive-today-on-the-trail-of-the-mysterious-guerrilla-archivist-of-the-internet/
This syntax should work in most Lemmy clients natively: [email protected]
The linked paper, “Replication of Quantum Factorisation Records with an 8-bit Home Computer, an Abacus, and a Dog” is also a great breakdown of how much the quantum factoring is more of a parlor trick and not practical for factoring RSA Keys, mainly since the prime factors are only a few bits off of each other and from the square root of the number being factored.
They’re probably not even building to industry standards and not properly grounding their equipment, so if you were to visit the “datacenter” you’d be literally shocked.
The raw comment is this:
[Digg.com](digg.com) didn't load for me, good start 😅
It’s missing the https:// protocol, so the link is assumed to be relative to the current page you’re on. It should have been formatted as
[Digg.com](https://digg.com/) and then it’ll look like: Digg.com
huh, really?? this post and the original is showing in [email protected] for me, and going there, I see two posts with the same link:
Original: https://lemmy.ml/post/41458701
Repost (this post): https://lemmy.ml/post/41482621
I don’t see this post in [email protected] at all, even when checking on lemmy.world directly. I don’t think this is a federation issue.
I’ve never seen any interview as invasive as this, but i think simple take home assignments are useful to weed out people who don’t have basic skills for the role, can’t read instructions clearly, and/or don’t care enough for the role. It avoids me spending 30 minutes to an hour interviewing them to just reject them.
The roles i interview for are mid level devops based, and we’ve found that the best way to do this is to provide the candidate a simple git repo with 2 branches, which can’t be merged due to a merge conflict of two text files; no coding required. Just asking the candidate to resolve the merge conflict and write a README with the steps taken is enough to have more than half of the candidates unable to complete the task. If we interviewed all those candidates first, and then had to reject them, it would probably be 1 full working day per month in aggregate that would be utterly wasted.
Am I missing something but this isn’t cross posted from another community, right? the original post was in this community, [email protected], so why repost if it’s less than 12 hours later in the same community?
Yeah, Honey is just exacerbating the inherent flaws in the system, and most of it can be dealt with having a limit of coupon usage and expiration of the coupons.
The thing which really upset me is advertisers pulling money from podcasts which have referral codes because of abuse from Honey. I’m not a fan of advertisements, but the referal codes were a simple solution since there’s no way to accurately measure if an ad was listened to. Honey causing advertisers to pull support for podcasts just pushes podcasts to closed ecosystems with more tracking and analytics, and takes money away from Podcasters.
Why would a 302 temporary redirects for
engramma.dev→app.engramma.devbe classified as “Social engineering content”?