1
6
submitted 51 minutes ago by yogthos@lemmy.ml to c/technology@lemmy.ml
2
49
submitted 12 hours ago by chobeat@lemmy.ml to c/technology@lemmy.ml
3
34
submitted 16 hours ago by yogthos@lemmy.ml to c/technology@lemmy.ml
4
13

Google has partnered up with Jeff Bezos' Blue Origin to deploy small satellite data centers into space, as part of its Project Suncatcher project. Each of these satellites will be equipped with "roughly the capacity of a data center rack" and will enter into a sun-synchronous orbit via heavy-lift New Glenn rockets.

The rocket will carry several Google tensor processing units, the company's proprietary AI chips, along with data center servers. The first launch isn't scheduled until early 2029, so we have a couple of years to see if this whole project even works.

This is an experiment that Google calls a "long-term moonshot" to see if it's possible to put AI infrastructure in space by "tapping into the abundant solar power in orbit." The benefits of this would be massive. Data centers here on Earth are notorious hogs, with their snouts all over electricity grids, land and cooling systems.

The hope is that the harsh vacuum of the cosmos will be a better fit for the technology. After all, in space nobody can hear you make endless industrial noises and high-pitched whirs all day every day. This is a very real situation for folks living near data centers.

Google is far from the only company trying to kick the data center can straight into outer space. Elon Musk's SpaceX has been experimenting with the idea, though it may involve putting a gigantic catapult on the moon (really.) There are also some startups fiddling with the technology, like Starcloud.

Can this even work? We don't know yet, though there are some serious hurdles to overcome. Google did deploy its first AI server satellite back in October, but it was sent into low-Earth orbit and can only operate for 15 minutes at a time. Scaling up the affiliated cooling systems looks to be incredibly difficult.

That's because standard heat dissipation doesn't work in space, so it has to be released through pipes and panels rather than conventional cooling systems. There's also the matter of radiation. It's everywhere and causes something called "bit flip." This essentially flips the binary code from a one to a zero, or vice versa. Obviously, this would be a major issue for binary-coded systems.

Did I mention the actual launches? It's extremely expensive to send stuff to space. Just one Falcon 9 launch costs around $74 million and the maximum payload can barely cover the hardware for a small server room, let alone a hyperscale data center.

"Expanding from one satellite to a vast network of them that operate like a giant data center will take years and enormous funds," Brandon Lucia, a professor of electrical and computer engineering at Carnegie Mellon University, told The New York Times. "If you do this on a large scale, there are additional engineering problems."

Finally, there's a risk to us humans here on Earth. Scientists have been considering a theoretical scenario called Kessler syndrome for decades. This is when the density of objects in low-orbit gets so high and collisions become so commonplace that it creates a chain reaction of debris. We would be on the receiving end of that debris.

This theory was posited back when there were just under 2,000 items circling a low-Earth orbit. That number has since risen to over 47,000 and Elon Musk recently floated an idea to add millions of new satellites into the mix.

5
21
submitted 16 hours ago by yogthos@lemmy.ml to c/technology@lemmy.ml
6
3
submitted 12 hours ago by Confidant6198@lemmy.ml to c/technology@lemmy.ml

cross-posted from: https://lemmy.ml/post/55521865

7
23
No to Pax Silica (notopaxsilica.com)
submitted 23 hours ago by chobeat@lemmy.ml to c/technology@lemmy.ml
8
28
submitted 1 day ago by yogthos@lemmy.ml to c/technology@lemmy.ml
9
17
submitted 1 day ago by yogthos@lemmy.ml to c/technology@lemmy.ml
10
14
submitted 1 day ago by yogthos@lemmy.ml to c/technology@lemmy.ml
11
32
submitted 1 day ago by chobeat@lemmy.ml to c/technology@lemmy.ml
12
78
submitted 2 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
13
6
submitted 1 day ago by yogthos@lemmy.ml to c/technology@lemmy.ml
14
21
submitted 2 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
15
20
submitted 2 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
16
22
submitted 2 days ago by chobeat@lemmy.ml to c/technology@lemmy.ml
17
50
submitted 2 days ago by chobeat@lemmy.ml to c/technology@lemmy.ml
18
8
submitted 2 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
19
40
submitted 2 days ago by davel@lemmy.ml to c/technology@lemmy.ml

The California Department of Motor Vehicles announced it has banned Waymo from operating its self-driving taxis on all state freeways due to what it called an “imminent hazard to public safety.”

The DMV said restrictions took effect on Nov. 11 and will remain in place “until Waymo demonstrates to the Department that it has taken effective corrective actions to address the deficiencies that precipitated the restrictions.”

Before freeway operations can resume, the DMV said Waymo must provide sufficient evidence that its vehicles can safely detect and respond to construction zones, emergency vehicles, and other roadway situations.

California’s restrictions bar Waymo from both operating and testing its driverless vehicles on the state’s freeways.

Waymo will continue to operate its service as normal on surface streets in California.

The company told KTLA it has also temporarily restricted freeway operations across its other operating markets to evaluate their performance in response to the ban in California.

Waymo currently serves riders in 15 markets, including Los Angeles, San Diego, the Bay Area, Las Vegas, Phoenix and more, according to its website.

