Earlier this year, popular NAS vendor Synology announced it would start requiring some of its more expensive models to only use Synology-branded drives. It seems the uproar this announcement caused has had some real chilling effect on sales, and the company just cancelled its plans.

Synology has backtracked on one of its most unpopular decisions in years. After seeing NAS sales plummet in 2025, the company has decided to lift restrictions that forced users to buy its own Synology hard drives. The policy, introduced earlier this year, made third-party HDDs from brands like Seagate and WD practically unusable in newer models such as the DS925+, DS1825+, and DS425+. That change didn’t go over well. Users immediately criticised Synology for trying to lock them into buying its much more expensive drives. Many simply refused to upgrade, and reviewers called out the move as greedy and shortsighted. According to some reports, sales of Synology’s 2025 NAS models dropped sharply in the months after the restriction was introduced.

↫ Hilbert Hagedoorn at Guru3D.com

If you want to screw over your users to make a few more euros, it’s generally a good idea to first assess just how locked-in your users really are. Synology is but one of many companies making and selling NAS devices, and even building one yourself is stupidly easy these days. There’s an entire cottage industry of motherboards and enclosures specifically designed for this purpose, and there are countless easy-to-use software options out there, too.

In other words, nobody is really locked into Synology, so any unpopular move by the company was bound to make people look elsewhere, only to discover there are tons of competing options to choose from. The market seems to have spoken, and Synology can only respond by reversing its decision. Honestly, I had almost forgotten what a healthy tech market with tons of competing options looks like.

MicroPythonOS is a lightweight, fast, and versatile operating system designed to run on microcontrollers like the ESP32 and desktop systems. With a modern Android-like touch screen UI, App Store, and Over-The-Air updates, it’s the perfect OS for innovators and developers.

↫ MicroPytonOS’ website

It’s quite neat to see this running in such a constrained environment, especially considering it comes with a graphical user interface, some basic applications, and niceties like OTA updates and an application repository. As the name implies, MicroPythonOS uses native MicroPython for application and driver development, making cross-platform portability from microcontrollers to regular PCs a possibility. It’s built on the MicroPython runtime, with LVGL for graphics, packaged by the lvgl_micropython project.

It’s still relatively early in development, but it’s completely open source so anyone can help out and improve the project. I’m personally not too well-versed in the world of microcontrollers like the popular ESP32, so I’m not entirely sure just how capable other operating systems and platforms built on top if it are. This particular operating system seems to make it rather easy and straightforward for anyone to build and distribute an application for such microcontrollers, to a point where even an idiot like myself could relatively easily buy, say, an ESP32 kit with a display and assemble my own collection of small applications.

To repeat myself, it simply looks neat.

Bradford Morgan White has published an excellent retrospective of QNX, the realtime microkernel operating system focused on embedded use cases. The final paragraph made me sad, though.

QNX is a fascinating operating system. It was extremely well designed from the start, and while it has been rewritten, the core ideas that allowed it survive for 45 years persist to this day. While I am sad that Photon was deprecated, the reasoning is sound. Most vendors using QNX either do not require a GUI, or they implement their own. For example, while Boston Dynamics uses QNX in their robots, they don’t really need Photon, and neither do SpaceX’s Falcon rockets. While cars certainly have displays, most vehicle makers desire their screen interfaces to have a unique look and feel. Of course, just stating these use cases of robots, rockets, and cars speaks to the incredible reliability and versatility of QNX. Better operating systems are possible, and QNX proves it.

↫ Bradford Morgan White at Abort Retry Fail

Way back in 2004, before I even joined OSNews properly, I wrote about QNX as a desktop operating system, because back then I went through a short stint where I used QNX and its amazing Photon MicroGUI as my primary desktop. Back then, there was a short-lived but very enthusiastic community using QNX on desktops, sharing tips and findings, supported by one or two QNX employees who tried their best to support this fledgling community in the face of corporate indifference.

Eventually, these QNX employees left the company, and QNX started making it clearer than ever that they were not, in any way, interested in people using QNX on desktops, and in all honesty, they were most likely correct. However, I still think we had something special there, and had QNX’ management decided to help us out, it could’ve grown into something more sustainable. An open source QNX and Photon could’ve had an impact.

