computers

06 Jul 2026

Slashdot

South Korea's SK Hynix Launching $28 Billion US Listing To Ride Global AI Wave

SK Hynix is launching a Nasdaq listing expected to raise about $28 billion, giving US investors easier access to one of the biggest beneficiaries of the AI memory-chip boom. Reuters reports: The company will sell 17.79 million new shares in the depository receipt listing on the Nasdaq. Ten ADRs will represent one common share and the stock will be sold in a price range that is due to be revealed on Monday, based on SK Hynix's Seoul trading price. SK Hynix's share price was down 4% at 2,327,000 won each on Monday, but the stock is up about 273% this year, as it rides surging global investor demand for AI stocks. Korea's KOSPI was down 2.2% on Monday. [...] SK Hynix has been among the world's largest beneficiaries of the AI boom as it outperformed its major rivals Samsung and Micron. "This is more than a liquidity event," said Dave Mazza, the chief executive officer of Roundhill Investments in New York, which manages an exchange-traded fund tracking DRAM manufacturers, which is one of the most popular ways for U.S. investors to trade SK Hynix's stock. "SK Hynix has been one of the most important companies in the world that most U.S. institutions could not easily own." "The listing removes an accessibility discount, not a quality discount." [...] SK Hynix said the proceeds from the listing of the American Depositary Receipts will be used to build chip factories in South Korea and buy chipmaking equipment including an extreme ultraviolet scanner made by Dutch equipment maker ASML. The final price of the New York listing is due to be set on Thursday, ahead of the stock starting trade on Friday, regulatory filings showed. The company's management will meet global investors on a roadshow this week. The deal is expected to be the second-biggest share sale after a record $85.7 billion initial public offering by SpaceX last month, surpassing Saudi Aramco's $25.6 billion IPO in 2019 and Alibaba's similar-sized offering in 2014.

Zombie 'Who Owns Unix?' Lawsuit Comes Alive Again

The long-running SCO/IBM Unix and Linux ownership dispute has resurfaced yet again, this time through SCO successor Xinuos, which is trying to pursue old license and copyright claims tied to Project Monterey. "The core issue seems to be whether Xinuos even has the right to litigate the matter, or if some ancient legalese in the original agreements means the window for legal argument has long since expired," reports The Register. From the report: [T]he roots of the case are the 1998 alliance between IBM and a company called the Santa Cruz Operation which sold a version of UNIX for x86 CPUs. Those two companies, plus Intel and Sequent, created "Project Monterey" -- an effort to create a unified version of UNIX that could run on multiple processors. By 2001, Project Monterey was close to delivering a unified UNIX, an achievement made possible by blending code from IBM and SCO. By then, a little project called "Linux" already ran on multiple processors. Big Blue decided Linux was the future and bailed from Project Monterey -- then allegedly contributed some Monterey code to the open-source project and to its own AIX and Z operating systems. SCO felt it owned some of that code, so sued IBM. SCO and its successors struggled to survive, but interested parties kept the lawsuit alive because the chance to emerge as owner of parts of the Linux codebase, and IBM's code, had the potential to turn into a colossal payday. The case and its successors ended in 2021, with a settlement that saw litigants agree to end the matter without IBM admitting fault. But by then, SCO had sold its software to a biz called Xinuos that decided to fight on. The Xinuos case has burbled along quietly since, and on June 22nd reached the milestone of a hearing. The matter has become a little more modern, if only because this hearing was held online and the presiding judge appeared to unwittingly be on mute at one point. But the arguments otherwise seemed to revisit Project Monterey, debated the relevance of past litigation, contested who owned what, when they owned it, and how they could prove it. Xinuos argued IBM never had a license for SCO code. Big Blue argued that it did nothing wrong.

Secret Claude Tracker Shocks Users After Anthropic's Anti-Surveillance Stance

