$ⵜǝⴼ@ن

Estados Unidos inicia una guerra. Iran cierra el Ormuz a todos. Estados Unidos pide ayuda a todos los países. Ningún país ayuda. Iran abre Ormuz a 215 países que han dicho que no iban a ayudar. Como los únicos perjudicados son los barcos estadounidenses, israelíes y de los aliados árabes, Trump decide joder de nuevo a los otros 215 paises y ahora el que pone el cierre es él. Es el mayor hijo de puta de la historia y nos quiere ver a todos jodidos.

'LAST WARNING… I am ready to OPEN FIRE' MOMENT US Navy warship ordered to TURN AWAY from Strait of Hormuz by Iran — IRIB

"Gerekirse ot yeriz ama nükleer bombamızı yaparız." Tarih 15 Aralık 1971 Pakistan Cumhurbaşkanı Zülfikar Ali Butto'nun Birleşmiş Milletler'de Pakistan'ın nükleer silahlara sahip olmamasını emrettiğinde BM belgesini yırttığı anlar... "Ben bir sıçan değilim. Hayatım boyu hiç kaçmadım. Güvenlik Konseyinizi alabilirsiniz!" diyerek karar taslağını yırtmış ve salonu terk etmiştir. Zülfikâr Ali Butto, bu olaydan kısa bir süre sonra 1972'de Pakistan'ın nükleer programını resmen başlatmıştır. Ünlü "Gerekirse ot yeriz ama nükleer bombamızı yaparız" sözünü de bu dönemde, Hindistan'ın nükleer kapasitesine karşı ülkesinin güvenliğini sağlamak için söylemiştir.

@JamesCGraves1 @Amockx2022 Copium

@Amockx2022 "US got scared and immediately stopped their movements towards SoH" Not true. Two destroyers passed through the Straits sweeping for mines Iran lost track off. Iran did not shoot.

THIS IS ABSOLUTE CINEMA 🍿🔥 > 🇺🇸 US smartly tried to send warships to the Strait of Hormuz > 🇮🇷 Iran told negotiators to tell US that they will destroy warships in just 30 mints 😂 > 🇺🇸 US got scared and immediately stopped their movements towards SoH > 🇮🇷 Iran still didn't get impress with the US because they tried to ditch negotiations Now Iran has blocked all the tankers at the Strait of Hormuz carrying oil of US allies 😭 They have published this video 🔥 🇺🇸 Trump : 00 || 🇮🇷 Araghchi : 02

@ze_rusty Makes sense

@Steph_iD Read it again. Trifield TF2 can't measure it because it cannot detect those band of RF frequencies

> guy buys TriField TF2 to check his EMF exposure > tests his router: 2.4 GHz.. meter peaks > tests his phone: 700-2600 MHz.. meter peaks > installs Starlink on his roof > points meter at the dish > reads ZERO > "huh, totally safe I guess" > Starlink broadcasts at 10.7–14.5 GHz > TriField tops out at 6 GHz > Safe and Sound Pro II tops out at 8 GHz > no consumer meter covers 8–20 GHz range > ZERO > the measurement gap isn't filled by any product at any price under $5,000 > FCC certified it safe in 1996 > using standards that only measure heat > MrBeast says it's amazing > Elon says this will advance humanity in unimaginable ways > yeah > unimaginable

Once you deconstruct religion there's no going back When people say they deconstructed and went back I KNOW they are lying There’s no going back mate

If you want to see how logical a Muslim can be, deconstruct Christianity If you want to see how logical a Christian can be, deconstruct Islam But tell both parties to apply same logic to their own religion... Impossible

The truth is: God doesn't exist. The #ArtemisII flyby the moon which directly again for the 1 millionth time disproves the Tower of Babel and splitting the moon fairytales (Bible and Quran) is another proof that those books are simply filled will lies. Again, man created God when man was ignorant of a lot of things. Man knows better now and can explore our world, solar system, galaxy more. Science does need faith or belief. Science is REAL. Science gives you verifiable proofs.🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥

