OSnews

Have a Samsung phone (outside of the United States), and want to unlock the bootloader? Well, soon you won't be able to do so anymore, as Samsung seems to be removing this option from their phones - including already sold models being upgraded to One UI 8. Bootloader unlocking is a popular way to breathe new life into older devices, by loading unofficial software onto a device, like custom ROMs, gaining root access, custom kernels, etc. This option will be taken away from users withOne UI 8. This means not only is the OEM Unlock not visible in Settings anymore, but the bootloader doesn't even contain any of the code required to unlock itself. This means a workaround to brute force it open is not possible at all, unless Samsung updates the bootloader to add this logic back in. Josh Skinner at SammyGuru And so, the ongoing process of locking down Android to a point where it becomes nigh-on indistinguishable from iOS' locked-down, anti-user nature continues unabated. Samsung is the default choice for Android users in a lot of places around the world, and seeing them, too move ever closer to fully locking down their phones is terrible news for consumers. We should be striving for less restrictive computing, not more. Combined with persistent rumours that Google is looking into effectively taking Android closed source, leaving only a stub AOSP behind, the future of Android as an least somewhat open" platform looks quite grim indeed.

Becoming friendlier to desktop users is one of the goals of the FreeBSD project at the moment, as we recently saw with the new ability to install a full KDE Plasma desktop environment during FreeBSD's initial installation. This is just one small piece of a larger effort, though, to improve, modernise, and possibly even replace the current FreeBSD installer entirely. As such, Pierre Pronchery, a Security Engineer for the FreeBSD Foundation and member of their team as a Userland Software Developer, published a blog post today with more information around this effort. The article goes into great detail to compare the installation procedures of other operating systems to that of FreeBSD, and the conclusion is that FreeBSD is lagging behind in quite a few areas. Among other shortcomings, the FreeBSD installer has no support for different languages, very little accessibility features, no niceties like progress bars or lists of steps, and most notably, no graphical mode. Some of these are already being addressed. The current FreeBSD installer (a combination of bsddialog, bsdconfig, and bsdinstall) consists of a number of shell scripts with some small C programs here and there, and the downside of this is that this is really only suitable for creating very basic steps and user interfaces. As an example, Pronchery mentions values during network setup, like network mask, DNS server or gateway, can't be prepopulated with the most likely values, which puts quite a burden on the user. This specific issue is being worked on by one of the original creators of bsddialog, and the solution they settled on is adding Lua scripting, which would give developers an avenue to fix some of these shortcomings. As far as a possible graphical installer goes, Pronchery looked at the various options out there, both from the Linux world and the few graphical installers that exist for a few desktop-oriented FreeBSD distributions, but for a variety of reasons, none of them proved to be particularly suitable for FreeBSD. As such, Pronchery created a quick proof-of-concept for a graphical installer by implementing bsddialog as a GTK+ application which he calls gbsddialog. It's important to note that this proof-of-concept is not suitable for FreeBSD, as GTK+ is licensed under the LGPL, but it does illustrate that by simply" reimplenting bsddialog using a graphical toolkit, you can get quite a long way to a usable FreeBSD installer that mimics the traditional installer quite well. The article covers a number of other topics, such as setting up a development environment to make it more straightforward and easier to work on the FreeBSD installer, as well as various steps that need to be taken to improve the accessibility of the installer. It concludes with a mention of the possibility of a complete rewrite of the installer, but such decisions are of course not made by a single person and require a lot more discussion and input. Regardless, the amount of work being done to improve FreeBSD for generic desktop use is exciting, as we need a viable, competitive alternative to that other open source desktop operating system.

This article will explain in details about the fundamental issues that held back accessibility in GNOME Calendar since the very beginning of its existence, the progress we have made with accessibility as well as our thought process in achieving it, and the now and future of accessibility in GNOME Calendar. Hari TheEvilSkeleton" Rana You'd think it would be easy to make a simple" calendar application properly accessible, but boy would you be wrong. In this article, Hari TheEvilSkeleton" Rana details just how much work had to be done in order to turn GNOME Calendar from entirely inaccessible into an accessible application, and considering the length of the article, you can see it wasn't a weekend effort. There were apparently two primary reasons why making GNOME Calendar accessible was so hard. First, maximising GNOME Calendar's performance optimisations had significant negative implications for accessibility, and two, the effectively endless flexibility a calendar needs to offer makes it very difficult to create a usable accessibility tree. Both the events on a calendar as well as the zooming view of a calendar lead to a ton of complexity in creating this tree. GNOME Calendar uses a ton of custom widgets, and these all needed specific, individual solutions to be made accessible. As an example, the article mentions that while it was possible to use the keyboard to create an event, it was not possible to use the keyboard to select created events. Obviously, even this one shortcoming alone effectively makes the entire application inaccessible to anyone relying solely on keyboard navigation. The article goes into great detail how both the above widget and countless other widgets were changed to make them accessible to both the keyboard and screen reader. If you're working on GTK applications, or even applications using other toolkits, Rana's article is a great resource to start to understand the complexities and creative thinking needed to implement accessibility in software properly.

You've seen them everywhere, especially on older computer equipment: the classic 9-pin serial connector. You probably know it as a DB9. It's an iconic connector for makers, engineers, and anyone who's ever used an RS232 serial device. Here's a little secret, though: calling it a DB9 is technically wrong. The correct name is actually DE9. Christo-boots with the-pher at Sparkfun Electronics I honestly had no idea, and looking through the Wikipedia page, it seems this isn't the only common misnomer when it comes to D-sub connectors.

Last year the European Union introduced legislation to greatly improve the transparency around political advertising, specifically on social media and websites. The law mandates a few very basic requirements that tend to already apply to many other forms of political advertising, like clearly labeling who paid for the ad and how much was spent, which election or referendum they're about, and which targeting techniques were used. In addition, data used for targeting may only be collected from the person being targeted, and the person targeted has to give explicit permission specifically for political advertising. Furthermore, a whole slew of data types are not allowed to be used, such as data that may reveal ethnic or racial origin or political opinions. Lastly, an obvious one: starting three months before an election of referendum, third country sponsorsare banned from advertising. It seems these rather basic, elementary requirements are too much for Facebook, as the company today announced it's going to stop offering political advertising in the European Union altogether in October of this year. The company cries on its blog: Despite extensive engagement with policymakers to share these concerns, we have been left with an impossible choice: alter our services to offer an advertising product which doesn't work for advertisers or users, without guarantee that our solution would be viewed as compliant, or stop allowing political, electoral and social issue ads in the EU. We'renot the only companyto have been forced into this position. Once again, we're seeing regulatory obligations effectively remove popular products and services from the market, reducing choice and competition. Sad Facebook As the link in Facebook's above lament points out, Google has also decided to stop offering political advertising in the European Union, for the exact same reasons. Facebook and Google are clearly trying to frame this as bad", but the only people the removal of hyper-targeted political advertising is bad for are threat actors trying to unduly and illegally influence elections, and of course, for the bottom line of Facebook and Google. Neither of these are of any relevance to the proper execution of fair and free elections, and people all across the European Union will be better off without these two advertising giants providing an easy avenue for shady organisations and foreign entities to unduly influence our elections. Basically, cry me a river Zuck. Nobody likes you.

TheLinux Terminal appthat Google introduced earlier this year is one of the most exciting new features in Android, not for what it currently does but for what it can potentially do. The Terminal app lets you boot up an instance of Debian in a virtual machine, allowing you to run full-fledged Linux apps that aren't available on Android. Unfortunately, the current version of the Terminal app is limited to running command line programs, but that's set to change in the near future. In the newAndroid Canarybuild that Google released today, the Terminal app now lets you run graphical Linux apps. Mishaal Rahman at Android Authority It comes with Weston, the reference implementation of a Wayland compositor, allowing you to run a basic graphical environment and accompanying applications. It won't be long before you can take your Pixel, connect a display, and run KDE. Neat, but so many devils are in so many details here, and there's so many places where this can fall apart entirely if the wrong decisions are made.

