fidzu : computers

NASA has called off a $30 million mission to rescue its aging Swift space telescope after Katalyst Space's Link spacecraft developed persistent control and positioning problems. The Associated Press reports: Katalyst said Link will not attempt to capture Swift and boost it to a higher orbit because of problems with controlling the spacecraft. NASA said this means the telescope will plunge through the atmosphere after more than 20 years of tracking some of the biggest explosions in the universe like gamma ray bursts and exploding stars. Its demise is not expected before October. NASA paid $30 million to Katalyst in an attempt to raise the telescope to a safer, longer-lasting orbit. Intense solar activity caused it to lose altitude faster than expected. The rescue spacecraft went into an uncontrollable spin a few weeks after its liftoff in early July. While flight controllers managed to slow Link's tumble, issues continued to plague its pointing and positioning in orbit. "This is not the outcome we were working toward, but it does not change why this mission was worth attempting," NASA Administrator Jared Isaacman said in a statement. As a consolation prize, Katalyst will continue to operate Link in proximity with the telescope to demonstrate capabilities for future rescue operations. Katalyst CEO Ghonhee Lee said it was an ambitious mission on an aggressive timeline that was thrown together in under a year. "We took on this high-risk, high-reward challenge and are proud of the milestones we reached along the way," Lee said in a statement. "We have already learned a tremendous amount."

Read more of this story at Slashdot.

20 Aug 2026 7:00am GMT

An anonymous reader quotes a report from NPR: Meta was infused with a culture in which employees obsessed over user numbers and consistently pushed safety to the side, according to Arturo Bejar, a former employee turned whistleblower, who testified today in the landmark child safety trial against the social media company. Only one man had the ability to change that, Bejar said: CEO Mark Zuckerberg. But he didn't. "At the end of the day, it was the company culture that Mark had created that made it so that it was practically impossible to deliver features that addressed the wellbeing and safety issues that we've been talking about," he said. Bejar is a linchpin witness for a consortium of states led by California, Colorado, Kentucky and New Jersey that sued Meta, alleging violations of consumer and child data protection laws, and that the company lied to the public about risks its platforms posed. The attorneys for the states say Meta designed Facebook and Instagram to hook young users and to keep them on site longer thanks to features such as infinite scrolling and the "like" button. Meta has denied the allegations. In his opening statement on Tuesday, attorney Paul Schmidt argued that the company was sensitive to the risks to teens, sought to address them and did not deceive the public about them. The state attorneys have not yet said if they will call Zuckerberg as a witness. Testifying in federal court in Oakland, California, for a second day on Wednesday, Bejar, who worked on safety issues at Meta for eight years, said he interacted with Zuckerberg dozens of times, and charged that Zuckerberg was not telling the truth when he made public denials that the company put profits over safety. In particular, Bejar addressed a widely-shared Facebook post Zuckerberg made in 2021 after another whistleblower, Frances Haugen, shared internal documents with The Wall Street Journal that highlighted risks to the mental health of teens. In the post, Zuckerberg said it's "just not true" that Meta prioritizes profit over safety and wellbeing. "Based on my experience at Meta, that is not an accurate statement," Bejar said. [...] Bejar testified, at almost every turn the company chose policies that boosted usership and revenue over safety. Safety was "not a meaningful priority," he said.

Read more of this story at Slashdot.

20 Aug 2026 3:30am GMT

Without a rescue, NASA's Swift Observatory is expected to reenter the atmosphere later this year.

20 Aug 2026 12:18am GMT

BrianFagioli writes: PINE64 has some very bad news for Linux hardware fans. PINE64 says it has no plans to produce additional Linux devices in the near future because of the ongoing DRAM and eMMC shortage. Future production will depend on component pricing after mid 2027, while existing PineNote and PineTab2 inventory could run out in roughly three months. The company says PineTime, PineVoice, and Pinecil production will continue as usual, but the outlook for its Linux hardware is much less certain. "That's it for this post, all in all it's a bit bleak for the Linux devices, but in the meantime PineStore still have a great lineup of MCU powered devices which will continue to expand with more exciting devices," the company said.

Read more of this story at Slashdot.

19 Aug 2026 11:00pm GMT

US residents face trade-offs as delivery drone services such as Prime Air expand.

19 Aug 2026 10:02pm GMT