An anonymous reader quotes a report from Ars Technica: Anthropic quickly removed a tracker secretly monitoring Claude Code users in China after a security researcher exposed the hidden code and condemned the spyware-like tracking as a "serious breach of user trust." Last week, a web developer known as "Thereallo" was researching privacy issues in Claude Code and was shocked to find that the AI firm was using "prompt steganography" to hide code that tracks Chinese users "in plain sight." This code wasn't malicious, but it was sending information to Anthropic that most users wouldn't detect, relying on shorthand markers to quietly flag users' timezone, proxy, and potential connection to Chinese AI labs that Anthropic has accused of distillation attacks. On X, Anthropic engineer Thariq Shihipar confirmed that the tracker was added to Claude Code as an "experiment" in March. According to Shihipar, the code "was meant to prevent account abuse from unauthorized resellers and protect against distillation." Regarding the former, The Washington Post found unauthorized retailers have sold access to free models for $1 a month, and pro subscriptions that can cost $100 monthly sell for "as little as $12." Supposedly, Anthropic has "actually been meaning to take this down for a while," Shihipar said of the hidden code, because engineers have "landed stronger mitigations since then." Privacy advocates were not happy with the explanation, though, warning that the code is evidence that Anthropic is willing to cross lines to surveil users. That's perhaps especially surprising, considering that Anthropic riled the Trump administration by refusing to allow the US government to use Claude to surveil US users. The AI firm has since sued the White House over the clash. The Post suggested that the tracker incident is a sign that US firms like Anthropic are taking "increasingly aggressive measures" to block Chinese AI firms from copying their models. A more defensive stance has apparently become critical. In the past year, Chinese firms have "consistently matched" US firms' model capabilities "within months," the Post reported. Most recently, "a new, free AI model from Chinese company Zhipu AI was better at finding computer vulnerabilities than Anthropic's Claude Opus 4.8 model, which was released in May," the Post reported.

Ars Technica

NRC is (sort of) getting rid of "as low as reasonably achievable" standard

Its issues with current nuclear safety standards are termed semantic, not physical.

06 Jul 2026 5:48pm GMT

Katalyst's satellite rescue mission is now in pursuit of NASA's Swift

It will take several weeks for the Link spacecraft to rendezvous with NASA's Swift observatory.

06 Jul 2026 5:14pm GMT

Secret Claude tracker shocks users after Anthropic’s anti-surveillance stance

Anthropic accused of spying on users; engineer says "experiment" is over.

06 Jul 2026 4:44pm GMT

05 Jul 2026

OSnews

Review: iodéOS offers a frictionless de-Googled Android experience