I have stumbled upon the most Microsoft support document of all time. Support for the Microsoft Store installation type of Microsoft 365 Apps is ending. New feature updates will stop in October 2025 and security updates will end in December 2026. If you have the Microsoft Store installation type of Microsoft 365 Apps, you must upgrade to the Click-to-Run installation type for continuing new features and security updates. The following steps show how you can upgrade the installation type of Microsoft 365 products on a PC from the Microsoft Store to Click-to-Run. End of support for the Microsoft Store installation type of Microsoft 365 Apps There is so much to unpack here. First, if you're not neck-deep in Microsoft lore, you might not even know what Microsoft 365 Apps even are. Remember Office 365, the subscription version of Microsoft Office? It's called Microsoft 365 now, for some inexplicable reason, but you probably haven't noticed because it is a stupidly confusing, nondescript name that nobody out in the real world uses. Adding to the confusion, in 2022, Microsoft announced it would phase out the Office name in favour of calling both the subscription version and the regular, buy-once-run-forever version Microsoft 365", but then changed their mind a year later, and as such, the regular, buy-once-run-forever version is now still called Office. Oh and there's also the Microsoft 365 Copilot app (formerly Office)" (at Office.com?) which I think is what used to be called the mobile iOS/Android Office application, which existed alongside the individual mobile Office applications on these platforms (because that was a thing, too - maybe still is?)? I don't know man, I merely have two university degrees, which clearly isn't enough to understand any of this 4D office suite chess. Anyway, the Microsoft 365 Apps (so the subscription version of what was temporarily formerly known as Microsoft Office) can be installed either through the Microsoft Store, which is the application store bundled with Windows that you never use, or through something called Click-to-Run. Apparently, Microsoft is discontinuing the Microsoft Store version of the Microsoft 365 Apps, and is urging everyone to move to the Click-to-Run version of the Microsoft 365 Apps. Alright, we're getting really, really deep into the very darkest crevices of the Microsoft Cinematic Universe lore now. The Microsoft Store version of the Microsoft 365 Apps is almost entirely identical to the Click-to-Run version of the Microsoft 365 Apps, except for one tiny part: the exact packaging method of the applications. Whereas the Microsoft Store version is packaged and delivered in Microsoft's Appx packaging format (designed for the Universal Windows Platform or UWP), the Click-to-Run version is packaged and delivered through, well, Click-to-Run. So, what is that, exactly? Click-to-Run is an entirely custom application streaming technology specifically designed for and exclusively used by Microsoft Office. You download a very small installer, which then proceeds to download the various Microsoft 365 applications like Word, Excel, and so on, which you can then start using well before the entire download is finished. The technology is similar to Microsoft App-V. It's actually remarkably difficult to find detailed documentation about Click-to-Run, which is odd considering Microsoft is usually quite decent at providing documentation for its technologies. So what Microsoft is announcing in this support document is that if you have Microsoft 365 Apps installed through the Microsoft Store, you're going to have to switch to the Click-to-Run version. You can check which installation type you're using by going to File>Account(it might be called Office Account, because everything is made up and nothing is real) - under Product information locate the About button, where it'll list the installation type. If your installation type is Microsoft Store, you need to switch to the Click-to-Run version to keep receiving updates. To do so, download the Click-to-Run installer and run it, which will automatically remove the Microsoft Store version of the Microsoft 365 Apps and replace them with the Click-to-Run versions. The reason they're making you do this is that the Click-to-Run version offers enterprises and corporate customers more control over deployment, update schedules, configuration options, and so on. The Microsoft Store version is more suited for normal consumers, but Microsoft doesn't care about those, and never has, and never will. Why is Microsoft?

Wayback, the recently announced tool that will allow you to run a legacy X11 desktop environment on top of Wayland, has just announced its first release, version 0.1. As the version number implies, there be dragons here, but the developers state some of them already use Wayback on a day-to-day basis. Still, there's no multi-monitor support yet, quite a few X.org options are just stubs for now, there's no mouse-locking, and so on. Since the initial announcement and the first progress report a few weeks ago, Wayback has become an official part of FreeDesktop.org, which indicates the wider desktop Linux community is definitely interested in what Wayback has to offer. It's also been split into several different parts to mimic X.org's structure, several distributions have picked it up and packaged it already, and ton more changes have been made. It definitely seems like Wayback has a good chance of becoming a simpler, more straightforward replacement for X.org, greatly reducing the maintenance burden of Linux distributions. Not having to keep the full legacy X.org stack around alongside Wayland is going to save a lot of people a lot of time.

The work towards making the 64bit version of AROS a viable choice is continuing, as is the work on AROS' web browser, and developer Krzysztof deadwood' miechowicz gave an update a few days ago detailing the progress that's been made - and it's extensive. First, the beta version of Odyssey 3.0, the web browser for AROS, can now load a whole slew of important websites, like YouTube, Google Docs, and Discord, which is a big deal for an alternative operating system like AROS. Odyssey uses Apple's WebKit as its browser engine, and it's obviously important to make sure it runs on the 64bit version of AROS. Speaking of 64bit, more and more applications are being recompiled to add 64bit support, with the stated goal being to have at least the best application in each category available in 64bit. A major issue is that certain pieces of hardware that work in 32bit do not yet work in 64bit. As a temporary solution, they're going to make use of the virtualisation route AROS Portable uses to plug the gaps in 64bit hardware support until such support is realised. AROS Portable is basically a Linux distribution that runs a virtual copy of the 32bit version of AROS. It's clear that a lot of work is happening in the 64bit space for AROS, which is crucial for the long-term viability of the project. AROS is still the easiest and most accessible way to get a taste of an Amiga-like experience since it runs on plain x86 hardware, so it's important to keep that dream alive.

One of the things lacking from the FreeBSD installation routine is the easy installation of a full desktop experience, from X11 all the way up to a login manager, desktop environment, and its applications. It seems this might finally change for FreeBSD 15.0, as the FreeBSD Foundation's Laptop Support and Usability Improvements project is working on adding support for this to bsdinstall, the FreeBSD installer. Based on a goal set out in this GitHub issue, the way this will work is that through a set of dialogs (which you can check out on GitLab) in the FreeBSD installer, the user can select to install KDE, which will then guide the user through installing the correct graphics driver and adding users to the video group. Once the installation is finished, the computer will reboot and load directly into SDDM, allowing you to log into the installed KDE Plasma desktop environment. For FreeBSD 15.0, our goal is to extend the FreeBSD installer to offer a minimal KDE-based desktop as an install option. The initial concept is a low-interaction installation process that, upon completion, brings the user directly to a KDE graphical login screen. FreeBSD Foundation Laptop Update - June 2025 Future plans for desktop users in the FreeBSD installers are more elaborate, and will include additional desktop environments to choose from, the ability to install sets of desktop applications during FreeBSD's installation, and yes, even opting for Wayland instead of X11, because FreeBSD developers know which way the wind is blowing. This is excellent news, and will make installing a FreeBSD-based desktop a lot easier for a ton of people. Work isn't fully completed just yet, but even if the developers miss their FreeBSD 15.0 target, it'll just move on to one of the follow-up releases.

Ever wanted Windows to monitor what's on your screen continuously and ask it to do stuff for you? Well, have I got news for you: Copilot Vision, as this feature is called, is now rolling out to users in the US. Copilot Vision on Windows, now available in the U.S., is a new way to engage with your Windows 11 PC. When you enable it, it can see what you see on your device and talk to you about it in real time. It acts as your second set of eyes, able to analyze content, help when you're lost, provide insights and answer your questions as you go. Whether you're browsing, working or deep in a project, Copilot Vision offers instant insights and answers. The Windows Experience Blog team Do note that Copilot Vision will not keep its data on your device, instead sending it off to Microsoft. So, if you ever wanted to give Microsoft even more insight into exactly what you're doing with your Windows installation, now's your chance. Well, if you're in the US, that is, and some its capabilities are only available on Snapdragon PCs, not on Intel or AMD machines. In the same blog post, Microsoft also highlights a few actually useful features coming to Windows, like a colour picker in the screenshot tool, the ability to change the lighting in photos, or having the area selector in the screenshot tool snap to what it thinks is the important part you wish to actually take a screenshot of. However, Microsoft is also adding nonsense like sticker generators in Paint, text generators in Word, and stuff related to Teams that makes me even happier than I already am that I'm self-employed and work alone. If you're in the US, you can get these features now if you wish through Windows Update.