Using QNX on the desktop back then was much easier than you might imagine, with graphical package managers, capable browsers and email clients, a massive pile of open source packages, pretty great performance, and little to no need to ever leave the GUI and use a CLI. If your hardware was properly supported, you could have a great experience.

One of the very small “what-ifs” form the early 2000s.

Can these months please stop passing us by this quickly? It seems we’re getting a monthly Redox update every other week now, and that’s not right. Anyway, what have the people behind this Rust-based operating system been up to this past month?

One of the biggest changes this month is that Redox is now multithreaded by default, at least on x86 machines. Unsurprisingly, this can enable some serious performance gains. Also contributing to performance improvements this month is inode data inlining for small files, and the installation is now a lot faster too. LZ4 compression has been added to Redox, saving storage space and improving performance.

As far as ports go, there’s a ton of new and improved ports, like OpenSSH, Nginx, PHP, Neovim, OpenSSL 3.x, and more. On top of that, there’s a long list of low-level kernel improvements, driver changes, and relibc improvements, changes to the main website, and so on.

Your lovely host, late last night:

Google claims they won’t be sharing developer information with governments, but we all know that’s a load of bullshit, made all the more relevant after whatever the fuck this was. If you want to oppose the genocide in Gaza or warn people of ICE raids, and want to create an Android application to coordinate such efforts, you probably should not, and stick to more anonymous organising tools.

↫ Thom Holwerda

Let’s check in with how that other walled garden Google is trying to emulate is doing.

Apple has removed ICEBlock, an app that allowed users to monitor and report the location of immigration enforcement officers, from the App Store.

“We created the App Store to be a safe and trusted place to discover apps,” Apple said in a statement to Business Insider. “Based on information we’ve received from law enforcement about the safety risks associated with ICEBlock, we have removed it and similar apps from the App Store.”

↫ Katherine Tangalakis-Lippert, Peter Kafka, and Kwan Wei Kevin Tan for Business Insider

Oh.

Apple and Google are but mere extensions of the state apparatus. Think twice about what device you bring with you the next time you wish to protest your government’s actions.

Google has been on a bit of a marketing blitz to try and counteract some of the negative feedback following its new developer verification requirement for Android applications, and while they’re using a lot of words, none of them seem to address the core concerns. It basically comes down to that they just don’t care about the consequences this new requirement has for projects like F-Droid, nor are they really bothered by any of the legitimate privacy concerns this whole thing raises.

If this new requirement is implemented in its current form, F-Droid will simply not be able to continue to exist in its current form. F-Droid builds the applications in its repository themselves and signs them, and developer verification does not fit into that picture at all. F-Droid works this way to ensure its applications are built from the publicly available sources, so developers can’t sneak anything nefarious into any binaries they would otherwise be submitting themselves.

The privacy angle doesn’t seem to bother Google much, either, which shouldn’t be a surprise to anyone. With this new requirement, Android application developers can simply no longer be anonymous, which has a variety of side-effects, not least of which is that anyone developing applications for, say, dissidents, can now no longer be anonymous. Google claims they won’t be sharing developer information with governments, but we all know that’s a load of bullshit, made all the more relevant after whatever the fuck this was. If you want to oppose the genocide in Gaza or warn people of ICE raids, and want to create an Android application to coordinate such efforts, you probably should not, and stick to more anonymous organising tools.

Students and hobbyists are getting the short end of the stick, too, as Google’s promised program specifically for these two groups is incredibly limited. Yes, it waves the $25 fee, but that’s about the only positive here:

Developers who register with Google as a student or hobbyist will face severe app distribution restrictions, namely a limit on the number of devices that can install their apps. To enforce this, any user wanting to install software from these developers must first retrieve a unique identifier from their device. The developer then has to input this identifier into the Android Developer Console to authorize that specific device for installation.

↫ Mishaal Rahman at Android Authority

Google does waive the requirement for developer certification for one particular type of user, and in doing so, highlights the only group of users Google truly cares about: enterprise users. Any application installed by an enterprise on managed devices will not need to have its developer certified. Google states that in this particular use case, the enterprise’s IT department is responsible for any security issues that may arise. Isn’t it funny how the only group of users who won’t have to deal with this nonsense are companies who pay Google tons of money for their enterprise tools?