@TCGView @vxunderground I'm not talking about now, clown.

@Steph_iD @vxunderground Both sides confirmed it is getting or is already fixed. You're like 2 days late.

Microsoft locked out OSR?! Holy FUCKING shit. I thought VeraCrypt and WireGuard was bad. Dawg, someone at Microsoft is fucking up BAD. This is ridiculous. The initial excuse was people didn't verify their email, so it was plausible like, "oh two people probably made a small mistake, bureaucracy, dumb stuff, weird coincidence". But then Windscribe... AND OSR?! What the fuck is going on at Microsoft? There is a galactic level of fuck up happening somewhere

I am the VP of Developer Ecosystem Compliance at Microsoft. I have held this title for eleven months. Before that I was Senior Director of Platform Integrity. Before that I was Director of Partner Verification. Before that I was a program manager who sent emails. Each promotion added a word. Each word added a layer between me and the people my systems affect. I am now five layers away. That is called career growth. I did not block VeraCrypt. I completed the verification process. The distinction between those two sentences is my entire career. On October 16, 2025, my department launched the Windows Hardware Program Account Verification Mandate. The mandate required all developers with active signing certificates to reverify their accounts through a standardized identity confirmation workflow. The workflow included document submission, organizational validation, and a response to an automated email sent to the address on file. The email was sent once. It was sent to the address on file. If the address on file was correct, the developer received the email. If the address on file was not correct, that was the developer's responsibility. We do not manage developer email addresses. We manage the ecosystem. Developers had thirty days. Then we extended the deadline to March 30. That is five months and fourteen days. Five months and fourteen days is generous. I said that in the launch presentation. I was standing in Building 25, Studio B, in front of a slide that said "Developer-First Compliance" in 62-point Segoe UI. There were forty-three people in the room. The slide had a timeline graphic. The timeline had two colors. Green for compliant accounts. Gray for accounts that had not yet responded. There was no red. I was asked about that. I said we do not use red. Red implies a problem. Gray implies an opportunity. An opportunity to verify. That's outreach. The automated emails went out on October 17. They were generated by the Ecosystem Notification Engine, which is a system I named. It sends communications. It does not read replies. It is a one-directional compliance instrument. Developers who received the notification could click a link, complete a seven-page verification form, upload two forms of identification, confirm their organizational affiliation, and attest to their continued participation in the Windows Hardware Program. The form took approximately forty-five minutes to complete. I know this because internal testing averaged thirty-eight minutes with employees who built the form and knew what every field meant. For developers unfamiliar with Microsoft's organizational taxonomy, it takes longer. We did not test with external developers. We tested with ourselves. That is called user validation. The deadline passed. 1,247 accounts did not complete verification. The system suspended them. Automatically. No human reviewed the suspensions. No human triggered them. The system triggered them because the deadline passed and the accounts had not verified. That is the process completing. That's compliance. Mounir Idrassi was one of the 1,247. I need to explain who Mounir Idrassi is, because I did not know who Mounir Idrassi was until 557 people on Hacker News were upset with me, which is how I learn things. Mounir Idrassi is a French security researcher. He is the sole maintainer of VeraCrypt. VeraCrypt is the most widely used open-source disk encryption tool in the world. It is the successor to TrueCrypt, which was the most widely used disk encryption tool before VeraCrypt. Mounir has maintained it for over a decade. He signs the Windows drivers and bootloaders that allow VeraCrypt to operate on Windows. Without a valid signing certificate, he cannot release new Windows builds. Without new Windows builds, VeraCrypt on Windows cannot be updated. Without updates, vulnerabilities cannot be patched. I learned all of this in the same week. I learned it backward, which is how I learn most things. First the Hacker News post. Then the SourceForge thread. Then the internal escalation. Then the Wikipedia article. Then the realization that I had suspended the signing certificate of the person who provides disk encryption to journalists, human rights organizations, and security researchers worldwide. That's ecosystem management. I want to tell you about the emails. Mounir posted on the VeraCrypt SourceForge forum that he had contacted Microsoft support. He received an automated reply. The automated reply contained a case number. The case number linked to a knowledge base article. The knowledge base article explained the verification process. The article did not explain how to resolve a suspended account. It explained the process. The process was the answer. If the process had not suspended the account, the article would not be necessary. The article existing is evidence that the process works. He emailed again. He received a second automated reply with the same case number and a satisfaction survey. The survey asked him to rate his support experience on a scale of one to five. He did not complete the survey. I do not know what he would have rated it. The survey results feed into our Support Health Index. Unanswered surveys are excluded from the calculation. His experience does not affect our score. That is called data hygiene. He emailed a third time. This time a human responded. The human asked him to complete the verification process. He explained that the verification form required organizational affiliation and he is an independent developer. The human directed him to the FAQ. The FAQ did not address independent developers. It addressed organizations. Mounir is not an organization. He is one person who provides encryption to millions of people. The system does not distinguish between one person providing encryption to millions and a company providing screensavers to twelve. Both are developer accounts. Both must verify. That's equality. I should tell you about the others. VeraCrypt was not alone. WireGuard VPN. MemTest86. Windscribe VPN. Several others I am not authorized to name because their suspensions are still being processed, and naming them would acknowledge that a problem exists, and acknowledging that a problem exists would suggest the process is not working, and the process is working. I know because my dashboard says so. The dashboard is called Compliance Horizon. It occupies the left monitor on my desk. I open it before I open email. It shows four metrics: Total Active Accounts, Verified Accounts, Verification Rate, and Ecosystem Health Score. The Ecosystem Health Score is calculated as Verified Accounts divided by Total Active Accounts. Suspended accounts are removed from Total Active Accounts. They are not counted as unverified. They are not counted at all. The denominator shrinks. The percentage rises. When I suspended 1,247 accounts, the Ecosystem Health Score went up. The dashboard does not track what the suspended accounts do. It tracks that they were suspended. The suspension is the health. I start each morning with the Ecosystem Health Score the way other people start with coffee. Mine was 97.3% on April 1. It was 94.1% before the suspensions processed. I gained three points by removing the people who did not complete the process from the count of people who exist. My manager mentioned the improvement in a skip-level. He said "good trajectory." I said thank you. I did not explain the math. The math is the trajectory. That's ecosystem health. The Hacker News post reached 557 points on a Wednesday. I know it was a Wednesday because my Slack went from four messages to sixty-one messages in the time it took me to walk from the Redmond campus coffee bar to Building 25. Sixty-one messages. Fourteen were from my team. Seven were from developer relations. Twelve were from communications. Twenty-eight were from people I had never spoken to who all had opinions about what I should say and how quickly I should say it. I said nothing. That is the protocol. When a compliance action generates public attention, the protocol is to route all communications through the Developer Relations Response Framework, which is a document I co-authored that specifies a 24-hour cooling period before any public statement. The cooling period is not for us. It is for the community. They need time to process their feelings. We need time to craft the sentence. The sentence was crafted by Thursday. Scott Hanselman was briefed. Scott is a VP in Developer Community. Scott is good at sentences. Scott posted publicly that it was a "routine verification process." I want to tell you about that phrase. "Routine verification process." Four syllables, then five syllables, then three syllables. Twelve syllables that contain no information about who was affected, why they were affected, what the consequences are, or whether the consequences will be reversed. "Routine" means it has happened before. "Verification" means we asked a question. "Process" means nobody is responsible. Scott was right. It was routine. The process was routine. The process is always routine. I built the routine. That's communication. I want to tell you about Rachel. Rachel is not her real name. Rachel is a program manager on the Developer Ecosystem Partnerships team, which is adjacent to my team but reports to a different VP. Rachel sent me a message on the Thursday after the Hacker News post. The message said that VeraCrypt is listed in the digital security toolkits recommended by the Committee to Protect Journalists, the Electronic Frontier Foundation, and Reporters Without Borders. The message said that VeraCrypt is used by journalists operating in countries where encryption is the difference between a published story and a prison sentence. The message said that suspending the signing certificate of the sole maintainer of this tool could have implications beyond ecosystem compliance. Rachel used the word "implications." I appreciated the softness. I replied that the verification mandate applies uniformly to all developer accounts and that exceptions would undermine the integrity of the compliance framework. I used the word "uniformly." I used the word "integrity." I used the word "framework." Rachel did not reply. I saw her in the hallway the following Monday. She nodded. I nodded. She transferred to the Azure team six weeks later. That is not related. That's stakeholder alignment. I want to tell you who uses VeraCrypt because the process does not ask. Journalists in 41 countries use VeraCrypt to protect their sources. CPJ recommends it in their safety kit. EFF lists it in their Surveillance Self-Defense guide. Reporters Without Borders includes it in their digital security training. Human rights investigators use it to store testimony from witnesses who could be killed if their names became public. Enterprise security teams at Fortune 500 companies use it for disk encryption on sensitive workstations. Government agencies use it for classified-adjacent storage. Whistleblowers use it. Dissidents use it. People who live in countries where the wrong file on the wrong laptop means the wrong kind of visit at three in the morning use it. The process does not have a column for sources. The process does not have a field for "lives at risk." The form has a field for organizational affiliation. Mounir left it blank. He is not an organization. He is one person. The process does not care about one person. That's equality. I said that already. It is still true. I should tell you about the award. Last Thursday I received the Q1 Ecosystem Health Excellence Award at the quarterly all-hands for the Developer Platform division. The ceremony was in Building 33, the large auditorium with the curved screen. The slide behind me showed the Compliance Horizon dashboard. 97.3%. The number was green. There was a graph. The graph went up and to the right. The graph always goes up and to the right when you remove the people who failed from the people who count. My manager presented the award. The plaque says "Ecosystem Integrity Through Process Excellence." It is brushed aluminum. It is on my shelf between a ten-year service award and a framed team photo from the 2024 Platform Integrity offsite in Leavenworth, Washington. I received applause. Forty-two seconds. I counted because the moment felt significant and because I count things. Forty-two seconds of applause for the man who suspended the signing certificate of the world's most widely used open-source encryption tool and then measured his own success using a metric that excluded the suspension from the calculation. The process works. I know because I built the metrics that measure whether the process works. That's verification. I want to tell you about the board presentation. Last month I presented to the Platform Leadership Team on ecosystem compliance posture. The deck was fourteen slides. Slide three showed the verification mandate timeline. Slide seven showed the Ecosystem Health Score trajectory. Slide eleven showed "accounts requiring action," which is the phrase we use for suspended accounts when speaking to leadership. "Requiring action" sounds like the accounts need to do something. Not like we did something to them. The accounts need to act. We already acted. Our action was the suspension. Their action is to complete a form we built, in a system we control, on a timeline we set, using criteria we defined. Nobody on the Platform Leadership Team asked what the suspended accounts do. Nobody asked what software they maintain. Nobody asked how many people depend on that software. They asked whether the Ecosystem Health Score was trending favorably. It was. I showed them the graph. The graph went up and to the right. That's leadership engagement. Mounir Idrassi has mass-produced privacy for fifteen years. He maintains the encryption infrastructure used by journalists and dissidents on every continent. He does this as a single developer. He is not a company. He does not have a compliance department. He does not have a program manager. He does not have a VP of Developer Ecosystem Compliance who can navigate a seven-page identity verification form in thirty-eight minutes because he built it. I mass-produced compliance for eleven months. Compliance won. I should tell you one more thing. I use VeraCrypt on my personal laptop. I have used it for three years. I encrypt a partition that contains personal financial documents, family photographs, and a folder of contracts from before I joined Microsoft that I would prefer to remain private. The personal laptop is not part of the ecosystem. The personal laptop runs Windows. The version of VeraCrypt on the personal laptop is version 1.26.17, which was the last version Mounir was able to sign before I suspended his signing certificate. There will not be a 1.26.18 for Windows until the process completes. The process is the process. I cannot expedite it. I built it so that nobody can expedite it. That was the point. The point was uniformity. The point was integrity. The point was that no single account, regardless of what it does, who it serves, or how many lives depend on it, receives treatment different from any other account. The point is compliance. VeraCrypt works on Linux. It works on macOS. It works everywhere that does not require my signature on the certificate that lets it work. Journalists in 41 countries use VeraCrypt to protect their sources. The process does not have a column for sources. The process completed. Verification achieved. Ecosystem protected. I am the process. I am the compliance. I am the metric and the dashboard and the graph that goes up and to the right. I received the award. The plaque is brushed aluminum. Forty-two seconds of applause. That's the ecosystem.