Earlier this year, we talked about a peculiar oddity concerning Flatpaks and Fedora: unlike just about any other distribution, Fedora maintains its own Flatpak repository, while everyone else just defaults to Flathub. While there's a few technical differences between Fedora Flatpaks and Flathub Flatpaks, the main gist is that the Fedora ones are built using Fedora's own RPMs, while Flathub's are built using different means. This is an odd situation, since it does not reflect what users really want - users seem to greatly prefer Flatpaks from Flathub, since they have fewer bugs, are packaged by the applications' creators, and bugs in Flathub Flatpaks can be reported to the actual developers, whereas bugs in Fedora Flatpaks generally cannot. As such, Fedora users are often surprised to learn that the Flatpak they installed came from Fedora instead of Flathub. Now, since Fedora's long-term goal is to make their immutable, Flatpak-focused variants the default, this situation needs to be addressed. As such, Fedora and GNOME developer Michael Catanzaro has published an incredibly detailed article outlining all the issues and possible solutions and courses of action. The basic gist is that before Fedora can consider switching from its own Flatpak repository to Flathub, a number of shortcomings in Flathub must be addressed: Some of these points are fairly obvious, but let's go over them anyway. A lot of binaries on Flathub are pre-built in that they are not built using Flathub's infrastructure, and as such, you don't know if anything has been done to the code between, say, the code's release on GitHub and the Flatpak you install on your computer. This obviously needs to change, and ideally, all Flatpaks on Flathub should be reproducible. End-of-life runtimes should obviously also not be a thing, for entirely obvious reasons. Currently, a little under a third of applications on Flathub use end-of-life runtimes, meaning the runtimes they use are not receiving any security updates. The same applies to external dependencies packaged inside Flatpaks; they can be outdated too, but many Flatpaks do not use the designated tool to deal with this issue. Obviously, holes in the Flatpak sandbox should not exist either, again for entirely obvious reasons. Catanzaro proposes a number of solutions to all of these problems, which require work from both Fedora and Flathub to be implemented. On top of that, even once these issues are satisfactorily addressed, there's a debate to be had over the exact way in which both the traditional and immutable variants of Fedora move on over to Flathub - the variant I personally like the most is where the core applications installed by default remain in control of Fedora, while everything else gets installed from Flathub. Of course, this is not of much relevance to people who prefer plain, traditional RPMs - such as myself - to whom Flatpaks are more of a if all else fails" option than a default. While the immutable, Flatpak-based variants of Fedora are definitely on their way to become the default option, the traditional RPM variants will not be going anywhere, and will remain an option as well. I think defaulting new users to the immutable variants is the way to go, even if I personally won't be using them.

Microsoft wants to know why, exactly, Windows 11 is slow, so it's adding a feature in the latest Insider Preview to collect data when a Windows 11 machine is experiencing slowness or sluggishness. As part of our commitment to improving Windows performance, logs are now collected when your PC has experienced any slow or sluggish performance. Windows Insiders are encouraged to provide feedback when experiencing PC issues related to slow or sluggish performance, allowing Feedback Hub to automatically collect these logs, which will help us root cause issues faster. Use theDesktop > System Sluggishnesscategory when filing feedback to allow Feedback Hub to automatically pick up these logs. These logs are stored locally (%systemRoot%\Temp\DiagOutputDir\Whesvc folder) and only sent to Microsoft via Feedback Hub when feedback is submitted. Amanda Langowski and Brandon LeBlanc In case you want to solve performance problems with Windows 11, just go here and follow the steps, and your computer will be spry as a Spring chicken in a few minutes. I am very funny.

Is KDE too much for you? GNOME tries to do too much? Xfce still a bit too fancy? Do you need something smaller? Even more minimalist? What about a mere 20 lines of code which provide the absolute barest possible minimum of window management functionality? You need mwm. This is the smallest, actually usable window manager I know about. Even TinyWM is twice as large. However, it doesn't let you launch programs, or assign key bindings.mwmdoes. Mwm's GitHub page It will open a window, and let you switch between windows, that are always fullscreen. No titlebars, no virtual desktops, no menus, no nothing. This is the true minimalist's experience.

The Document Foundation, which developers LibreOffice, is mad at Microsoft for the levels of complexity in the Microsoft 365 document format. They claim Microsoft intentionally makes this format's XML schema as complex and obtuse as possible to lock users into the Microsoft Office ecosystem. This artificial complexity is characterised by a deeply nested tag structure with excessive abstraction, dozens or even hundreds of optional or overloaded elements, non-intuitive naming conventions, the widespread use of extension points and wildcards, the multiple import of namespaces and type hierarchies, and sparse or cryptic documentation. In the case of the Microsoft 365 document format, the only characteristic not present is sparse or cryptic documentation, given that we are talking about a set of documents totalling over 8,000 pages. All the other characteristics are present to a greater or lesser extent, making life almost impossible for a developer trying to implement the schema. Italo Vignoli I feel like this was widely known already, since I distinctly remember the discussions around the standardisation process for the Office Open XML file formats. Then, too, it was claimed that Microsoft's then-new XML file formats were far more complex and obtuse than the existing, already standardised OpenDocument file formats, and that there was no need to push Microsoft's new file formats through the process. These days, you might wonder how relevant all of this still is, but considering vast swaths of the private, corporate, government, and academic world still run on Microsoft Office and its default file formats, it's definitely still a hugely relevant matter. As an office suite, you are basically required to support Office Open XML, and if Microsoft is making that more complex and obtuse on purpose, that's a form of monopoly abuse that should be addressed.

The year before his death in 1994,Gary Kildall-inventorof the early microcomputer operating system CP/M-wrote a draft of a memoir, Computer Connections: People, Places, and Events in the Evolution of the Personal Computer Industry." He distributed copies to family and friends, but died before realizing his plans to release it as a book. This week, theComputer HistoryMuseum in Mountain View, with the permission of Kildall's children, released thefirst portion of that memoir. You can download ithere. Tekla S. Perry at IEEE Spectrum Invaluable writing, and I'm so glad it's getting published.

Why is my burgerblue?" I asked, innocently. Oh! We're making all of our foodblue, all the best restaurants are doing it now." the waiter explained. But I didn't want my burger to beblue. Luna Winters Blue" food isn't food.

In this blog post, I have described how I have been using Linux on my Amiga 4000. I hope this information can be of use to anyone who is planning to run Linux on their Amigas. Furthermore, I hope that the existing documentation on the Linux/m68k homepage gets updated at some point. May be the information in this blog post can help with that. Debian 3.1 works decently for me, but everything is much slower compared to a PC. This is not really surprising if you run an operating system (last updated in 2008) on a CPU from the early 90s that still runs at a 25 MHz clock speed :). Sander van der Burg The blog post in question is from January of this year, but as soon as I saw it I knew I had to post it here. It's an incredibly intricate and detailed guide to running Linux on a 25Mhz Amiga 4000, including X11, networking, internet access, file sharing, and so, so much more - up to running Linux for Amiga inside FS-UAE. There's so much love and dedication in this detailed guide, and I love it. In fact, Van den Burg has a similar article about running NetBSD on the Amiga 4000, with the same level of detail, dedication, and information density. A fun note is that while X11 for Linux on the Amiga can't seem to make use of the Amiga chipset, the X Window System on NetBSD does make us of it. I'm not surprised. Articles like these are useful only for a very small number of people, but having this amount of knowledge concentrated like this will prove invaluable like five years from now when someone else finds an Amiga 4000 in their attic or at a yard sale, and choose to go down this same path. We need more of these kinds of write-ups.