The only way we’re going to get out of this is if any governments step up and put a stop to this. We can safely assume the United States’ government won’t be on our side – they’re too busy with their recurring idiotic song-and-dance anyway – so our only hope is the European Commission stepping in, but I’m not holding my breath. After all, Apple’s rules and regulations regarding installing applications outside of the App Store in the EU are not that different from what Google is going to do. While the EU is not happy with the details of Apple’s rules, their general gist seems to be okay with them.

I’m afraid governments won’t be stepping in to stop this one.

With Google closing up Android at a rapid pace, there’s some renewed interest in mobile platforms that aren’t either iOS or Android, and one of those is Ubuntu Touch. It’s been steadily improving over the years under the stewardship of the UBports Foundation, and today they released Ubuntu Touch 24.04-1.0.

Ubuntu Touch 24.04-1.0 is the first release of Ubuntu Touch which is based on Ubuntu 24.04 LTS, a major upgrade from Ubuntu 20.04. This might not be as big compared to our last upgrade from Ubuntu 16.04 to 20.04, but this still brings newer software stack to Ubuntu Touch (such as Qt 5.15).

↫ Ubuntu Touch 24.04-1.0 release announcement

In this release, aside from the upgrade to Ubuntu 24.04 LTS, there’s now also a light mode for the shell, including experimental support for switching themes on the fly. Applications already supported a light theme since the previous releases, so adding support for it in the main shell is a welcome improvement. We’ve also got experimental support for encrypting personal data, which needs to be enabled per device, which I think indicates not all devices support it. On top of that, there’s some changes to the phone application, and a slew of smaller fixes and improvements as well.

The list of supported devices has grown as well, with the Fairphone 5 as the newcomer this release. The list is still relatively small, but to be fair to the project, it includes a number of popular devices, as well as a few that are still readily available. If you want to opt for running Ubuntu Touch as your smartphone platform, there’s definitely plenty of devices to choose from.

Microsoft is reorganising the Windows teams. Again.

For those unaware, the Windows organization has essentially been split in two since 2018. Teams that work on the core of Windows were moved under Azure, and the rest of the Windows team (those that focused on top level features and user experiences) remained under the Windows org.

That is finally changing, with Davuluri saying that the Windows client and server teams are now going to operate under the same roof once again. “This change unifies Windows engineering work under a single organization … Moving the teams working on Windows client and server together into one organization brings focus to delivering against our priorities.”

↫ Zac Bowden at Windows Central

I mean, it’s obviously far too simplistic to attribute Windows’ many user-facing problems and failures on something as simple as this particular organisational split, but it sure does feel like it could be a contributing factor. It seems like the core of Windows is mostly fine and working pretty well, while the user experience is the ares that has suffered greatly in recent years, pressured as the Windows team seems to have been to add advertising, monetisation, tons of sometimes dangerous dark patterns, and more.

I hope that bringing these two teams back together will eventually lead to an overall improvement of the Windows user experience, and not a deterioration of the core of the platform. In other words, that the core team lifts up the user experience team, instead of the user experience team dragging the core team down. A Windows that takes its users seriously and respects them could be a fine operating system to use, but it reorganisations like this take a long time to have any measurable effect.

Of course, it could also just have no effect at all, or perhaps the rot has simply spread too far and wide. In a few years, depressing as it may seem, Windows 11 might be regarded as a highlight.

Have you ever heard of the Encore 91 computer system, developed and built by Encore Computer Corporation? I stumbled upon the name of this system on the website for the Macintosh like virtual window manager (MLVWM), an old X11 window manager designed to copy some of the look and feel of the classic Mac OS, and wanted to know more about it. An old website from what appears to be a reseller of the Encore 91 has a detailed description and sales pitch of the machine still online, and it’s a great read.

The hardware architecture of the Encore 91 series is based on the Motorola high-performance 88100 25MHz RISC processor. A basic system is a highly integrated fully symmetrical single board multiprocessor. The single board includes two or four 88100 processors with supporting cache memory, 16 megabytes of shared main memory, two synchronous SCSI ports, an Ethernet port, 4 asynchronous ports, real-time clocks, timers, interrupts and a VME-64 bus interface. The VME-64 bus provides full compatibility with VME plus enhancements for greater throughput. Shared main memory may be expanded to 272 megabytes (mb) by adding up to four expansion cards. The expansion memory boards have the same high-speed access characteristics as local memory.

