@init4tti
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- United States Android App
Account-level information from X, not a live location or the device used for a specific post.
Joined November 2021
- Tweets10.5K
- Following114
- Followers202
- Likes22.4K
init4_tech retweeted
Say what you will about Windows (OS), but the NT kernel really is an engineering marvel that still puts Linux to shame in many ways.
The quickest way to describe it for a programmer, is NT was more like an object-oriented language, with a strong security model from day one, whereas Linux is very…not.
A lot of the “good” features in Linux feel bolted-on (SELinux, Capabilities, Namespaces) because…well they were. I love to imagine an alternate history where NT won.
IMO, Microsoft *should* have made an “Open NT” in the early 2000s; not fully GPL-style open, but one where a large org could say…swap out a memory allocator for their own. (they sorta did this with limited source access, but it was too restrictive)
You could imagine say…an early Amazon forking OpenNT to create an “AmazonNT” for EC2, where they have a modified scheduler, network stack, whatever. But, the security+compatibility contract keeps a stable baseline on the Microsoft side.
Controversial take, but if we enter this era where users are giving AI agents increasingly higher levels of access control; the Linux kernel is legitimately a poor fit. Think about it; answer the question “What exactly is this AI agent allowed to do?”
On Standard Linux, it’s disgustingly messy with lots of overlap.
Do you use UIDs? GIDs? ACLs? CGROUPs? Policies? SELinux? Filesystem modes? There’s not a singular coherent graph of capabilities you can point to. Too many ways you can escape an initially narrow scope.
NT, by comparison, can go the route of explicitly typed resources, and then you could have these really strong centralized audit trails when an agent goes haywire…etc.
I know I’m rambling, but the point is…if you were greenfielding an OS kernel from scratch, in 2026, with the intent of being forward-looking, it would *not* look like Linux. Frankly, it’d probably look a lot closer to NT, or even a BSD fork…
init4_tech retweeted
NOBODY tells Americans this part of the story.
March 11, 2011.
A black, 30-foot wall of ocean swallowed Northeast Japan.
Our government froze. The Pentagon had no orders.
Communications were dead.
You know what Captain Thom Burke and Rear Admiral Robert Girrier did on the USS Ronald Reagan?
They didn't wait for the White House.
They didn't wait for paperwork.
They looked at the TV screen, saw their friend drowning, and committed the ultimate military sin:
UNAUTHORIZED ADVANCE.
“We’re going. NOW.”
They turned the massive nuclear carrier full throttle straight into the disaster zone.
Then came the hydrogen explosions at Fukushima.
Radiation plumes drifted across the Pacific.
Every foreign embassy told their citizens: RUN.
The US Embassy ordered an evacuation zone: STAY 50 MILES AWAY.
Did the Ronald Reagan turn around?
DID YOUR SAILORS RUN?
NOT. ONE. INCH.
Nineteen-year-old kids from Texas and Ohio stood on a freezing flight deck, radiation detectors in hand, launching helicopters into blizzards.
They hovered over submerged rooftops, pulling shivering mothers and babies out of the black water.
When Japanese refugees were brought aboard shivering in shock, your sailors gave up their own warm bunks and slept on the cold steel floor.
While the rest of the world ran away from Japan,
AMERICA CHARGED STRAIGHT INTO THE FIRE.
You didn't do it for a treaty.
You didn't do it for politicians.
You saw your friend bleeding, and you kicked the doors down to save us.
Happy 250th, America.
Japan will remember your boys forever. 🇺🇸🤝🇯🇵
🤖 Made with AI
init4_tech retweeted
Some bangers from the SEC today:
1) buybacks do not make a commodity token into a security
2) liquid staking tokens for commodities are not securities
sec.gov/about/divisions-offi…
At 18:31 UTC on September 24, 2026, Bitget’s security systems identified unauthorized transfers involving a limited number of hot wallets.
Our security team immediately activated emergency response procedures and began a full investigation.
Based on our current assessment, approximately $351.6 million in assets were affected. Bitget’s cold wallets and the overwhelming majority of platform assets remain secure and unaffected.
Most importantly, user funds remain protected.
The incident falls within the coverage of Bitget’s User Protection Fund, which currently holds more than $464 million.
Customer account balances remain accurate, and deposits and trading continue to operate normally.
As a precaution, withdrawals have been temporarily suspended while our teams complete a comprehensive security review.
We have identified and flagged the relevant transfer addresses and have formally engaged law enforcement agencies and leading on-chain security partners.
We are working around the clock to restore withdrawal services as soon as it is safe to do so.
Bitget will provide further updates through our official channels.
We will not speculate on the attack vector while the investigation remains ongoing. Our focus is on protecting users, securing all systems, and delivering complete transparency throughout this process.
[SECURITY NOTICE] Bitget Hot Wallet Incident — September 24, 2026
At 18:31 UTC on September 24, 2026, Bitget's security systems detected unauthorized transfers from some of our hot wallets. Our security team activated emergency response protocols immediately.
What we have confirmed:
-Estimated funds affected: approximately $351.6 million
-Cold wallets remain fully secure. Bitget operates a three-tier wallet architecture — the breach contained only a portion of the hot wallet and warm wallet layers.
-User funds are safe. The full amount of this loss falls within the coverage of Bitget's User Protection Fund, which currently holds over $464 million
Actions we have taken:
-Emergency response team activated within minutes of detection
-Abnormal transfer addresses identified, flagged, and reported
-Withdrawals temporarily suspended as a precautionary measure, pending security review
-Law enforcement and on-chain security firms have been formally notified and are engaged
What this means for you:
-Your account balances are accurate and your assets are protected
-Deposits and trading remain fully operational
Withdrawals are temporarily paused and will be restored as soon as the security review is complete
-What comes next: We will provide updates on an hourly basis across this channel and all official platforms. A full incident report — including root cause analysis and corrective actions — will be published within 24 hours. We will not speculate on the attack vector until the investigation is complete.
Bitget has navigated multiple market cycles. We will not run from this. Every dollar and every decision will be accounted for, transparently and in full.
Updates will be posted here and across all official Bitget channels as they become available.
— Gracy Chen, CEO, Bitget
$ORCL bonds crossing 8.3% for the first time after Larry Ellison used the Enron trick (first time anyone did since Enron) of “Customer Pre-Payments with a Significant Interest Component” to hide Operating Cash Flow Problems.
Notably Oracle also was the first Publicly Listed US company outside of drillers and Miners (or Covid) to use Force Majeur to avoid paying on a data center lease it couldn’t afford, since… you guessed it… Enron.
init4_tech retweeted
⚠️ Microsoft Confirms Windows 11 Update Bug Causing Black Screens and Loading Issues
Details: cybersecuritynews.com/window…
Microsoft has confirmed a Windows 11 issue that can leave users staring at a black screen after signing in, with the desktop shell failing to start automatically.
The problem emerged after installation of the August 27, 2026 non-security preview updates and later cumulative updates.
Microsoft lists the incident as “mitigated,” while engineers continue developing a permanent correction for a future Windows update.
The failure has been observed primarily on Azure Virtual Desktop hosts using FSLogix, particularly when sessions load certain existing user profiles. Affected users may authenticate but never reach a usable desktop.
#windows11
init4_tech retweeted
Why does Congresswoman Nancy Mace look like she's about to give me a Soviet mission in Red Alert 2?
init4_tech retweeted
Rebs Gaming has come out with an insider report on the state of Halo Studios before they were closed down this week:
- Xbox has laid off almost the entire Halo Studios team with only 30 employees remaining, these include engineers, artists, designers and support personnel.
- There were NO Halo games in full production at Halo Studios/343i, despite Halo Infinite being nearly 5 years old
- There were some Halo games in the very early concept stages with no major work done, these were: Halo 2 Remake, Halo 3 Remake, Halo 7 and a Halo spin-off game based on the "First Strike" novel
- First Strike takes place between Halo CE and Halo 2, and was intended to connect Halo CE and Halo 2 more effectively
- First Strike was planned as a smaller, quick release game in-between large releases, with only 5 campaign missions, a Firefight mode and was planned to be finished and released by next year
- Halo Studios was considering a strategy of adapting Halo novels into smaller games inbetween the major remakes
- Halo 7 was reportedly still many years away, only a small team was working on the concept and overall vision
- Right before the lay-offs, developers did reportedly present the concept of Halo 7 to Xbox execs, which included Campaign, PvP, PvE and Forge all at launch
- The remaining Halo Studios team wants to also exploring using AI tools to help create smaller Halo projects, while outsourcing development of Halo remakes and potentially still make Halo projects internally
- A source of Rebs claims that Activision has 0 intention to work with Pierre Hintze, the current leader of Halo Studios, Making it unlikely they'll ever work on a new Halo game again
- Reb's sources strongly criticize Pierre Hintze's leadership and Matt Booty's, with a general lack of accountability across Xbox Game Studios sited as a major issue
- They also speculate that Halo Studios will probably be eventually fully shut down
Honestly, my thoughts on all this is: I am not surprised. Halo Studios aka 343 Industries' leadership alongside the old Xbox team's incompetence in controlling their studios caused Halo's downfall. There is a ton of talent at Halo Studios that clearly wanted to make great Halo games, but the higher ups and then Xbox above them consistently did nothing for years and years. The fact that Halo 7 to this day, 5 years since Infinite, was just a concept, is insane to think about.
Asha Sharma 100% did the right thing ending this entire charade and giving the IP over to Activision. Despite all of Activision's issues, they run Call of Duty like a machine and there is ALWAYS new content and games for COD. Meanwhile, Halo is just collecting dust with a whole studio dedicated to it that's seemingly ended up producing nothing other than a subpar remake in 5 years. An entire generation does not know Halo or enjoy it because there is practically nothing coming from this franchise. For so many years, I constantly voiced my frustrations with Xbox and their handling of their studios. Could Halo Studios' closure have been avoided? Yeah, If Phil Spencer and other execs actually took charge and got this studio to make a Halo 7 in the past half a decade. But now, it's just too late.
RIP Halo Studios
init4_tech retweeted
Imagine us all listening to “Cleveland!” by Taylor Swift for the first time and it’s just this
init4_tech retweeted
The bond market is screaming at us to stop the deficit spending
For almost two decades, America enjoyed a moat that very few countries in the world can afford, which was cheap cost of capital
We should have taken these dollars and built out infrastructure like never before. Bridges, tunnels, roads, factories and everything in between
Instead, we funded social services for boomers who already had too much, pushed on ESG and wokeness to folks who had too little, and awarded massive foreign aid to organizations who never deserved it
Probably one of the worst allocations of capital in history on a national scale. History will not look back kindly at us