ISO 27001 is like that careful lawyer who never says exactly what they mean - it tells you what needs to be achieved, not how to do it. When it comes to logging, this is particularly telling: Control A.12.4.2 simply states that logging information and logging facilities shall be protected against tampering and unauthorized access." Period. How? That's your problem to solve. Rafael Sadowski It turns out OpenBSD has a few relatively simple tools to make logs immutable, in a way that not even root can delete or modify them, or change any of the logging schedules. Reading through the blog post, you don't even need a ton of intricate knowledge to set this up, thanks mostly to just how much innate sense OpenBSD tends to make, and how excellent the documentation is. I have no need for this level of security, but if you do, you can set this up in a few minutes.

With both Exchange 2016 and 2019going out of support in October 2025, we have heard from some of our customers that they have started their migrations to Exchange Subscription Edition (SE) but might need a few extra months of Security Updates (SU) for their Exchange 2016 / 2019 servers while they are finalizing their migrations. We are announcing that we now have a solution for such customers.Starting onAugust 1st, 2025, customers can contact their Microsoft account team to get information about and purchase an additional 6-month Extended Security Update (ESU) for their Exchange 2016 / 2019 servers.Your account teams will have information related to per server cost and additional details on how to purchase and receive ESUs, starting August 1st, 2025. The Exchange Team blog Microsoft is clearly in a place where a lot of their software released over the past ten years or so just kind of works, and people just don't feel as strong of a need to upgrade to newer versions, especially not if those newer versions come with complex subscriptions. It must be a strange position to be in for Microsoft.

Tilckis an educationalmonolithickernel designed to be Linux-compatible at binary level. It runs on i686 and RISCV64 at the moment. Project's small-scale and simple design makes it theperfect playgroundfor playing in kernel mode while retaining the ability to compare how thevery sameusermode bitsrun on the Linux kernel as well. That's arare featurein the realm of educational kernels. Because of that, building a program for Tilck requires just agcc-musltoolchain frombootlin.com. Tilck hasno needto have its own set of custom written applications, like most educational kernels do. It just runs mainstream Linux programs like theBusyBoxsuite. While the Linux-compatibility and the monolithic design might seem a limitation from the OS research point of view, on the other side, such design bring the whole project much closer toreal-worldapplications in the future, compared to the case where some serious (or huge) effort is required to port pre-existing software on it. Also, nothing stops Tilck from implementing custom non-Linux syscalls that aware apps might take advantage of. Tilck GitHub page Tilck implements about 100 Linux syscalls, and is not focused on replacing the Linux kernel or even becoming a generic desktop or server operating system. It supports both i686 and RISC-V, has support for FAT, and a whole slew of other features. It can run a number of console and even a few framebuffer applications, but don't expect things like X11 to work, or to ever work.

Do you have a Windows XP retro virtual machine or, god forbid, run Windows XP on your primary machine? You're going to need a sort-of up-to-date browser, and it turns out Mypal68 offers just that. Terrible name aside, it's Firefox 68 ported to and maintained to run on Windows XP SP3; SP2 and lower are not supported, but some people do seem to have some success getting it to run on those. There are issues, of course: there's a 1.5GB memory limit, and the browser will crash when it reaches that limit, and 64bit builds simpy don't work at all, so there's only a 32bit build. Version 74.1.0 was released a few days ago, but that version number doesn't actually mean the browser is now based on Firefox 74; they had to change the reported version number for extension compatibility. I'm currently setting up a dedicated Proxmox PC for retro virtual machines, and Windows XP will obviously be one of them. I'm definitely going to try this out.

When it comes to open hardware, choices are not exactly abundant. Truly open source hardware - open down to the firmware level of individual components - that also has acceptable performance is rare, with one of the few options being the Talos II and Blackbird POWER9 workstations from Raptor Computing Systems (which I reviewed). Another option that can be fully open source with the right configuration are the laptops made by MNT, which use the ARM architecture (which I also reviewed). Both of these are excellent options, but they do come with downsides; the Talos II/Blackbird are expensive and getting a bit long in the tooth (and a possible replacement is at least a year away), and the MNT Reform and Pocket Reform simply aren't for everyone due to their unique and opinionated design. Using an architecture other than x86 also simply isn't an option for a lot of people, ruling out POWER9 and ARM hardware entirely. In the x86 world, it's effectively impossible to avoid proprietary firmware blobs, but there are companies out there trying to build x86 laptops that try to at least minimise the reliance on such unwelcome blobs. One of these companies is NovaCustom, a Dutch laptop (and now desktop!) OEM that sells x86 computers that come with Dasharo open firmware (based on coreboot) and a strong focus on privacy, open source, customisability, and repairability. NovaCustom sent over a fully configured NovaCustom V54 laptop, so let's dive into what it's like to configure and use an x86 laptop with Dasharo open firmware and a ton of unique customisation options. Hardware configuration I opted for the 14'' laptop model, the V54, since the 16'' V65 is just too large for my taste. NovaCustom offers a choice between a 1920*1200 60Hz and a 2880*1800 120Hz panel, and I unsurprisingly chose the latter. This higher-DPI panel strikes a perfect balance between having a 4K panel, which takes a lot more processing power to drive, and a basic 1080p panel, which I find unacceptable on anything larger than 9'' or so. The refresh rate of 120Hz is also a must on any modern display, as anything lower looks choppy to my eyes (I'm used to 1440p/280Hz on my gaming PC, and 4K/160Hz on my workstation - I'm spoiled). The display also gets plenty bright, but disappointingly, the V54 does not offer a touch option. I don't miss it, but I know it's a popular feature, so be advised. While the V54 can be equipped with a dedicated mobile RTX 4060 or 4070 GPU, I have no need for such graphical power in a laptop, so I stuck with the integrated Intel Arc GPU. Note that if you do go for the dedicated GPU, you'll lose the second M.2 slot, and the laptop will gain some weight and thickness. I did opt for the more powerful CPU option with the Intel Intel Core Ultra 7 155H, which packs 6 performance cores (with hyperthreading), 8 efficiency cores, and 2 low-power cores, for a total of 16 cores and 22 threads maxing out at 4.8Ghz. Unless you intend to do GPU-intensive work, this combination is stupid fast and ridiculously powerful. Throw in the 32GB of DDR5 5600MHz RAM in a dual-channel configuration (2*16, replaceable) and a speedy 7.400 MB/s (read)/6.500 MB/s (write) 1TB SSD, and I sometimes feel like this is the sort of opulence Marie Antoinette would indulge herself in if she were alive today. It won't surprise you to learn that with this configuration, you won't be experiencing any slowdowns, stuttering, or other performance issues. Ports-wise, the V54 has a USB-C port (3.2 Gen 2), a Thunderbolt 4 port (with Display Alt Mode supportingDP 2.1), a USB-A port (3.2 Gen 2) and a barrel power jack on the right side, a combo audio jack, USB-A port (3.2 Gen 1), microSD card slot, and a Kensington lock on the left, and an Ethernet and HDMI port on the back. Especially the Ethernet port is such a welcome affordance in this day and age, and we'll get back to it since we need it for Dasharo. The trackpad is large, smooth, and pleasant to use - for a diving board type trackpad, that is. More and more manufacturers are adopting the Apple-style haptic trackpads, which I greatly prefer, but I suspect there might be some patent and IP shenanigans going on that explain why uptake of those in the PC space hasn't exactly been universal. If you're coming from a diving board trackpad, you'll love this one. If you're coming from a haptic trackpad, it's a bit of a step down. A standout on the V54 is the keyboard. The keys are perfectly spaced, have excellent travel, a satisfying, silent click, and they are very stable. It's an absolute joy to type on, and about as good as a laptop keyboard can be. On top of that, at least when you opt for the US-international keyboard layout like I do, you get a keyboard that actually properly lists the variety of special characters on its keys. This may look chaotic and messy to people who don't need to use those special characters, but as someone who does, this is such a breath of fresh air compared to all those modern, minimalist keyboards where you end up randomly mashing key combinations to find that one special character you need. Considering my native Dutch uses diacritics, and my wife's native Swedish uses the extra letters a, a, and o (they're letters!), this is such a great touch. The keyboard also has an additional layer for a numeric pad, as well as the usual set of function keys you need on a modern laptop, including a key that will max out the fan speed in case you need it (the little fan glyph on my keyboard seems double-printed, though, which is a small demerit). I especially like the angry moon glyph on the sleep key. He's my grumpy friend and I love him. Of course, the