↫ Encore computing 91 system

The Encore 91 ran a combination of AT&T’s system V.3.2 UNIX and Encore’s POSIX-compliant MicroMPX real-time kernel, and would be followed by machines with more powerful processors in the 88xxx series, as well as machines based on the Alpha architecture. The company also created and sold its own modified RISC architecture, RSX, for which there are still some details available online. Bits and bobs of the company were spun off and sold off, and I don’t think much of the original company is still around today.

Regardless, it’s an interesting system with an interesting history, but we’ll most likely never get to see oe in action – unless it turns up in some weird corner of the United States where the rare working examples of hardware like this invariably tends to end up.

The consequences of Google requiring developer certification to install Android applications, even outside of Google’s own Play Store, are starting to reverberate. F-Droid, probably the single most popular non-Google application repository for Android, has made it very clear that Google’s upcoming requirement is most likely going to mean the end of F-Droid.

If it were to be put into effect, the developer registration decree will end the F-Droid project and other free/open-source app distribution sources as we know them today, and the world will be deprived of the safety and security of the catalog of thousands of apps that can be trusted and verified by any and all. F-Droid’s myriad users will be left adrift, with no means to install — or even update their existing installed — applications.

↫ F-Droid’s blog post

A potential loss of F-Droid would be a huge blow to anyone trying to run Android without Google’s applications and frameworks installed on their device. It’s pretty clear that Google is doing whatever it can to utterly destroy the Android Open Source Project, something I’ve been arguing is what the rumours about Google killing AOSP really mean. Why kill AOSP, when you can just make it utterly unusable and completely barren?

Sadly, there isn’t much F-Droid can do. They’re proposing regulators the world over look at Google’s plans, and hopefully come to the conclusion that they’re anti-competitive. Specifically the European Union and the tools provided by the Digital Markets Act could prove useful here, but in the end, only if the will exists to use them can these tools be used in the first place.

It’s dark times for the smartphone world right now, especially if you care about consumer rights and open source. iOS has always been deeply anti-consumer, and while the European Union has managed to soften some of the rough edges, nothing much has changed there. Android, on the other hand, had a thriving open source, Google-free community, but decision by decision, Google is beating it into submission and killing it off. The Android of yesteryear doesn’t exist anymore, and it’s making people who used to work on Android back during the good old times extremely sad.

Jean-Baptiste Quéru, husband of OSNews’ amazing and legendary previous managing editor Eugenia Loli-Queru, worded it like this a few days ago:

All the tidbits of news about Android make me sad.

I used to be part of the Android team.

When I worked there, making the application ecosystem as open as the web was a goal. Releasing the Android source code as soon as something hit end-user devices was a goal. Being able to run your own build on actual consumer hardware was a goal.

For a while after I left, there continued to be some momentum behind what I had pushed for.

But, now, 12 years later, this seems to have all died.

I am sad…

↫ Jean-Baptiste Quéru

And so am I. Like any operating system, Android is far from perfect, but it was remarkable just how open it used to be. I guess good things just don’t survive once unbridled capitalism hits.

Some time ago, I described Windows 3.0’s WinHelp as “a program for browsing online help files.” But Windows 3.0 predated the Internet, and these help files were available even if the computer was not connected to any other network. How can it be “online”?

↫ Raymond Chen at The Old New Thing

I doubt this will be a conceptual problem for many people reading OSNews, but I can definitely understand especially younger people finding this a curious way of looking at the word “online”. You’ll see the concept of “online help” in quite a few systems from the ’90s (and possibly earlier), so if you’re into retrocomputing you might’ve run into it as well.

What if you have a PC-98 machine, and you want to run Linux on it, as you do? I mean, CP/M, OS/2, or Windows (2000 and older) might not cut it for you, after all. Well, it turns out that yes, you can run Linux on PC-98 hardware, and thanks to a bunch of work by Nina Kalinina – yes, the same person from a few days ago – there’s now more information gathered in a single place to get you started.

Plamo Linux is one of the few Linux distributions to support PC-98 series. Plamo 3.x is the latest distribution that can be installed on PC-9801 and PC-9821 directly. Unfortunately, it is quite old, and is missing lots of useful stuff.

This repo is to share a-ha moments and binaries for Plamo on PC-98.

↫ Plamo98 goodies

