Wild Horizon (@DGJFarrell) header
Wild Horizon (@DGJFarrell) profile picture
Joined June 2012
Specifically what is St. John’s getting?
From skating lessons, to rec league after work, we’re putting $750 million into ice rinks across the country in Budget 2026.
1
3
Expected. War times.
⚡️Zelensky warns of imminent Russian attacks, 'extremely dangerous' North Korean missile development. "Please, be sure to heed air-raid alerts this evening, tonight, and throughout the day tomorrow," Zelensky said. The president also warned that North Korea is now supplying Moscow with dozens of ballistic missiles each month. kyivindependent.com/zelensky…
1
As far as the porch.
If I broke into your house and stole what's under your bed, what would I get?
2
Looking great.
Drive along with me as we build the roads to space in Newfoundland and Labrador, @Nord_Space Atlantic Spaceport Complex (ASX). Canada's largest spaceport and future home of our Taiga, Tundra, and Tempest rockets.
1
18
Canadian first - merit based.
Canada is looking for skilled tradespeople, including carpenters, plumbers and machinists, to help build homes, strengthen our workforce and support critical infrastructure across the country. If you have the training, credentials and experience in the skilled trades we’re looking for, explore our immigration pathways and build your future in Canada: bit.ly/4uXwAoe
3
Can't train a retard.
She didn’t think twice before throwing other people’s bags but she wasn’t expecting what happened next …
15
I remember buying that for $80 in 1985.
Replying to @Wanderwthkarth
It's Dom Pérignon, the iconic vintage Champagne from Moët & Chandon. The distinctive shield label and bottle shape match the one on the table. A standard 750ml bottle of recent vintages (like 2013 or 2015) typically costs $200–300 USD retail, depending on the exact year and market. Older ones such as 2006 run higher.
1
VPN appears to work.
WOW 🤯 looks like the upcoming meeting details about EU Canada CETA is actually blocked for Canadians to view it 👀 I asked Grok and GROK confirmed the full agenda and exact location are on the EESC site, which is currently geo-blocked for Canadian IPs Also proof I’m not a Russian Bot 😀
3
Tremendous vertical heat.
WATCH: SpaceX gives viewers a front-row seat to Starship’s return to Earth, sharing stunning POV footage from aboard the spacecraft. The video captures its final approach and first-ever catch at Starbase, offering a unique perspective as SpaceX works toward a fully reusable rocket system. Download the Fox News app or go to Foxnews.com for more: foxnews.onelink.me/xLDS/z2jy…
1
7
Gall stones?
First Lady Melania Trump steps off Air Force ONE… and people immediately notice something unusual.
17
Wild Horizon retweeted
Just saying , You can’t fix STUPID, but you can stop voting for it !
97
283
4
1,437
8,705
Wild Horizon retweeted
Canada’s Real-Time Rail is officially live. Chief Delivery Officer, Jude Pinto celebrates the launch of our new 24/7/365 sovereign payment system, built in Canada, for Canada. Watch the full update: payments.ca/canadas-real-tim… #PaymentsMatter #RealTimeRail
2
11
341
Public emergency test messages will be sent across Canada on November 18 to help you recognize what a lifesaving emergency alert looks and sounds like. Find out what time the test takes place in your region: alertready.ca/testing-schedu…
6
22
3
21
2,850
Missed out yet once again
Today, our government announced the new Family Affordability Benefit: a one-time, tax-free $500 payment per child for eligible families. That’s more than $38 million in direct support for over 77,000 children across Newfoundland and Labrador. Together with Budget 2026, that’s more than $380 million invested to help families, seniors and workers keep more of their hard-earned money. We heard the challenges people are facing, and we’re following through on our commitment to make life more affordable for all of us.
9
Wicked!
BREAKING: Citi just raised its SpaceX price target to $280 from $240, maintaining a Buy rating after the historic Starship catch. • Second increase in under a month: $200 → $240 → $280. • That’s a 40% increase across the two revisions. • Citi attended Flight 15 at Starbase and witnessed the milestone. • The bank also raised its revenue and adjusted EBITDA forecasts for Q4 2026 and the first half of 2027, mainly for SpaceX’s AI business. Ahead of the mission, Citi described Flight 15 as a potential “monumental space-industry catalyst” that could set the stage for rapid reusability. The successful catch also advances Citi’s longer-term scenario of $900+ per share, dependent on SpaceX achieving key engineering milestones at scale. SpaceX keeps making history. Wall Street keeps raising its expectations.
4
Nothing wrong with copper. It's just slower than fiber.
"It was an old copper wire that basically was going to be decommissioned... This is part of our maintenance that we do on this really old architecture of a telecom network that goes back decades," says @SecDuffy on what led to Friday's ground stop. "The rest of the world — every institution, every company, not just in the U.S., but around the world — they've all switched over to digital from fiber. It's just the FAA is still using this really old telecom network that has to be updated, upgraded, and I think built brand new."
4
Costs about $1 million to fuel Starship. If they recover both the ship and the booster, that's their cost to get 100 TONS of payload to orbit. Unreal. New era in space exploration.
SHIP CATCH: SpaceX has caught Starship 42 at Starbase to conclude Flight 15! A historic moment in humanity’s journey to explore the stars.
225
553
51
14,701
664,371
Wild Horizon retweeted
An estimated 100 million American homes are running on a router that nobody has logged into since the day it was plugged in. Not once. Not to change a password, not to check for updates, not to look at a single setting. And those same homes are paying $70, $80, even $100 a month for "fast" internet. Then the video call freezes in the middle of a work meeting. Netflix buffers on a Friday night. The kids' games lag. The Wi-Fi "just feels slow." So what does everyone do? They call the provider and yell. They upgrade the plan. They buy a $140 Wi-Fi extender. One household I know replaced their router twice in 18 months and spent more than $400 doing it. None of it fixed the problem. Not because the internet was too slow. Not because the new router was bad. Because every router ships on factory settings built for an "average home on an average day," crowded onto the same Wi-Fi channel as every neighbor, steering devices onto the wrong band, using the slowest default DNS, running firmware that is months or years out of date, and treating your work video call the same as someone's 40GB game download. Then I sat down for 10 minutes in the admin panel. I didn't change the plan. I didn't buy new hardware. I didn't call the provider. I changed 6 settings: channel, band steering, DNS, firmware, QoS, and one buried security toggle most people never touch. Same router. Same plan. Same house. [Speeds nearly doubled / insert your real before and after speed test numbers]. "Your router was never too slow. It was never told how to manage your home. And nobody, not your provider, not the store, not the box it came in, was ever going to tell you the fix was free." Here are the 6 settings I changed (and exactly how to do it) 🧵
38
314
11
1,519
365,414
Wild Horizon retweeted
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.
Replying to @MSFT365Status
We have released the Preliminary Post-Incident Report of last week’s outage, which is accessible via the Admin center under MO1550821 and EX1550543.
184
399
104
2,993
557,771