Did you know KDE has a television-focused user interface? It's been languishing for a while now, but a recent week-long effort by KDE developer Devin has brought a lot of new life into the project. I have been a long timePlasma Mobilecontributor, but I have always had a keen interest in having Linux on my TV! I have noticed that in the past few months, thePlasma Bigscreenproject has had some interest from people wanting to contribute, but there have not been any active KDE developers working on the project. Since I have some time off school (having just graduated university), I decided to take a swing at improving the project for a week. Devin, KDE developer It turned out to be one hell of a productive week, because the list of improvements achieved in that one week is kind of amazing. Lots of overhauls of the visual design, a new search view, complete redesign of the settings panels, and a lot more. The idea of running a KDE Plasma-based interface on my TVs sounds incredibly appealing, and I hope the project can make even more progress.

Haiku also survived another month of development, so it's time for another roundup of what they've been doing. Considering it's the height of Summer, it's no surprise the list of changes is a bit shorter, consisting mostly of smaller bugfixes and minor improvements. A few standout changes are that cursors can now be properly scaled in HiDPI, the iprowifi3945 driver from FreeBSD has been replaced by the OpenBSD one because it performs better, and several improvements to how colour schemes work. waddlesplash refactored how control edge (borders, etc.) colors are computed inside HaikuControlLook (the class that renders UI controls under the default appearance), cleaning up a lot of convoluted computations. He also fixed some color handling in the progress bar control, and then along with nephele, refactored how control colors are used and computed across the system. The Control background" color in Appearance preferences now has a new default and is much more properly used across the Interface Kit; under the default colors, renderings should be basically the same as before, but for users on dark mode" or other custom color schemes, it will now be much easier to pick control colors. waddlesplash on the Haiku website There's more, of course, so be sure to read the whole thing.

Late last year, Mishaal Rahman reported that Google was going to merge ChromeOS and Android, and it seems Google itself has now confirmed that's exactly what's happening. I asked because we're going to be combining ChromeOS and Android into a single platform, and I am very interested in how people are using their laptops these days and what they're getting done," Samat explained. Lance Ulanoff at TechRadar I'm definitely interested to see what using Android across desktops, laptops, tablets, martphones, and smartwatches is going to be like. The same applications on all those form factors? So many have tried, and as many have failed. I just don't think Google has what it takes.

The latest alpha of the upcoming Blender 5.0 release comes withHigh Dynamic Range (HDR) support for Linux on Waylandwhich will, if everything works out, make it into the final Blender 5.0 release on October 1, 2025. The post on the developer forum comes with instructions on how to enable the experimental support and how to test it. If you are using Fedora Workstation 42, which ships GNOME version 48, everything is already included to run Blender with HDR. All that is required is an HDR compatible display and graphics driver, and turning on HDR in the Display Settings. Sebastian Wick It's interesting to note that Blender on Windows won't be getting HDR support, and that's because Windows' HDR support is subpar compared to Wayland on Linux, and requires a ton more work which the Blender team isn't going to do. It seems the Wayland developers made all the right choices when it comes to HDR support. Needless to say, X11 doesn't have HDR support. The design of the Wayland color-management protocol, and the resulting active color-management paradigm of Wayland compositors was a good choice, making it easy for developers to do the right thing, while also giving them more control if they so chose. Sebastian Wick Weird. I was told Wayland was an unusable mess.

Tribblix, the illumos distribution that aims to provide a retro feel with modern components, has just released a new update, Milestone 37. At the system level, the max PID is now 99999, so you may see larger PIDs. Usernames exceeding 8 characters are now accepted without warnings. Files with dates after the Y2038 transition are now permitted on ZFS. Notable default version updates: the default Java is now JDK21, postgres is now v17, go is now v1.24, and ruby is v3.4. Tribblix Milestone 37 release notes See the full list of changes for all the various updated components.

On Windows, there's an option to show the seconds on the taskbar clock, but it comes with a warning that it might reduce battery life if you switch it on. LTT Labs decided to look into this to see just how much of a thing this really is, and they concluded that yes, it does actually affect battery life. They saw a drop of about 5%-15%, depending on configuration. In percentage terms, the drops weren't massive. For most people, it probably won't make or break your day. But if you're on a long flight, running low on battery, or trying to squeeze out every last bit of endurance, it's not entirely nothing either. Woolly Door at LTT Labs I mean, having the second tick away on the click would drive me up the wall when I'm trying to use my computer, but I'm sure quite a few among you do enable the seconds display on your own setups (Windows or otherwise). I'm curious to see if the same battery life reduction is measurable on KDE, GNOME, or macOS.