@AnosVoldigoad91 @windscribecom @vxunderground @shanselman Thanks VeraCrypt for starting this whole thing.

@windscribecom @vxunderground @shanselman You only got it back because it was a PR disaster. If this issue didn't get such a widespread attention, Microsoft wouldn't have cared.

@TCGView @vxunderground You are a clown, they never received anything.

@vxunderground They got it fixed. Apparently, Microsoft started sending out emails to people back in October and, allegedly, a lot of them simply never checked the email they gave Microsoft and never saw that they were going to need to verify some stuff to keep going with the program.

@shanselman Address the elephant in the room: why do you force your accounts to ID via Au10tix, the mossad linked company?

Hey I love dumping on my company as much as the next guy, because Microsoft does some dumb stuff, but sometimes it's just check emails and verify your accounts. Not every "WTF micro$oft" moment is a slam dunk. I've emailed VeraCrypt personally and we'll get him unblocked. I've already talked to Jason at WireGuard. Not everything is a conspiracy, sometimes it's literally paperwork.

@FatalHydra @IntCyberDigest What are thr chances that 3 separate accountd all missed those emails? Stop with the clownish takes, clown.

@IntCyberDigest To be fair, they were notified SINCE OCTOBER and took no action. Sounds like their fault... 6 months past deadline... Yea, we can argue Microsoft needs proper support channels with actual humans but this all stemmed from these partners ignoring communication for 6 months.

