Pinned Tweet
This video is not from Bihar. But this is the reality of marathis.
1 din mar jayega marathi(kutte) ki maut, jag mein kahenge log
😊
This Post is from an account that no longer exists. Learn more
Green Mamba retweeted
Replying to @GreenMamba999
Lol, How is this even insulting? Indian men especially NW men are among the most handsome men in the world.
The dress should have been cleaner and skin tone fairer though.
Green Mamba retweeted
Outlook is back.
@Microsoft can process 6,000 H-1B applications, but processing your inbox is apparently a tougher assignment.
Green Mamba retweeted
The core issue is people with 76 IQs with a culture of lies and scams trying to maintain 100+IQ systems built by a culture that values competence, skill, and integrity.
They aren't up to the task.
Lots of hot takes on the Microsoft 365 outage. Here's an engineering one.
To be clear: this is speculation. Microsoft hasn't confirmed a root cause. It's my read of their own updates, from 35 years of building and breaking systems.
What Microsoft has actually said:
• Traffic isn't up. Capacity is down. Servers are failing health checks and dropping out.
• A process that establishes secure connections gets overwhelmed, and servers stop processing requests.
• Servers they bring back fall over again as soon as traffic hits them.
• They're reverting a network config change that lines up with when it started. But changes aren't syncing, and some machines are stuck in a bad state.
• No indication of an attack.
My hypothesis: a metastable failure.
Whatever triggered it may be long gone. The outage is now keeping itself alive.
1. Reconnect storm. Every Outlook, Teams and mobile client on the planet is hammering for a fresh secure connection.
Full TLS handshakes are CPU-heavy, and a freshly rebooted server has a cold session cache.
A server comes up, eats a wall of handshakes, CPU pegs, it fails its health check and gets pulled, and its load lands on the next one. Dominoes.
2. The fix shares fate with the failure. If the rollback travels over the same secure channel that's melting, the cure can't reach the patient.
That's exactly what "changes aren't syncing" sounds like to me.
That's why they're throttling traffic types and rebuilding servers from an older config instead of flipping a switch.
You don't get out of this by finding the bug.
You get out by shedding load, restoring capacity in isolated cells, and letting traffic back in slowly.
Where AI fits (also speculation): not "an AI wrote the bad line". It's velocity. Microsoft flagged several recent config changes as suspects and took hours to find one that correlated.
When the volume of change outpaces the humans who understand each change, finding the culprit gets slow and rollbacks get messy. Automate the shipping faster than you automate the understanding, and this is the bill.
The takeaway for every business: your email, chat, files, identity and security tooling now share one failure domain. Today proved it. Have a way to talk to your team that doesn't live in the same tenant.
Happy to be proven wrong by the post-incident review. And I hope this post ages terribly.
Green Mamba retweeted
No explanation needed. Just a picture of the staff is all that’s necessary.
We are deeply sorry for the disruption this incident has caused our customers and partners. We know the trust they place in our services and take that responsibility extremely seriously. We are seeing broad recovery and stability across our services.
This was a technical issue not related to cyber or AI / agents. The incident was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change. We have addressed the underlying issue and continue to restore service to remaining customers and regions.
Given the scale of demand, we restored services gradually, validating stability at each stage. While this took longer, it helped ensure a stable restoration.
We will provide a full post-incident report once our review is complete.
Green Mamba retweeted
Folks, we all saw how bad things got with Microsoft the past few days. Total jeetification. Remember… these people are also “doctors”. Can you imagine how bad they will fuck up your care? DEPORT. EVERY. INDIAN.
Satya Nadella comes from Andhra Pradesh, India. And these indian CEOs overwhelm their companies with incompetent indian biomass.
🚨 EXCLUSIVE: Multiple Microsoft employees are blowing the whistle on alleged ANTI-WHITE discriminatory hiring practices.
Over the past couple of weeks I’ve interviewed dozens of current and former employees regarding hiring practices, visas, and national-security concerns.
👇Recurring claims from these employees:
• Multiple managers claim they were unable to, or strongly discouraged from, hiring white males and whites in general.
• Allegations of pressure to sign false “no American can do the job” documents to justify H-1B hires.
• Claims that executive bonuses have been tied to diversity numbers since 2016.
• White employees describe being singled out in “struggle sessions.”
• Microsoft has publicly pushed explicit goals to double the number of Black and Latino leaders.
This pattern has come up repeatedly in interviews tied to hiring, visas, and access to GCC data. I believe it’s worth sharing with the public.
Some screenshots of convos I’ve had with 3 different employeees are attached below. (I am choosing to keep the majority of the conversations private atm in order to protect employee privacy.)
My DMs are open and all sources are kept private. More coming. #microsoft
1
28
Green Mamba retweeted
This is a recreation of what might of happened at Microsoft server rooms. Saars are still trying to fix it as we speak
You’ve got to love how there’s a catastrophic IT infrastructure outage every few months now because corporations decided to hire H1B Indians instead of Americans.
Green Mamba retweeted
Satya's plan to boost India's GDP to $5t
and fire masses more Americans for Indian H1Bs
just hit a not-small bigger-than-a-pot hole.
The wheels came off.
But he can just laugh it off while he fingers his Greatest American Replacer medal from Fatass Boomer Traitor Trump.
And know that J.D. is in no position to follow through on any of his threats.
Or can he? @JDVance This is your moment to shine - if you can & will.
Satya Nadella, H1B CEO already has his American Citizenship.
Satya goes around openly giving speeches saying
that Microsoft's "mission" is to:
1. Raise India's GDP by trillions, not America's.
2. Invest in developing India's AI capabilities, not America's.
3. And that the way he is going to do this is to
Replace Millions of Americans with Indians training only Indians on AI, not Americans.
Which Microsoft has now put $30 billion into.
Guess how Satya feels about being American -
what American Citizenship means to him?
It means the right to run American Companies
to Replace Americans with Indians & use H1Bs
Onshore to move Microsoft investment Offshore -
as many people & as much $$ as he can.
Guess who he said his main partners were? The other companies who cheated so badly on their H1Bs that you had to suspend their citizenship applications (which should not have been added to the "temporary" H1B visa in the first place).
A little too late to stop him - unless you intend to investigate, denaturalize, and deport him for race-based hiring, firing, & promotion of 10s of 1,000s over his 10+ years as CEO.

