What if you want to use Wayland, but prefer Window Maker, which is restricted to legacy X11? Enter wlmaker, or Wayland Maker, a Wayland compositor that reproduces the look and feel of Window Maker. It's lightweight, very configurable through human-readable configuration files, supports dockable applications, and more. It's actually packaged in FreeBSD and a number of Linux distributions, including Ubuntu and Debian (Fedora's package is outdated), but of course, you can compile it yourself, too.

In recent weeks and months, you may have noticed that when accessing some websites, you see a little progress bar and a character, performing some sort of check. You've most likely encountered Anubis, a tool to distinguish real human browser users from AI" content crawlers that are causing real damage and harm. It turns out Anubis is quite effective at what it does, but it did come with a limitation: it required JavaScript to be enabled. Well, no more. One of the first issues in Anubis before it was moved to theTecharoHQ orgwas a requestto support challenging browsers without using JavaScript. This is a pretty challenging thing to do without rethinking how Anubis works from a fundamentally low level, and with v1.20.0,Anubis finally has support for running without client-side JavaScriptthanks to theMeta Refreshchallenge. Xe Iaso Before this new non-JS challenge, users who disabled client-side JavaScript or browsers which don't support JavaScript were straight-up blocked from passing Anubis' test, meaning they couldn't access the website Anubis was protecting from AI" scraper abuse. This is now no longer the case.

I'm hardly a networking" or system admin expert. Even still, I've always been interested in the concept of building out my own home router with OpenBSD. It seemed so hacky" and cool! The problem is that most of the tutorials I stumble across on the internet seem sodaunting. I normally read through the guides (maybe even poke around the coremandocs for a bit as well) but always end up returning to my default ISP setup. But that all changes today! Best of all, you can come along for the ride! Bradley Taunt Exactly what it says on the tin.

It's become almost impossible to avoid the AI" evangelists spreading the gospel of how AI" tools are helping them work faster and get more stuff done in less time, but do any of those claims have any basis in reality? Should we really be firing countless people and replace them with AI" tools? Should we spend god knows how much money on AI" tools and force employees to use them? Well... When developers are allowed to use AI tools, they take 19% longer to complete issues-a significant slowdown that goes against developer beliefs and expert forecasts. This gap between perception and reality is striking: developers expected AI to speed them up by 24%, and even after experiencing the slowdown, they still believed AI had sped them up by 20%. Joel Becker, Nate Rush, Beth Barnes, and David Rein We're very much in the early days of proper research into the actual effectiveness and real-world benefits of AI" tools for all kinds of professions, so a study like this definitely isn't a smoking gun, but it does fly in the face of the tech companies and their evangelists shoving AI" down our collective throat. With how much these tools get even the most basic stuff wrong, with how often they lie and make stuff up, I just can't imagine them speeding up as many tasks as people claim they do. At the same time, AI" tools do definitely have a place for very specific tasks, and I think that studies like these will look different for every single profession and even every single task within a profession. It's going to be incredibly hard or even impossible to come to a theory of everything" on the effectiveness and usefulness of AI" tools. It won't be until this idiotic hype dies down before we can have a grounded, honest, fact-based discussion about which AI" tools make sense where.

James Heppell, representing Open Web Advocacy, published an article detailing his experience attending DMA compliance workshop in Brussels, in which members of the public can ask questions of companies who have products designated as gatekeepers under the DMA. After attending the Apple one, he concludes: As a final thought, I called this article Apple Vs The Law" primarily in reference to the rule of law, about how it should be applied equally and fairly against all, no matter the size and influence of your company. I think some of these gatekeepers - above all Apple, do a lot to undermine this process, in some places genuinely damaging trust in democracy. Going out of their way to paint the DMA law and the EU as overstepping and extreme hurts its reputation, as does the invented rhetoric about it being the great risk to privacy ever imposed to government" (China?), or that they're acting without experts in the field". Similarly for the number of covertly funded and supported lobbying groups that they bring to regulators all around the world. And the constant pressure from the US administration to not enforce the DMA - helped in no small part by these gatekeepers. These money-driven practices - which in many ways mirror the propaganda typically produced by authoritarian regimes like Russia, seriously hurt all democracies that they come in to touch with, and is a kind of behaviour that should make Apple, and any other group involved, ashamed of themselves. James Heppell Sometimes I wonder if us Europeans wouldn't simply be better off without these lying, scheming, law-breaking American technology companies. Yes, there's be a bit of a shock and a chaotic scrambling as newcomers fill the void, but I think I'd prefer that over the illegal behaviours that are clearly endemic in US technology companies. As a EU citizen, I'm not even afforded 0.01% of the kind of silk glove, patient, and cooing treatment these corporations get when they break the law, and it highlights once more just how tiered justice really is. I think the EU would, in the long term, be better off without the likes of Apple, Google, Microsoft, Amazon, and Facebook routinely and repeatedly breaking our laws. Rip that festering, rotting band-aid off and endure the chaos for a few years while European newcomers fill the void in a beautiful explosion of competition and innovation. Do we really want to be tied to these corporations that clearly despise us?

There's quite a few ways to mess around with home automation, with the most popular communication methods being things like ZigBee, plain Wi-Fi, and so on. One of the more promising new technologies is Thread, and Dennis Schubert decided to try and use it for a new homebrew project he was working on. After diving into the legalese of the matter, though, he discovered that Thread is a complete non-starter due to excessive mandatory membership fees without any exceptions for non-commercial use. To summarize: if you're a hobbyist without access to some serious throwaway money to join the Thread Group, there is no way to use Thread legally - the license does not include an exception for non-commercial uses. If you're like me and want to write a series of blog posts about how Thread works, there's also no legal way. A commercial membership program for technology stacks like Thread isn't new; it's somewhat common in that space. Same with requiring certifications for your commercial products if you want to use a logo like the Works with Thread" banner. And that's fine with me. If you're selling a commercial electronics product, you have to go through many certification processes anyway, so that seems fair. But having a blanket ban on implementations, even for non-commercial projects, is absolutely bonkers. This means that no hobbyist should ever get close to it, and that means that the next generation of electrical engineers and decision-makers don't get to play around with the tech before they enter the industry. But of course, that doesn't really matter to the Thread Group:their members listincludes companies like Apple, Google, Amazon, Nordic, NXP, and Qualcomm - they can justforceThread into being successful by making sure it's shipped in the most popular home hubs". So it's just us that get screwed over. Anyway, if you planned to look at Thread... well, don't. You're not allowed to use it. Dennis Schubert So you can buy Thread dev kits to create your own devices at home, but even such non-commercial use is not allowed. The situation would be even more complex for anyone trying to sell a small batch of fun devices using Thread, because they'd first have to fork over the exorbitant yearly membership fee. What this means is that Thread is a complete non-starter for anyone but an established name, which is probably exactly why the big names are pushing it so hard. They want to control our home automation just as much as everything else, and it seems like Thread is their foot in the door. Be advised.

To better support you and provide earlier, more consistent access to in-development features, we are announcing a significant evolution in our pre-release program. Moving forward, the Android platform will have aCanary release channel, which will replace the previous developer preview program. This Canary release channel will function alongside the existing beta program. This change is designed to provide a more streamlined and continuous opportunity for you to try out new platform capabilities and provide feedback throughout the entire year, not just in the early months of a new release cycle. Dan Galpin on the Android Developers Blog This new Canary channel is intended for developers, and you can expect a ton of bugs and breaking changes. Updates are basically streamed continuously over the air, but not all changes will make it to a final release of Android (as in, they can be pulled definitively). You can join the new channel with any supported Pixel device, but going back to a beta or final release will require a full wipe.

The year is 2013 and I amhopping mad. systemdis replacing my plaintext logs with a binary format and pumping steroids intoinitand it islaughingat me. The unix philosophy cries out: is this the end of Linux (or, as many are calling it, GNU plus Linux)? The year is 2025 and I'm here to repent. Not only issystemda worthy successor to traditionalinit, but I think that it deserves a defense for what it's done for the landscape - especially given the hostile reception it initially received (and somehow continues to receive? for some reason?). No software is perfect - except forTempleOS- but I think that systemd has largely been a success story and proven many dire forecasts wrong (including my own). I was wrong! Tyler Langlois The article goes into detail on a number of awesome features, niceties, and clever things systemd has, and they're legion. Even as a mere user, I like systemd, as every time I have had to or wanted to interact with it, it's been a joy to use, with excellent documentation making it remarkably easy even for someone like me to get into it without doing any damage or breaking anything. Every time I read up on system'd more advanced features, I'm surprised by how well thought out and implemented it all seems to be. I've experienced several major leaps forward in the Linux world that made using Linux on my computers easier and more reliable, and the adoption of systemd stands among them as one of the biggest leaps forward desktop Linux has ever made. The idea of going back to a random piles of non-standardized init scripts with nebulous dependencies from varying sources and wildly different levels of quality seems like a complete nightmare to me. There's a lot of charm in doing things the old way', and I'm not saying you're wrong for wanting an init system that tries to do less, or that's easier to read and parse for you, or whatever, but that doesn't mean systemd is bad, evil, or part of a Red Hat conspiracy to kill Linux.

In Chrome, Skia is used to render paint commands from Blink and the browser UI into pixels on your screen, a process called rasterization. Skia has powered Chrome Graphicssince the very beginning. Skia eventually ran into performance issues as the web evolved and became more complex, which led Chrome and Skia to invest in a GPU accelerated rasterization backend called Ganesh. Over the years, Ganesh matured into a solid highly performant rasterization backend and GPU rasterization launched on all platforms in Chrome on top of GL (via ANGLE on Windows D3D9/11). However, Ganesh always had a GL-centric design with too many specialized code paths and the team was hitting a wall when trying to implement optimizations that took advantage of modern graphics APIs in a principled manner. This set the stage for the team to rethink GPU rasterization from the ground up in the form of a new rasterization backend, Graphite. Graphite was developed from the start to be principled by having fewer and more comprehensible code paths. This forward looking design helps take advantage of modern graphics APIs like Metal, Vulkan and D3D12 and paradigms like compute based path rasterization, and is multithreaded by default. Michael Ludwig and Sunny Sachanandani at the Chromium Blog The level of complexity in browsers and their rendering engines blows my mind every time I read about it. When I first got access to the internet, it consisted of static pages with text and still images, but now browser engines are almost as complex as entire operating systems. Not all of that progress has been good - boy has a lot of it not been good - but we're stuck with it now, and thus people making browsers have to deal with stuff like this. If you ever wonder why there really only are two browser engines in the world - Google's Blink and Apple's WebKit - this is your answer. Who in their right mind wants to develop something like this from scratch and compete with Google and Apple?

GlobalFoundries today announced a definitive agreement to acquire MIPS, a leading supplier of AI and processor IP. This strategic acquisition will expand GF's portfolio of customizable IP offerings, allowing it to further differentiate its process technologies with IP and software capabilities. Press release about the acquisition MIPS has a long and storied history, most recently as it abandoned its namesake instruction set architecture in favour of RISC-V. MIPS processors are still found in a ton of devices though, but usually not in high-profile devices like smartphones or whatever. Their new RISC-V cores haven't yet seen a lot of uptake, but that's a problem all across the RISC-V ecosystem.

Ah, Power. The architecture that has so much going for it, but despite concerted efforts from very dedicated people, IBM seems to be hellbent on preventing anyone from expanding Power beyond expensive enterprise servers. We had Raptor Computing Systems achieving some niche success with their POWER9 workstations - I have two, and reviewed one of them - but that's about it. When IBM moved to Power10, the new processors required closed-source, proprietary firmware in a few areas of the design, which made them unsuitable for Raptor to develop a successor to the Talos II and Blackbird POWER9 workstations. I admire Raptor for sticking firmly to their convictions of only producing fully open source hardware, down to the firmware level. The requirement for proprietary firmware was never addressed by IBM during the Power10 lifecycle, so Raptor obviously never jumped aboard the IBM Power10 train, and as far as I can tell, neither did anyone else. As such, the only Power10 hardware we have comes from IBM, and the offering consist entirely of enterprise servers, which are unsuitable and unaffordable for home use, whether as server or workstation. Raptor did make a joint announcement with Solid Silicon, with rumours suggesting Solid Silicon was working on a Power10-based chip that didn't require any proprietary firmware, but that was late 2023, and it's been silence ever since. But Power10 is old news now, since IBM just officially launched Power11. IBM made the date official: Power11 launchesJuly 25, with the 32 AI-coreSpyre Acceleratorexpected to follow in the fourth quarter. IBM's launch products will be the full-rack Power E1180 with up to up to 256 SMT-8 Power11 cores with 2MB L2 each and up to 128GB of shared L3 (8GB per core) with 64TB of DDR5 memory, the midrange 4U Power E1150 with up to 120 Power11 cores and 16TB of DDR5, the junior 4U Power S1124 with up to 60 Power11 cores and 8TB of DDR5, and the low-end" 2U Power S1122 with up to 60 Power11 cores and 4TB of DDR5. The processors come in 16, 24 or 30-core versions; the E systems have four sockets (with up to four nodes in the E1180) and the S systems have two. All four systems can run AIX and Linux, and all systems except for the E1150 can run IBM i. As is usual for IBM's initial offerings, internally they look like straight-up implementations of the Blueridge reference platform and should be expected to scale accordingly. And if you have to ask how much they are, well... Cameron Kaiser Sadly, there's no word on whether or not IBM's Power11 processors still require proprietary firmware, so it's impossible to tell if they will show up in any possible Raptor workstations. There's also zero indication of anyone else joining the fray, and IBM itself obviously isn't going to focus on end-user workstations because the world is bleak and joyless. That being said, we've got some solid rumours from Cameron Kaiser, who is generally well-informed on these topics. I have been advised by an anonymous individual with knowledge of the situation that a new Raptor announcement on products under development is scheduled for Q1 2026 ... which would be six to twelve months after" as predicted. Open firmware" is specifically mentioned and absolutely planned. It's worth pointing out thatbothRaptor and SolidSilicon are now listed as top-tierPlatinum members for OpenPOWERparallel with IBM itself. That implies SolidSilicon is still in the mix and IBM is still backing OpenPOWER. They stressed this is not an official announcement, so you take it for what it's worth. Cameron Kaiser It's something, but not much. I would love to be able to upgrade the POWER9 machines in my office to something newer, even if they perform quite well to this day. I simply have a soft spot for Power, and I want the ISA to succeed beyond enterprise servers. The architecture has what it takes to do so, but IBM seems to have zero interest in making it happen, making life quite hard for anyone else in the ecosystem trying their hardest. All we're asking for is a single or dual socket Power11 workstation in a nice case, IBM. Just flip one of those servers 90, disable the enterprise stuff, and optionally ship it with AIX. It won't bite. I promise.

Alpine Linux maintainer Ariadne Conill only started working on Wayback a few weeks ago, but in a blog post today they dive into a few more details about how much progress has already been achieved. To refresh your memory, Wayback allows you to run a legacy X11-based desktop environment on top of Wayland by running a stub Wayland compositor in front of Xwayland, capable of serving as a full X server. This way, the transition to Wayland and the removal of X.org from popular distributions won't mean you can't run X11-based desktop environments anymore. Within just a few weeks, the project has made serious progress. There's a lot still left to do before we can confidently say that Wayback is ready for distributions to switch to. This work is across the stack: Wayback still needs to expose surfaces that Xwayland can use, Xwayland needs to implement a few new features such as cursor warping and some X extensions inside Xwayland itself need to be properly plumbed (such as Xinerama being able to make use of the Wayland output layout data). Longer term goals aside, we are at most a few weeks away from the first alpha-quality release of Wayback. The main focus of this release is to get to a point where enough is working that users with basic setups and requirements can be reasonably served by Wayback in place of the X.org server, to allow for further testing. It's already to a point where I am daily driving it. Ariadne Conill Of course, there's still tons of bugs to figure out and missing functionality to implement, but the fact that they're just weeks away from a first alpha release is honestly impressive. I really hope Wayback picks up even more and gets adopted by other distributions as well, since it's such an elegant and future-proof solution to a very real problem. It's important that desktop environments that will not or cannot transition to Wayland remain available to Linux users regardless of their choice of Wayland or X11. When facing the slow sunsetting of a windowing system, some people go off on deranged neofascist conspiracy rants against the woke illuminati, while others sit down and develop real forward-looking solutions. I'm glad virtually every Linux distribution that matters trusts the latter over the former.

As of today, Stat Counter reports that Windows 11 now has 50.88% of the Windows market, with Windows 10 dropping to 46.2%, giving it a comfortable lead over its predecessor. Windows 11 has been on the market since 2021 but had only amassed less than 10% of the market by 2022. It's been a slow but steady climb since then, growing from 18% to 28% in 2023, with similar growth to 36% in 2024. It's this year where Windows 11 really started taking off, likely aided by the fact that Microsoft is now pushingWindows 10's end of supporthard. Zac Bowden at Windows Central Up to 50% of all Windows users, mere months before Windows 10 is no longer supported, and it took them 4 years to get here. Windows users really don't like Windows 11, do they?

The developers of Legacy Update, the tool that allows users of older Windows versions to keep downloading updates from Microsoft, recently discovered that users of the tool on Windows 7 were having issues. After doing some debugging they figured out it was DNS it was an expired Microsoft certificate. This certificate was set to expire on 1 July 2025, and when it did, nobody at Microsoft bothered to correct it until a few days later. As you can see from<ExpiryDate>, it definitely stopped working because the expiry date lapsed. As seems to happen too often in our industry, apparently nobody set a reminder to make sure it would be updated in advance of the date. You might notice that it has an <IssuedDate> of 2017-12-01. That's fairly recent! After digging further, we learned thatthis already happened once!On the 4th of that month,Bleeping Computer coveredan error Windows 7 users were receiving when checking for updates. That error is80248015- pretty familiar, right? Microsoft allowed this file to expire, not on the 1st but rather on the 4th (more specifically, 35 seconds before midnight in US Pacific time, or 8:00 PM UTC), and did not manage to upload a new file until the 6th at 10:02 AM Pacific (6:02 PM UTC). This left Microsoft Update broken for 3 days. Adam Demasi Microsoft moved the expiry date up to 2033, thereby fixing the problem. Legacy Update's developer Adam Demasi expected that once 2033 comes around, Legacy Update will probably have to add Widnows 7 to its proxy server that it's already using for older versions, as improvements in TLS and ciphers will probably lock Windows 7 out of Windows Update definitively. But hey, 2033 is decades away. Right?

WinUAE has released version 6.0.0 of the Windows version of the UAE Amiga emulator, packing a truly terrifying number of changes, improvements, and fixes. Major update to custom chipset emulation. Internally almost everything in main chipset emulation has been rewritten. Fastest possible/JIT mode chipset timing/sync had major changes which can cause side-effects. Bugs are very possible, especially in very rarely used features. WinUAE website Going through the changelog is dizzying, ranging from an almost complete rewrite of the main chipset emulation for internal cycle accuracy, to running the emulation of the Denise/Lisa chips in a separate thread for better performance, to a ton of fixes and smaller updates.

With macOS 26, Apple has announced a dramatically new look to their UI: Liquid Glass. Solid material icon elements give way to softer, shinier, glassier icons. The rounded rectangle became slightly more rounded, and Apple eliminated the ability for icon elements to extend beyond the icon rectangle (as seen in the current icons for GarageBand, Photo Booth, Dictionary, etc.). With this release being one of the most dramatic visual overhauls of macOS's design, I wanted to begin a collection chronicling the evolution of the system icons over the years. I've been rolling these out on social media over the past week and will continue to add to and update this collection slowly over the summer. Enjoy! BasicAppleGuy Every single one of these icons is getting progressively worse with almost every design change. They go from beautifully crafted, easily readable and supremely distinguishable icons to generic, repetitive blobs of colour, void of any personality, artistry, or usability considerations. Also, Apple's new icon design language makes the icons look fuzzy, like they're not being rendered properly. It's very unnerving. The one exception is probably the generic folder icon, which looks fine in all of its incarnations. Then there's the classic Platinum, pixelated version from Mac OS 9 and earlier, which, together with icons from Windows and BeOS from the same time period, are a whole different style that I don't think most people would accept anymore these days, but that I absolutely adore. Mostly I'm just sad that the craft of making exquisite icons for operating systems is dying, replaced by what almost look like AI" generated blobs of indeterminate meaning, that rely more on preexisting knowledge of the operating system and its applications in question than on being recognisable and decipherable by anyone. I truly hope Windows and the various open source desktops don't follow in Apple's footsteps here.

A couple of days ago, Microsoft announced9,000 layoffs across its global workforce, impacting its engineering, Xbox, sales, and management teams. This move also affected various initiatives, resulting in thecancellation of at least three Xbox games, job cuts across various studios, and even the shuttering of one game studio, The Initiative. In the wake of this dark day in the the tech industry, a tone-deaf Microsoft executive urged laid off workers to turn to AI tools for emotional support. Usama Jawad at Neowin These corporations are raking in massive amounts of profit, they're doing better than ever, the cup of money runneth over, and yet, they keep laying off thousands and thousands of people almost every few months. The incentives in modern-day capitalism clearly aren't working out for the vast majority of people, and then to give that final kick when you're already down, some asshat manager tells you to talk to" sparkly autocomplete for emotional support. Fuck this guy.

Since the disastrous launch of the RTX 50 series, NVIDIA has been unable to escape negative headlines: scalper bots are snatching GPUs away from consumers before official sales even begin, power connectors continue to melt, with no fix in sight, marketing is becoming increasingly deceptive, GPUs are missing processing units when they leave the factory, and the drivers, for which NVIDIA has always been praised, are currently falling apart. And to top it all off, NVIDIA is becoming increasingly insistent that media push a certain narrative when reporting on their hardware. Sebin Nyshkim Out of all the issues listed here - and there are many, and each is bad enough on their own - it's the frame generation and related pressure campaigns on reviewers that really get on my nerves the most. Technologies like DLSS (rendering at a lower internal resolution scaling that up) and frame generation (injecting fake AI" frames to jack up the frame rate) can be fine technologies when used at the consumer's discretion to find a balance between improved perceived performance in exchange for blurry image quality and artefacting, but we've now reached a point where NVIDIA will only boast about performance figures with these technologies enabled, downsides be damned. If that wasn't misleading enough, the company is also pressuring reviewers who don't enable these technologies, and focus on real frames, real resolutions, and this, real performance. If you don't comply, you're not getting the next crop of GPUs in early access. It's the kind of shit Apple pulls all the time, and we need less of it, not more. Just don't buy NVIDIA. They're already a terrible choice if you're running anything other than Windows, but the company's recent behaviour and serious missteps have made the choice for AMD or Intel only more obvious.

Redox continues to make progress, and as another month has passed us by, it's time for another monthly update. This past month, the focus has been on UNIX domain sockets, which are needed for Redox' goal of running Wayland. As we continue to move forward with our plans for Wayland, a key technology for Wayland support is the ability to send file descriptors over Unix Domain Sockets. File descriptor sending is also an important part of many other OS features, including Capability-based Security. Our Redox Summer of Code project to implement that ability has been progressing very well. Ibuki, a new member of the Redox team, has jumped right into the deep end, and implemented thesendmgandrecvmsgfunctionality, and continues to move forward with work on UDS. Ribbon and Ron Williams You can read more about the UNIX domain sockets progress in a detailed post on the Redox website. Redox now also supports network booting through PXE, but for now, only UEFI is supported. Of course, all of this work is topped off with the usual slew of fixes in relibc, RedoxFS, various drivers, and more, as well updated ports across the board.

All of this to say: value is complicated. The Pi 5 ismuchmore compact and slightly more power efficient (especially at idle) compared to the cheapest N1XX Intel systems. The Intel systems are better suited for a desktop use case. The Pi 5 can be run off PoE power, for easier one-cable networking + power. The Intel systems are more compatible with a wider range of software (not the least of which isanything requiring Windows). Jeff Geerling Intel's N100 and N150 are vastly underappreciated. The mini laptop I reviewed over a year ago is built around the N100, and I still use it every day for watching YouTube, writing OSNews posts, and so on. I never run into performance issues, battery life is excellent, and I don't have to deal with the annoyances of using ARM. The catch is that you're going to want to use Linux - I use Fedora KDE - because Windows' performance on the N100 is dreadful. I don't think the jump from the N100 to the N150 is worthwhile enough to buy the new version of my mini laptop, so I'll stick with what I have. I do hope Intel continues the Nxxx line or processors, because it offers something no other x86 chip offers: more than reasonable performance at low power usage for an incredibly low price.

A recent bug report filed against Ubuntu's upgrading tool confirmed a major change with regards to the RISC-V requirements for the upcoming Ubuntu 25.10 release - most existing RISC-V devices willnotbe able to run Ubuntu 25.10. How come? Joey Sneddon at omgubuntu.co.uk RISC-V just isn't delivering. That's the cold and harsh truth more and more people are having to deal with, such as Chimera Linux dropping RISC-V support because the ecosystem is simply lacking the kind of powerful and available hardware to sustain itself (Chimera got lucky, though, and gained access to a Milk-V Pioneer through Adelie Linux). The number of systems and boards that are both powerful and available is close enough to zero that it might as well be zero, and if neither users nor developers can buy RISC-V hardware, what's the point in supporting it? The issue for Ubuntu specifically is that version 25.10 of the distribution intends to target only the RVA23 baseline RISC-V profile, while currently Ubuntu supports RVA20 as the baseline. This higher baseline profile requires a number of extensions to the instruction set that no existing hardware yet supports, making 25.10 effectively a clean break for all existing RISC-V hardware. In other words, if you're running Ubuntu on RISC-V hardware today, you won't be able to upgrade to 25.10 or higher. RISC-V really needs vastly improved hardware availability, because right now it's just not delivering on the years of promises.