The ban comes after two recent safety incidents in the Bay Area involving the robotaxis, according to the DMV.

20
13
submitted 2 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
21
36
submitted 3 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
22
167

You are probably already aware of the recent Microsoft outage. For more than a day last week, a large share of the world’s office workers could not reliably send or receive email.

The trouble started on the afternoon of Nov. 12, when Outlook users found they could no longer reach their mailboxes. Within about an hour, Downdetector had logged reports from 74 countries and territories. Teams and Copilot features that rely on Exchange Online broke too.

Government systems in Singapore and Japan were hit, as were communications at the Supreme Court of the Philippines and, in Australia, the federal police and the country’s spy agency.

Microsoft said the outage was not a cyberattack. In a preliminary explanation, it pointed to an issue from an earlier network capacity upgrade that surfaced after a more recent network change. The company declared service fully restored early on Nov. 14, and has promised a full post-incident report.

The disruption is the latest in a run of Exchange Online failures this year. On Aug. 31, a bad authentication configuration knocked out email and spilled over into Teams, SharePoint, OneDrive and Defender for about 12 hours. Some estimated that lost productivity from the November outage could approach $7 billion.

For the companies selling open source alternatives to Microsoft’s products, the episode is a chance to make an argument they have been making for years. It’s FOSS asked several of them what governments and businesses should be thinking about as they recover. Their answer, broadly, was not that their software never fails. It was that no single company should be able to stop an entire economy’s email at once.

“Errors can happen to any provider,” said Peter Ganten, the chief executive of Univention, a German company that makes open source identity management software. “The more important question is concentration.”

“When hundreds of millions of people in thousands of organizations worldwide depend on the same infrastructure, running the same software and managed by the same company, a single fault in the wrong place can bring public life to a standstill,” Ganten said. This failure appears to have been technical, he noted, but “an external attack could have had equally severe consequences.” The same dependency, he added, leaves entire economies exposed to sudden price increases or politically motivated service restrictions.

The scale he describes is real. Microsoft reported more than 450 million paid commercial seats for Microsoft 365 in January this year.

Nextcloud, which makes a self-hostable file sharing and collaboration suite, struck a gentler note while the outage was still unfolding. “Mistakes happen in the IT industry,” Jos Poortvliet, a co-founder of the company, said in a statement on Friday. “This holds true for companies of all sizes, including us. Our heart goes out to all the admins today.”

But he too pointed to concentration. “Especially in critical infrastructure, monopolies are increasing the risk of stalling businesses globally if an incident occurs,” Mr. Poortvliet said. “When everything is hanging on a single vendor, companies can’t switch providers quickly to get back up and running, or have a second setup as backup, or pull the plug when under attack and keep working air-gapped.”

The weak point is the login

The outages this year have shown how one fault can spread. In August, a problem with Microsoft’s authentication configuration did not just break email. It took down other Microsoft 365 services that sit on the same sign-in layer.

Ganten said that was the risk worth worrying about most. “When authentication fails, every service that depends on it fails with it,” he said. Identity, in his view, should be an open and separate layer that different providers can run, so that services stay reachable when one of them goes down. Univention sells an identity platform, Nubus, built on that idea.

‘Outsourced operations’ is not ‘outsourced risk’

Galina Goduhina, the commercial director of ONLYOFFICE, an open source office suite, said organizations had misread what the cloud bought them. “The cloud has made infrastructure someone else’s problem, but it hasn’t made downtime someone else’s consequence,” she said. “Organizations need to stop confusing outsourced operations with outsourced risk.”

The question, she said, is whether an organization has “enough control, portability and independence to keep working when their primary provider cannot.”

She was candid that open source software is not immune. “The difference isn’t that open source fails less,” Ms. Goduhina said. “It’s that failure doesn’t necessarily leave you waiting for a single vendor to act.” Whether organizations can actually use that freedom, she added, depends on their preparation.

That raises an obvious objection: moving from Microsoft’s cloud to another company’s cloud could simply trade one dependency for another. Ganten agreed that it can. “It does, unless the software is open source and built on open standards,” he said. Such software can be run without its original vendor and, in the worst case, maintained by someone else entirely. Leaving is harder than it looks

None of the companies suggested that switching is quick. Asked what it would take for a 500-person organization to move off Exchange, Goduhina said the mailboxes were the simple part.

“Moving 500 mailboxes is the easy part to estimate,” she said. “Replacing years of accumulated integrations, permissions and habits is not.” She would plan for several months, starting with an audit of dependencies and a pilot group. “The biggest migration risk is discovering too late that Exchange was doing far more than handling email.”

Some governments have already done it. The German state of Schleswig-Holstein moved more than 44,000 mailboxes from Exchange to Open-Xchange by October 2025. Poortvliet said open source alternatives “exist, are ready to use and have been proven at scale.”

For organizations that are not ready to leave, Ganten suggested a smaller step. Where critical services are involved, he said, organizations should be able to keep at least a minimal operation running without their usual provider.

“This fallback,” he said, “must be rehearsed regularly.”

23
26
submitted 3 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
24
29
submitted 3 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
25
149
submitted 5 days ago by yogthos@lemmy.ml to c/technology@lemmy.ml
view more: next ›

Technology

43610 readers
151 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 7 years ago
MODERATORS