The repository details “upgrading” – it’s a bit more involved than plain upgrading, but it’s not hard – Plamo Linux from 3.x to 4, which gives you access to a bunch of things you might want, like GCC 3.3 over 2.95, KDE 3.x, Python 2.3, and more. There’s also custom BusyBox config files, a newer version of make, and a few other goodies and tools you might want to have. Once it’s all set and done, you can Linux like it’s 2003 on your PC-98.

The number of people to whom this is relevant must be extraorinarily small, but at some point, someone is going to want to do this, only to find this repository of existing work. We’ve all been there.

A few months ago, Microsoft finally blinked and provided a way for Windows 10 users to gain “free” access to the Windows 10 Extended Security Update program. For regular users to gain access to this program, their options are to either pay around $30, pay 1000 Microsoft points, or to sign up for the Windows Backup application to synchronise their settings to Microsoft’s computers (the “cloud”). In other words, in order to get “free” access to extended security updates for Windows 10 after the 25 October end-of-support deadline, you have to start using OneDrive, and will have to start paying for additional storage since the base 5GB of OneDrive storage won’t be enough for backups.

And we all know OneDrive is hell.

Thanks to the European Union’s Digital Markets Act, though, Microsoft has dropped the OneDrive requirement for users within the European Economic Area (the EU plus Norway, Iceland, and Liechtenstein). Citing the DMA, consumer rights organisations in the EU complained that Microsoft’s OneDrive requirement was in breach of EU law, and Microsoft has now given in. Of course, dropping the OneDrive requirement only applies to consumers in the EU/EEA; users in places with much weaker consumer protection legislation, like the United States, will not benefit from this move.

Consumer rights organisations are lauding Microsoft’s move, but they’re not entirely satisfied just yet. The main point of contention is that the access to the Extended Security Update program is only valid for one year, which they consider too short. In a letter, Euroconsumers, one of the consumer rights organisations, details this issue.

At the same time, several points from our original letter remain relevant. The ESU program is limited to one year, leaving devices that remain fully functional exposed to risk after October 13, 2026. Such a short-term measure falls short of what consumers can reasonably expect for a product that remains widely used and does not align with the spirit of the Digital Content Directive (DCD), nor the EU’s broader sustainable goals. Unlike previous operating system upgrades, which did not typically require new hardware, the move to Windows 11 does. This creates a huge additional burden for consumers, with some estimates suggesting that over 850 million active devices still rely on million Windows 10 and cannot be upgraded due to hardware requirements. By contrast, upgrades from Windows 7 or 8 to Windows 10 did not carry such limitations.

↫ Eurconsumer’s letter

According to the group, the problem is exacerbated by the fact that Microsoft is much more aggressive in phasing out support for Windows 10 than for previous versions of Windows. Windows 10 is being taken behind the shed four years after the launch of Windows 11, while Windows XP and Windows 7 enjoyed 7-8 years. With how many people are still using Windows 10, often with no way to upgrade but buying new hardware, it’s odd that Microsoft is trying to kill it so quickly.

In any event, we can chalk this up as another win for consumers in the European Union, with the Digital Markets Act once again creating better outcomes than in other regions of the world.

The contributions of Sun Microsystems to the world of computing are legion – definitely more than its ignominious absorption into Oracle implies – and one of those is NFS, the Network File system. This month, NFS more or less turned 40 years old, and in honour of this milestone, Russel Berg, Russ Cox, Steve Kleiman, Bob Lyon, Tom Lyon, Joseph Moran, Brian Pawlowski, David Rosenthal, Kate Stout, and Geoff Arnold created a website to honour NFS.

This website gathers material related to the Sun Microsystems Network File System, a project that began in 1983 and remains a fundamental technology for today’s distributed computer systems.

[…]

The core of the collection is design documents, white papers, engineering specifications, conference and journal papers, and standards material. However it also covers marketing materials, trade press, advertising, books, “swag”, and personal ephemera. We’re always looking for new contributions.

↫ NFS at 40

There’s so many amazing documents here, such as the collection of predecessors of NFS that served as inspiration for NFS, like the Cambridge File Server or the Xerox Alto’s Interim File System, but also tons of fun marketing material for things like NFS server accelerators and nerdy NFS buttons. Even if you’re not specifically interested in the history of NFS, there’s great joy in browsing these old documents and photos.