When I wrote about using Windows 11 for a month as part of the ongoing OSNews fundraiser (keep donating to get me to do the same for macOS!), one of the things I mentioned was that "the modern desktop context menu has its own classic Win32 context menu". This is, in fact, a long-standing complaint I've repeatedly used as the perfect example of just how chaotic and low-quality Windows has become. Thankfully, and naturally I fully attribute this to my repeated complaints (*), Microsoft has been working on a brand new, faster, configurable context menu, and Neowin actually reviewed it. If you ask me, this revamped context menu addresses just about the biggest problem users had with the one in Windows 11, and that is the need to click through more buttons than necessary to do simple things like renaming a file or opening its properties. That problem is now basically gone. I have no issues with the new design. It looks modern, it feels more consistent with the rest of Windows, and even though all the new sections can still make it look a little busy, you now have the option to make it as simple or as button-packed as you want. That should cover most use cases and preferences well. I'd even say that when the new context menu becomes available to everyone, my guide on how to bring back the classic context menu might become obsolete. ↫ Ivan Jenic at Neowin The biggest reason I'm linking to this is not because I care about whatever monster of a context menu Windows users are having to deal with. No, I'm only linking to this because I never in my life imagined I'd be linking to a review of a context menu. I mean, at least it's not the chess application icon. That would be embarrassing. I get a perverse sense of joy out of this.

19 Aug 2026 9:58pm GMT

Framework says it's replacing some out-of-warranty AMD mainboards.

19 Aug 2026 8:21pm GMT

A great and concise history of the run-up to MS-DOS 2.0. Yet, there was a nagging feeling that a single-tasking CP/M clone was inadequate for the new generation of personal computers. Digital Research released multi-user, multitasking MP/M-86 in September 1981 and announced the single‑user multitasking Concurrent CP/M in early 1982. In response, Microsoft came up with a plan for tiered approach to its operating systems: single-user/single-tasking MS-DOS at the bottom; multi-user/multitasking XENIX at the top; and in the middle, something called XEDOS: a single-user version of XENIX. This "pyramid of upward-compatible operating systems" was announced in a Byte Magazine editorial in January 1982. ↫ Nemanja Trifunovic I've always found this tiered approach fascinating, and the world surely would've looked quite different had Microsoft been able to make it work. I doubt Windows NT would ever have existed, and most of the world would probably be running a XENIX-based Windows today (all else being equal, which is of course unlikely and silly). Regardless, MS-DOS 2.0 contained a few UNIX-like utilities to deal with its brand new support for directory trees and other new features, and even had a /dev directory.

18 Aug 2026 9:59am GMT

If you thought pervert glasses weren't bad enough, Apple is taking it up a notch by adding cameras to its AirPods. Apple is working on camera-equipped AirPods that appear to be nearly ready to launch, based on a video MacRumors found in the macOS Tahoe 26.7 release candidate. In a short demo, a man holds a book up so the camera in the AirPods can see the title. "With Visual Intelligence, your world becomes savable. See something you like? Just ask me to save it for later," says the voiceover text. ↫ Juli Clover at MacRumors AirPods are tiny. I've seen people use them at the gym. I've seen them on playgrounds. I've seen them around swimming pools. People use them at the beach. They're used at schools. In locker rooms. Tiny cameras in tiny AirPods that can photograph anything in front of the user are a pervert's wet dream. Abusers are going to love this. Why wear bulky glasses anyone can see and try to demand you take off, when you can wear tiny AirPods that have already been fully normalised in society? Was there not a single woman or parent on the team that made this? All over the United States, people are destroying Flock surveillance cameras. More and more communities are rising up and demanding these things removed from their streets and neighbourhoods. The awareness of just how pervasive mass government surveillance has become is growing, and Silicon Valley's complicity is not exactly a secret. And in this climate of rapidly growing concern and anger, Apple is going to add tiny cameras to its tiny AirPods. Was there not a single person of colour or protester on the team that made this? How detached from reality do you have to be to greenlight something like this? Does anyone - regardless of skin colour, gender, or political leaning - want even more cameras around them?

18 Aug 2026 9:41am GMT

Over the last few weeks, we have been doing research on the integration of our official distribution packages when installed on a target system. In this context we have been looking at the current uses of alpm-install-scriptlet(5) files and alpm-hooks(5) in around 120 package source repositories (alpm-source-repo(7)) to better understand the underlying functionality and use-cases these two integrations offer and target. In this article we are going to look at how these two systems work, how Arch Linux is currently using them and attempt to provide suggestions for when to use which. Learning about alpm-hooks(5) and alpm-install-scriptlet(5) files …

09 Aug 2026 12:00am GMT

This is just a short note on my blog that I have resigned from Arch Linux a package maintainer, developer and security team. I've spent around 10 years as an AUR maintainer, security team, Package Maintainer and then Developer. I implemented support for debug packages, did the initial POC work that would become the git migration and even somehow managed to pull of an online conference during The Plague with the help of others.

01 Aug 2026 12:00am GMT

Good morning from JetBrains Berlin office!

01 Jun 2026 12:00am GMT