Wherever in the world you go, the smartphone landscape is dominated by Android and iOS, and while this has always been problematic, recent events have made the dependency on two American tech giants for what is probably our most personal computing device even more problematic than it already was. We use our smartphones to keep our secrets, do our banking, interact with our governments, share our deepest thoughts with our friends and family, and a whole lot more. Having this invaluable tool the vast majority of us depend on tied entirely to Google and Apple is not just bad for the market, it's also a downright threat to the national security of anyone not living in the US. Here in Europe, there's been an awakening lately, with governments, companies, and people alike finally realising that having our entire digital infrastructure controlled by foreign, adversarial interests is a terrible idea. Sadly, breaking free from our Android and iOS chains is not so easy. The most ideal solution would be a truly open source alternative smartphone operating system, but that's a hard sell for 99.9% of smartphone users who need the applications required to do their finances, talk to their friends, or interact with their governments. The cold and harsh truth is that with very few exceptions, these applications simply do not (yet) exist for smartphone operating systems that aren't Android or iOS. The only viable alternative at this point in time is to take whatever's left of the Android Open Source Project, remove anything that ties it to Google and its services, fill in the gaps with alternative services and applications, and sell it as a Google-free or de-Googled Android platform. There's several projects in this space, and with Europe drunkenly stumbling out of the technological hole it dug itself into, it's no surprise that two of the more popular alternatives to Apple or Google-controlled smartphones come from Europe (and from the same country, no less). Today, we're taking a look at one of these: iodéOS. Iodé is a company based in Toulouse, France, which focuses on offering a Google-free Android called iodéOS, either preinstalled on phones you can buy, or as a ROM you can install yourself on supported devices. As a company, iodé makes its money through selling devices with iodéOS preinstalled, through an optional premium subscription (that I didn't take a look at), and through donations, and all of their code is published as open source on their Gitlab instance hosted in France. Iodé loaned me a Fairphone 6 with iodéOS preinstalled, one of he many smartphones and tablets they sell through their online store for review. This isn't going to be an Android review; you already know what Android is like, and there's no need for me to rehash any of that. Instead, I want to focus on the things that make using de-Googled Android different from using Google Android. Don't be afraid of microG There are various ways to go about making a de-Googled Android variant, and iodéOS chose the LineageOS route, with microG installed on top. For those unaware, microG is a project which aims to replace the various proprietary parts of Google Play Services, required by many Android applications, with open source reimplementations. While it doesn't offer 100% compatibility, it works exceptionally well, and you'll be hard-pressed to find applications just don't work at all with microG. IodéOS updates its microG installation through a dedicated F-Droid repository that's obviously enabled by default, so you don't have to do anything yourself. Using microG instead of Google Play Services doesn't mean you have to rely solely on whatever's available in F-Droid, since there are a variety of alternative Play Store frontends available. IodéOS ships with the Aurora Store, which is an open-source frontend to the Play Store that can be used with or without a Google account. If you use it with your Google account, you'll gain access to whatever applications you already own, including paid ones, but you won't be able to buy applications inside Aurora. You can, however, buy an application on the Play Store website, after which it will show up in Aurora as well, assuming you're logged in with the same account. Aurora also comes with something something called FakeStore, which is sadly an important part of the puzzle; it's a stub application that has the same package name as the real Play Store. Some applications check whether the Play Store is available before working properly, so this is sadly needed to ensure maximum compatibility. The only issue I sometimes ran into with Aurora is that it would load up its listings, but then any application I tapped on said it was unavailable. When this happened, reloading the Aurora application always fixed the issue. Annoying, but not gamebreaking. A few things did not work for me when using microG on iodéOS, and they're exactly the things you'd expect not to work. If you have a WearOS device, you're out of luck; WearOS devices simply do not work when using microG, but there is a bounty to add support for it. If you want to use a smartwatch with iodéOS, there are various options available, such as Garmin devices, which is what I used during my testing and it worked flawlessly. Another feature from "regular" Android that simply won't work is RCS. There's only one RCS client available on Android, Google Messages, and as you can imagine, Google is in no rush to allow devices without Google Play Services to register for and use RCS messaging. Tying to register with Google Messages will fail, and there are no other RCS clients available (save for a few China and India-specific clients). There's a microG bounty for this, too, but no luck so far. Of course, there are countless messaging platforms that work just fine on iodéOS - regular SMS, WhatsApp, Facebook Messenger, Signal, and so on - and especially if you're European, it's unlikely RCS support matters to you at all. I just don't

05 Jul 2026 9:29pm GMT

Improved DEC Alpha emulator runs Windows 2000 for Alpha and OpenVMS and Tru64 with X11

Colour me positively surprised, as I had no idea Alpha emulation had progressed this much. As you might know, I'm involved a bit in the OpenVMS community and the Alpha emulation side via AXPBox. AXPBox (github) is a fork of the es40 alpha emulator by Camiel Vanderhoeven (who is now Chief Architect at VSI, the company that makes OpenVMS, for x86 nowdays). There have been many forks of es40 in the past and recently a new one has popped up with some great new features. Like speedups via a JIT compiler, S3 graphics port from MAME and ARC support, resulting in the ability to run Windows 2000 for the DEC Alpha. ↫ Remy van Elst Not only can you run the unreleased Alpha version of Windows 2000 on this forked emulator, it's also capable of running OpenVMS and Tru64 UNIX. In fact, both OpenVMS and Tru64 can run their full X11 CDE desktops on the emulator as well, which is incredibly cool and a huge milestone. As the name of the original emulator implies, it's emulating an AlphaServer Es40 from the turn of the century, which should be fast enough for enthusiast use. The last AlphaStation ever made, the ES47, is still very high on my list of computers I desperately want but will never have - they are incredibly rare, and whenever they do come up for sale, incredibly expensive. If you have one, consider yourself lucky, and please, write about it! Tell the world!

05 Jul 2026 8:27pm GMT

LineageOS and Android’s upcoming developer verification: what it is, and how it affects you

LineageOS, the de-Googled Android ROM that serves as the backbone for pretty much the entire custom Android ROM community, has published an article about what the Android developer verification changes mean for them. I really like the factual tone of their article, especially this part: Critics such as F-Droid, EFF, and "Keep Android Open" point out that this also happens to route every install path through Google-controlled infrastructure, hands Google a kill switch over any app or developer worldwide, and arrives shortly after Google's antitrust lawsuits. Both things can be true at once: real fraud is a problem and the restriction of developers is a convenient side effect of solving it this way - and we're not in a position to pretend we know Google's internal reasoning. We're just telling you what they've said and what it changes; you can weigh the "why" yourself. ↫ Nolen Johnson on the LineageOS website For LineageOS, these new verification measures don't really mean much, as they don't affect the project's work or software. The developer verification infrastructure is a separate application that is part of Google Mobile Services, and LineageOS does not ship GMS nor does it ever intend to. As such, they don't have to do anything, as this won't be an issue unless LineageOS users choose to install a GApps package that happens to include the developer verification infrastructure. If Google were to move the developer verification infrastructure into Play Services in the future, LineageOS makes it clear they'll disable it globally, as they have done with a number of other "annoying Play Services-provided over-the-air update implementations". There really isn't much more they can do; the rest is up to users and projects that use LineageOS as their base.

05 Jul 2026 8:11pm GMT