❗️ Microsoft VP wants us to stop hating on them for suspending the WireGuard and other developer accounts: "iT's LiTeRaLLy PaPeRwOrK." Bro. Also Microsoft: "There are no appeals available, we have closed your application."

@edandersen Not true, the accounts M$ blocked were signing drivers just fine 18 month ago. It is only a couple of months ago that they got banned without a notice. One account can ignore the email, but three or more? Nah. Stop with the lies already.

@Steph_iD They’ve needed verified ID for about 18 months not “just now”

If kernel level drivers cannot be code signed because the developer has not verified their ID with Microsoft that is the system WORKING. Microsoft Partner Center is a serious thing btw, if you use it you should take it seriously, because its serious

@shanselman Stop lying Scott, these accounts never received any email from you guys and you know it. Also, address the elephant in the room, why are relying on AU10TIX, the Israeli company for ID verification?

Should be fixed in a bit. We've been sending everyone emails since October 2025 techcommunity.microsoft.com/blog/hardware-…

@Avamander @shanselman M$ did not send emails, this Scott guy is lying.

@shanselman Customers truly never read the emails they're sent, seems to be universal.

@shanselman @RyanLNewington It's not only you, they didn't send emails and are now trying to make it looks like they did but you missed. Typical clown behavior.

@RyanLNewington Will report this

@pierskarsenbarg @_muddymind_ @edandersen Except they did not receive any, clown, and we're not talking about one account, we're talking three and maybe more.

@_muddymind_ @edandersen Or maybe they should respond to the emails from Microsoft asking them to validate their ID?