Technical Supporticus (@TechSupporticus) header
Technical Supporticus (@TechSupporticus) profile picture

Audio Engineer | IT Manager | Computer repair guru | Tesla/Rivian/Ford EV Owner | Car enthusiast | Terrible at jokes | Main Account - @IAmSuburban

Florida, USA
Joined May 2022
Photo by Technical Supporticus (@TechSupporticus)Photo by Technical Supporticus (@TechSupporticus)Photo by Technical Supporticus (@TechSupporticus)Photo by Technical Supporticus (@TechSupporticus)Photo by Technical Supporticus (@TechSupporticus)Photo by Technical Supporticus (@TechSupporticus)Photo by Technical Supporticus (@TechSupporticus)Photo by Technical Supporticus (@TechSupporticus)Photo by Technical Supporticus (@TechSupporticus)Photo by Technical Supporticus (@TechSupporticus)
You’re supposed to use your MacBook at Starbucks not Five Guys
How can I stop my MacBook keyboard from ending up like this?
36
457
8
27,642
586,648
Technical Supporticus retweeted
“vehicle detected” oh my absolute god
51
2,018
37
59,024
903,002
A common misconception is that internet speed and file size are equal measurements — speed’s measured in bits while size is measured in bytes. One byte is actually 8 bits, meaning one gigabit is ~1/8 of a gigabyte.. so it’ll take like 8 seconds to download it with those speeds
ok dumb question... if my internet speed is 1 Gbps, why can't I download a 1GB file in one second?
1
6
485
While I’m not a fan of this thermally, the vapor chamber(s) in my Duo are doing a decent job of keeping the phone cool. I still encounter some throttling but nowhere near that of my iPhone Air. Maybe titanium + full vapor chamber could be the way to go?
The iPhone 20 Pro could return to titanium, according to leaker Fixed Focus Digital. • Titanium frame on early prototypes • Much more rounded design • Somewhat similar to the iPhone Air The iPhone 15 Pro and 16 Pro used titanium before the 17 Pro switched to aluminum.
1
118
This could even be a cool tool to bring along for spatial computing in an AVP or Quest 3 etc
Pre-orders are open now for Framework Wireless Touchpad Keyboard. Finally, a living room keyboard you want to use.
3
118
Technical Supporticus retweeted
Pretty wild Apple added face unlock to the iPhone Duo before, you know, picture-in-picture FaceTime on the inner screen.
51
37
2
2,331
135,389
Keeping mine for the long haul!
Who else kept their iPhone Duo 👀
15
447
An “internal update”
Apple: “Many of our systems are back up and running after an internal update caused some outages this morning. We’re working to get the remaining systems online as soon as possible." Company says this wasn’t a cyberattack.
3
131
Technical Supporticus retweeted
It’s like Covid but for computers
88
4,288
158
34,526
472,628
iCloud starting to have outages
3
112
Hang on. This potentially could mean facial recognition on the ProLED MacBook Pro may come soon
Face Unlock is now on the iPhone Duo! With iOS 27.3 Beta 2
14
651
Technical Supporticus retweeted
INB4 iPhone 19 Pro has an UDC with "FaceID" and it's just a camera that uses image processing to verify identity. You know. Like what Google has been shipping since 2023 in the Pixel 8.
2
2
86
20,664
So essentially, 1) improper testing of all ranges of traffic and hardware configs caused the bug to go undetected for months 2) failover system brought Teams onto the Exchange gateway, increasing load and likelihood to encounter the bug 3) endpoint maintenance reduced the overall capacity to ~86% which was too much load for the bug and rapidly degrades endpoint availability 4) due to all that, the load of everything waiting kept bringing it down each time they tried to bring it back All could’ve been avoided by proper testing and deployment but that’s asking too much of Microsoft apparently
More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below. We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations. The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services. First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments. The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact. Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores. Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts. Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own. Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States. When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive. Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally. Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway. Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change. After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region). The final Post-Incident Review (PIR) will provide more details later this week.
1
9
433
Technical Supporticus retweeted
Tryna sleep but my Apple Watch keeps trying to take my blood oxygen levels
10
21
174
2,349
Spotted another Duo user in the wild
11
375
The even funnier thing is I played this out loud and it my HomePod mini heard it and set a timer for 10 minutes with no issue 💀
Here is the best review for HomeView for y’all. This thing is a joke. Siri is a joke. @johnternus how is this a great product?
3
34
3,823
Technical Supporticus retweeted
unfolding my iPhone Duo to assert dominance
8
4
1
105
3,159
Technical Supporticus retweeted
unfolding the iPhone Duo should automatically switch the calculator to scientific because What is this.
44
55
5
5,665
50,841
Technical Supporticus retweeted
Oops - Apple just referred to HomeView software as “NewsRoom software”
9
17
4
425
37,603