OSnews

As part of our vision for simplified Windows management from the cloud, Microsoft has announceddeprecation of Windows Server Update Services (WSUS). Specifically, this means that we are no longer investing in new capabilities, nor are we accepting new feature requests for WSUS. However, we are preserving current functionality and will continue to publish updates through the WSUS channel. We will also support any content already published through the WSUS channel. Nir Froimovici What an odd feature to deprecate. Anyone with a large enough fleet of machines probably makes use of Windows Server Update Services, as it adds some much-needed centralised control to the downloading and deployment of Windows updates, so you can do localised partial rollouts for testing, which, as the CrowdStrike debacle showed us once more, is quite important. WSUS also happens to be a local tool, that is set up and run locally, instead of in the cloud, and that's where we get to the real reason WSUS is being deprecated. Microsoft is advising IT managers who use WSUS to switch to Microsoft's alternatives, likeWindows Autopatch,Microsoft Intune,andAzure Update Manager. These all happen to run in the cloud, giving up that control WSUS provided by running locally, and they're not free either - they're subscription services, of course. I mean, technically WSUS isn't free either as it's part of Windows Server, but these cloud services come on top of the cost of Windows Server itself. Nobody escapes the relentless march of subscription costs.

Thewidely-reportedfoo is requesting to bypass the system private window picker and directly access your screen and audio" prompt in Sequoia (which Apple has moved fromdailytoweeklyto nowmonthly)can be disabledby quitting the app, setting the system date far into the future, opening and using the affected app to trigger the nag, clicking Allow For One Month", then restoring the correct date. tinyapps.org blog Or, and this is a bit of a radical idea, you could use an operating system that doesn't infantalise its users.

On Friday afternoon,The Wall Street JournalreportedIntel had been approached by fellow chip giant Qualcomm about a possible takeover. While any deal is described as far from certain," according to the paper's unnamed sources, it would represent a tremendous fall for a company that had been the most valuable chip company in the world, based largely on its x86 processor technology that for years had triumphed over Qualcomm's Arm chips outside of the phone space. Richard Lawler and Sean Hollister at The Verge Either Qualcomm is only interested in buying certain parts of Intel's business, or we're dealing with someone trying to mess with stock prices for personal gain. The idea of Qualcomm acquiring Intel seems entirely outlandish to me, and that's not even taking into account that regulators will probably have a thing or two to say about this. The one thing such a crazy deal would have going for it is that it would create a pretty strong and powerful all-American chip giant, which is a PR avenue the companies might explore if this is really serious. One of the most valuable assets Intel has is the x86 architecture and the associated patents and licensing deals, and the immense market power that comes with those. Perhaps Qualcomm is interested in designing x86 chips, or, more likely, perhaps they're interested in all that sweet, sweet licensing money they could extract by allowing more companies to design and sell x86 processors. The x86 market currently consists almost exclusively of Intel and AMD, a situation which may be leaving a lot of licensing money on the table. Pondering aside, I highly doubt this is anything other than an overblown, misinterpreted story.

Can you run Linux on the Intel 4004, the first commercially produced microprocessor, released to the world in 1971? Well, Dmitry Grinberg, the genius engineer who got Linux to run on all kinds of incredibly underpowered hardware, sought to answer this very important question. In short, yes, you can run Linux on the 4004, but much as with other extremely limited and barebones chips, you have to get... Creative. Very creative. Of course, Linux cannot and will not boot on a 4004 directly. There is no C compiler targeting the 4004, nor could one be created due to the limitations of the architecture. The amount of ROM and RAM that is addressable is also simply too low. So,same as before, I would have to resort to emulation. My initial goal was to fit into 4KB of code, as that is what an unmodified unassisted 4004 can address. 4KB of code is not much at all to emulate a complete system. After studying the options, it became clear that MIPS R3000 would be the winner here. Every other architecture I considered would be harder to emulate in some way. Some architectures had arbitrarily-shifted operands all the time (ARM), some have shitty addressing modes necessitating that they would be slow (RISCV), some would need more than 4KB to even decode instructions (x86), and some were just too complex to emulate in so little space (PPC). ... so ...MIPS again... OK! Dmitry Grinberg This is just one very small aspect of this massive undertaking, and the article and videos accompanying his success are incredibly detailed and definitely not for the faint of heart. The amount of skill, knowledge, creativity, and persistence on display here is stunning, and many of us can only dream of being able to do stuff like this. I absolutely love it. Of course, the Linux kernel had to be slimmed down considerably, as a lot of stuff currently in the kernel are of absolutely no use on such an old system. Boot time is measured in days, still, but it helped a lot. Grinberg also turned the whole setup into what is effectively an art piece you can hang on the wall, where you can have it run and, well, do things - not much, of course, but he did include a small program that draws mandelbrot set on the VFD and serial port, which is a neat trick. He plans on offering the whole thing as a kit, but a lot of it depends on getting enough of the old chips to offer a complete, ready-to-assemble kit in the first place.

The iPhone 16 family has arrived and includes many new features, some of which Apple has played very close to its vest. One such improvement is the inclusion of JPEG XL file types, which promise improved image quality compared to standard JPEG files while delivering relatively smaller file sizes. Overall, JPEG XL addresses many of JPEG's shortcomings. The 30-year-old format is not very efficient, only offers eight-bit color depth, doesn't support HDR, doesn't do alpha transparency, doesn't support animations, doesn't support multiple layers, includes compression artifacts, and exhibits banding and visual noise. JPEG XL tackles these issues, and unlike WebP and AVIF formats, which each have some noteworthy benefits too, JPEG XL has been built from the ground up with still images in mind. Jeremy Gray at PetaPixel Excellent news, and it will hopefully mean others will follow - something that tends to happen when Apple finally supports to the new thing.

Nintendo, together with The Pokemon Company, filed a patent infringement lawsuit in the Tokyo District Court against Pocketpair, Inc. on September 18, 2024. This lawsuit seeks an injunction against infringement and compensation for damages on the grounds thatPalworld, a game developed and released by the Defendant, infringes multiple patent rights. Nintendo press release Since the release of Palworld, which bears a striking resemblance to the Pokemon franchise, everybody's been kind of expecting a reaction from both Nintendo and The Pokemon Company, and here it is. What's odd is that it's not a trademark, trade dress, or copyright lawsuit, but a patent one, which is not what you'd expect when looking at how similar the Palworld creatures look to Pokemon, to the point where some people even suggest the 3D models were simply lifted wholesale from the latest Nintendo Switch Pokemon games. There's no mention of which patents Pocketpair supposedly infringes upon, and in a statement, the company claims it, too, has no idea which patents are supposedly in play. I have to admit I never even stopped to think game patents were a thing at all, but now that I spent more than 2 seconds pondering this concept, of course they exist. This lawsuit will be quite interesting to follow, because the games industry is one of the few technology sectors out there where copying each others ideas, concepts, mechanics, and styles is not only normal, it's entirely expected and encouraged. New ideas spread through the games industry like wildfires, and if some new mechanic is a hit with players, it'll be integrated into other games within a few months, and games coming out a year later are expected to have the hit new mechanics from last year. It's a great example of how beneficial it is to have ideas freely spread, and how awesome it is to see great games take existing mechanics and apply interesting twists, or use them in entirely different genres than where they originated from. Demon's Souls and the Dark Souls series are a great example of a series of games that not only established a whole new genre other games quickly capitalised on, but also introduced the gaming world to a whole slew of new and unique mechanics that are now being applied in all kinds of new and interesting ways. Lawsuits like this one definitely pose a threat to this, so I hope that either this fails spectacularly in court, or that the patents in question are so weirdly specific as to be utterly without merit in going after any other game.

As we look to the future, maintaining a proprietary IR format (even one based on an open-source project) is counter to our commitments to open technologies, so Shader Model 7.0 will adopt SPIR-V as its interchange format. Over the next few years, we will be working to define a SPIR-V environment for Direct3D, and a set of SPIR-V extensions to support all of Direct3D's current and future shader programming features through SPIR-V. This will allow developers to take better advantage of existing tools and unify the ecosystem around investing in one IR. Chris Bieneman and Cassie Hoef at the DirectX Developer Blog SPIR-V is developed by the Khronos Group and is anintermediate languageforparallel computingand graphics byKhronos Group". I don't know what any of this means, but any adoption of Khronos technologies is a good thing, especially by a heavyweight like Microsoft.

The European Commission has taken the next step in forcing Apple to comply with the Digital Markets Act. The EC has started two so-called specification proceedings, in which they can more or less order Apple exactly what it needs to do to comply with the DMA - in this case covering the interoperability obligation set out in Article 6(7) of the DMA. The two proceedings entail the following: Thefirstproceedingfocuses on severaliOS connectivity features and functionalities, predominantly used for and by connected devices.Connected devices are a varied, large and commercially important group of products, including smartwatches, headphones and virtual reality headsets. Companies offering these products depend oneffective interoperability with smartphones and their operating systems, such as iOS. The Commission intends to specify how Apple will provide effective interoperability with functionalities such as notifications, device pairing and connectivity. Thesecond proceedingfocuses on theprocess Apple has set up to address interoperability requestssubmitted by developers and third parties for iOS and IPadOS. It is crucial thatthe request process is transparent, timely, and fairso that all developers have an effective and predictable path to interoperability and are enabled to innovate. European Commission press release It seems the European Commission is running out of patience, and in lieu of waiting on Apple to comply with the DMA on its own, is going to tell Apple exactly what it must do to comply with the interoperability obligation. This means that, once again, Apple's childish, whiny approach to DMA compliance is backfiring spectacularly, with the company no longer having the opportunity to influence and control its own interoperability measures - the EC is simply going to tell them what they must do. The EC will complete these proceedings within six months, and will provide Apple with its preliminary findings which will explain what is expected of Apple. These findings will also be made public to invite comments from third parties. The proceedings are unrelated to any fines for non-compliance, which are separate.

The GNOME project has released their newest major version, GNOME 47, and while it's not the most groundbreaking release, there's still a ton of good stuff in here. Two features really stand our, with the first one being the addition of accent colours. Instead of being locked into the default GNOME blue accent colour, you can now choose between a variety of colours, which is a very welcome addition. I use the accent colour feature on all my computers, and since I run KDE, I also have this nifty KDE feature where it'll select an accent colour automatically based on your wallpaper. No, this isn't a groundbreaking feature, but considering GNOME's tendency towards not allowing any customisation, this is simply very welcome. A much more substantial feature comes in the form of brand new open/save file dialogs, and I'm sure even the GNOME developers themselves are collectively sighing in relief about this one. GNOME's open/save dialogs were so bad they became a meme, and now they're finally well and truly fixed, thanks to effectively removing the old ones and adding new ones based on the GNOME Files file manager. GNOME 47 comes with brand new file open and save file dialogs. The new dialogs are a major upgrade compared with the previous versions, and are based on the existing Files app rather than being a separate codebase. This results in the new dialogs having a much more complete set of features compared with the old open and save dialogs. With the new dialogs you can zoom the view, change the sort order in the icon view, rename files and folders, preview files, and more. GNOME 47 release notes And yes, this includes thumbnails. There's tons more in GNOME 47, like a new design for dialog windows that look and feel more like they belong on a mobile UI, tons of improvements to Files, the Settings application, GNOME Online Accounts, Web, and more. GNOME 47 will make its way to your distribution of choice soon enough, but of course, you can always build and install it yourself if you're so inclined.

Intel's woes are far from over. Pat Gelsinger, the company's CEO, has announced that Intel's chipmaking business will be spun off and turned into a separate company. A subsidiary structure will unlock important benefits. It provides our external foundry customers and suppliers with clearer separation and independence from the rest of Intel. Importantly, it also gives us future flexibility to evaluate independent sources of funding and optimize the capital structure of each business to maximize growth and shareholder value creation. There is no change to our Intel Foundry leadership team, which continues to report to me. We will also establish an operating board that includes independent directors to govern the subsidiary. This supports our continued focus on driving greater transparency, optimization and accountability across the business. Pat Gelsinger This is a big move, and illustrated the difficulties Intel is facing. Its foundry business lost $7 billion last year, and it's cutting 15% of its workforce - 15000 people - indicating it needs to do something to turn the ship around. Intel is also pausing construction on two additional plants in Europe, but will continue its expansion efforts in the United States. Bitter note is that Intel received a massive cash injection from the US Biden administration, yet then proceeds to fire 15000 people. Socialism for the rich, capitalism for the poor.

FreeBSD 13.4 has been released. This is already the fifth release in the FreeBSD 13 series, and contains the usual set of security fixes, driver updates, important updated packages, like openssh, LLVM, clang, and so on. If you're running FreeBSD 13, you already know how to upgrade, and if you want to start using FreeBSD 13, here's the download page.

Are you developing a game for Windows, and are you working on input handling? At first, it could reasonably be assumed that mouse and keyboard should be the simplest parts of this to deal with, but in reality, they are not - at least if we are talking about Windows. In fact,several extremely popular AAA games ship with severe mouse input issues when specific high-end mice are used, and some popular engines have issues that are still extant. In this article we'll explore a few reasons why that is the case, and end up with a solution that works but is still unsatisfactory. I assume that there is a whole other level of complexity involved in properly dealing with accessories like steering wheels, flight sticks, and so on in simulators, but so far I never had the pleasure of working on a game that required this, and this article will not cover those types of input devices. Peter Durante' Thoman So, what is the problem? Basically, there are two ways to handle mouse input in Windows: if you use batched raw input processing, which is pretty much a requirement, you need to also choose whether or not to keep legacy input enabled. If you keep it enabled, the legacy input will add so much junk to your message queue it can negatively impact the performance of your game quite harshly. If you disable it, however, something really fun happens: you can no longer move the game window... Because the Windows UI uses legacy input. Thoman has a solution that he and his company uses, and he considers it an ugly hack, but they just don't know of a better way to solve this issue. Thoman keeps legacy input enabled, but just limits the number of message queue events per frame that are being processed (they limit it to 5). As far as they can tell, this doesn't seem to have any negative side effects, but it's clearly a bit of an ugly hack that shouldn't be necessary. I found this a rather interesting niche topic, and I wonder how many people have struggled with this before, and what kind of other solutions exist.

We all know about the Desktop Publishing revolution that the first Macs and their PostScript LaserWriter printers brought in the late 1980s, but many have now forgotten the Desktop Video revolution that followed in the next decade. At its heart was support for multimedia in Apple's QuickTime. QuickTime isn't a single piece of software, or even an API in Classic Mac OS, but a whole architecture to support almost any media format you could conceive of. It defines container and file formats for multiple media types, forming the basis for the MPEG-4 standard, extensible encoding and decoding of a wide variety of media using Codecs, and more. Howard Oakley As a Windows users before I switched to the Mac somewhere in 2003 or 2004 or so, I mostly associated QuickTime with an annoying piece of crapware I sometimes had to install to watch videos, despite my Windows installation being perfectly capable of playing a whole slew of video codecs just fine. To make matters worse, Apple eventually started forcing Windows users to also install their auto-update tool that ran in the background, which would occasionally just... Install stuff without your permission. Of course, QuickTime was a whole lot more than that, especially on the Mac, where it was simply a core technology of the Mac operating system and the name of the built-in video player. It also served as underpinnings for a whole slew of related technologies, from movie editors like iMovie to the QuickTime streaming tools included in Mac OS X Server, so odds are that somehow, somewhere, you've used QuickTime in your life time. I'm not entirely ashamed to admit I had to check if QuickTime was still part of macOS today - I haven't actively used macOS since, I think, the Snow Leopard days in 2009 - but it obviously has been sunset quite a while ago in favour of AVFoundation, which macOS still uses today.

Last week, Julio Merino published an article I wish someone had written ages ago: a fair, unbiased look at the differences between Windows NT in its original form and UNIX roughly at the time of the initial releases of Windows NT. Merino, who has a long career in tech and has made contributions to several operating systems, does a great job cutting through the fanboyism and decades' worth of conventional wisdom, arriving at the following conclusion that I think many of us here will share even without diving into the great depth of his article. NT was groundbreaking technology when it launched. As I presented above, many of the features we take for granted today in systems design were present in NT since its inception, whereas almost all other Unix systems had to gain those features slowly over time. As a result, such features don't always integrate seamlessly with Unix philosophies. Today, however, it's not clear to me that NT is truly more advanced" than, say, Linux or FreeBSD. It is true that NT had more solid design principles at the onset and more features that its contemporary operating systems, but nowadays... the differences are blurry. Yes, NT is advanced, but not significantly more so than modern Unixes. What I find disappointing is that, even though NT has all these solid design principles in place... bloat in the UI doesn't let the design shine through. The sluggishness of the OS even on super-powerful machines ispainful to witnessand might even lead to the demise of this OS. Julio Merino You should definitely read the whole thing, and not just the conclusion, as it will give you some great insight into some of the differences between the two approaches, and how the UNIX and Windows NT worlds learned from each other and grew together. It's well-written, easy to read, and contains a ton of information and details about especially Windows NT most people are probably not aware of. Reading through the article helped my crystallise a set of thoughts I've been having about the future of Windows, and in particular, the future of Windows NT as a short-hand for the kernel, lower-level frameworks, and everything else below the graphical layer. I think there's a major change coming to Windows NT, something so big and unheard of it's going to be the most defining moment in Windows NT history since its very first release. There's a few facts that lie at the root of my conclusion. First, ever since the very beginning, Windows NT has been developed in roughly the same way: behind closed doors by a group of specialists inside Microsoft, and every now and then we got a massive dump of new code in the form of a major Windows release. It's only recently that Microsoft has started taking a more rolling release approach to Windows development, with smaller updates peppered throughout the year, with different release branches users can subscribe to. Second, despite many of us almost equating Microsoft with Windows - or perhaps with Windows and Office - the reality of it is that Windows hasn't been the primary driver for revenue for Microsoft for a while now. In Microsoft's fiscal year of 2023, Windows made up just 10% of the company's total revenue that year, which amounts to $22 billion out of a total revenue of $211 billion. Azure alone is almost four times as large at $80 billion, and even LinkedIn - yes, LinkedIn - is good for $15 billion in revenue, making Windows only about a third more profitable than the most soulless social network in human history. Third, despite Windows' decreasing revenue share, the operating system is becoming ever larger in scope. Not only does it need to cover the literally infinite possible combinations of x86 hardware in both the desktop/laptop and server space, it now also needs to cover what is surely going to be a growing market for ARM hardware, starting with laptops, but surely expanding to desktops and servers, too. Microsoft needs to foot the bill for all of this development, and for how much longer can the company justify spending an inordinate amount of money on a massive army of Windows developers, when the revenue they bring in is such a small part of the company, and a part that's decreasing every year, to boot? Fourth, the competition Windows faces is surprisingly strong. Not only are macOS, Chrome OS, and even the Linux desktop doing better than ever, mobile computing is also competing with Windows, and that's a space Microsoft is simply not present in at all. This is especially pressing in the developing world, where often people's first and only computing experience is mobile - through Android, mostly - and Microsoft and Windows simply don't play any role. Given these facts, there's only one reasonable course of action for Microsoft. I think the company is going to address all of these issues by releasing large parts of Windows NT as open source. I base this on a gut feeling bourne out of the above facts, and not on any form of insider information, and there is a 99.9% chance that I am wholly, completely, and utterly wrong. Still, deep down, I feel like releasing Windows as open source makes the most sense considering the challenges the operating system and its parent company are facing. You and I are going to witness Windows NT's source code being published as open source on GitHub by Microsoft within 5-7 years, accompanied by an open governance model wherein contributions are welcomed and encouraged. Even if such a step will not be taken by Microsoft, I am convinced that, in the future, when today's employees and executives write and publish their memoirs, it will contain a lot of discourse on the very serious consideration that took place within the company in the past to do so. You can quote me on this. And then laugh at me when it inevitable turns out I'm wrong.

It's Apple operating system release day, so if you're in the Apple ecosystem, it's like Christmas morning, but for your devices. The two major platforms are, of course, iOS/iPadOS 18: iOS 18 adds new customization options for theHome Screen, with the option to arrange apps and widgets with open spaces and add new tints to app icons. Control Center has been entirely overhauled with support for multiple pages, third-party controls, and the option to put controls on the Lock Screen and activate them with the Action Button. Juli Clover at MacRumors And macOS 15: macOS Sequoia featuresiPhoneMirroring, which allows you to control and monitor your iPhone right from your Mac. You can use your iPhone's apps and get your iPhone's notifications all while your iPhone is tucked away and locked. Window tiling has been improved to make it easier to arrange multiple windows on your Mac's display, and there are new keyboard and menu shortcuts for organizing your windows. In Safari, Highlights will now show you the information you want most from websites, and there's a new Viewer mode for watching videos without distractions. Juli Clover at MacRumors It doesn't stop there, though, as Apple also released watchOS 11, visionOS 2, tvOS 18, and the most import ant most hotly anticipated out of all of Apple's platforms, HomePod Software 18. It's genuinely kind of staggering how Apple manages to update all of these various platforms at the same time, each coming with a ton of new features and bugfixes, and ship them out to consumers - generally without any major issues or showstoppers. Especially in the case of iOS and macOS, that's definitely a major difference with the Windows and Android worlds, where users are confronted with strict hardware requirements, lack of update availability altogether, or just stick with previous versions because the new versions contain tons of privacy or feature regressions. Do note that Apple's AI/ML features announced during WWDC aren't shipping yet, and that iPhone Mirroring is not available in the EU because someone told Tim Cook no" and he threw a hissy fit.

It's one of the most pervasive common wisdoms shared all over the web, no matter where you go - it's one of those things everybody seems to universally agree on: Chrome will absolutely devastate your battery life on the Mac, and you should really be using Safari, because Apple's special integration magic pixie dust sprinkles ensures Safari sips instead of gulps electricity. Whether you read random forum posters, Apple PR spokespeople, or Apple's own executives on stage during events, this wisdom is hard to escape. Is it true, though? Well, Matt Birchler decided to do something entirely revolutionary and entirely unheard of: a benchmark. Back in the olden days of yore, we would run benchmarks to test the claims from companies and their PR departments, and Birchler decided to dust off this old technique and develop a routine to put the Chrome battery claims to the test. After 3 days of continuous testing on a freshly installed 14" MacBook Pro with an M2 Pro processor and 16 GB RAM running the latest stable releases of both browsers, Birchler came to some interesting conclusions. In my 3-hour tests, Safari consumed 18.67% of my battery each time on average, and Chrome averaged 17.33% battery drain.That works out to about 9% less battery drain from Chrome than Safari.Yes, you read that right, I found Chrome was easier on my battery than Safari. While I did experience some variability in each 3 hour test run, Chrome came out on top in 5 of the 6 direct comparisons. Matt Birchler His methodology seems quite sound and a good representation of what most laptop users will use their browser for: YouTube, social media, a few news websites, and editing a Google Doc, in a 20 minute loop that was repeated for three hours per test. Multiple of these three hour tests were then ran to counter variability. I highly doubt using different websites will radically change the results, but I obviously am curious to see a similar test ran on Windows and Linux, x86 and ARM, for a more complete picture that goes beyond just the Mac. Conventional wisdom is sometimes wrong, and I think we have a classic case of that here. While there may have been a time in the past where Chrome on the Mac devastated battery life, it seems Chrome and Chromium engineers have closed the gap, and in some cases even beat Safari. Now, this doesn't mean everybody should rush and switch to Chrome, since there are countless other reasons to use Safari over Chrome other than supposed battery life advantages. With Apple PR arguing that alternative browser engines should not be allowed on iOS because Chrome would devastate iOS' battery life, tests like these are more important than ever, and I hope we're going to see more of them. Tech media always just seems to copy/paste whatever manufacturers and corporations claim without so much as a hint of skepticism, and this benchmark highlights the dangers of doing so, in case you didn't already know believing corporations was a terribly idea.

Linus Torvalds justtaggedthe Linux 6.11 kernel as stable. There aremany changes and new features in Linux 6.11includingnumerous AMD CPU and GPU improvements, preparations for upcoming Intel platforms, initial block atomic write support for NVMe and SCSI drives, the DRM Panic infrastructure can now display a monochrome logo if desired, easier support for building Pacman kernel packages for Arch Linux, DeviceTree files for initial Snapdragon X1 laptops, and much more. Michael Larabel Especially the Snapdragon stuff interests me, as I really want to move to ARM for my laptop needs at some point, and I'm obviously not going to be using Windows or macOS. I hope the bringup for the Snapdragon laptop chips is smooth sailing from here and picks up pace, because I'd hate for Linux to miss out on this transition. Qualcomm talked big game about supporting Linux properly, but it feels like they're - what a surprise - not backing those words up with actions so far.

It's always a lovely day when it's a Haiku release day - and sadly, those don't come very often. Of course, Haiku's nightlies tend to be rather solid so an official release isn't really a must if you want to use Haiku, but if you were holding out for something more stable: Haiku has just released its fifth beta, Haiku R1/beta5. We've covered most of the new features and changes as they were developed, but since it's been so long since the previous beta, we should cover some of the highlights. One of the collection of improvements that's impossible to put in a screenshot is the performance improvements the successor to BeOS has received since the release of R1/beta4, and there are many. There's a ton of general performance improvements, of course, covering everything from the kernel to applications, including much better throughput in TCP, the network stack, which should lift Haiku's network performance much closer to that of other, more mature operating systems. There's also an overhaul of the user_mutexsystem, and much more. A great many performance optimizations were done to the kernel and drivers, including batching many more I/O operations, avoiding unnecessary locks on application startup, improved pre-mapping of memory mapped files, reduced lock contention in page mapping, batched modification of the global memory areas table (and a different implementation of its underlying data structure), changes to keep page lists in-order to ease allocations, temporary buffer allocation performance improvements in hot I/O paths, support forDT_GNU_HASHin the ELF loader, and more. Haiku R1/beta5 release notes Looking at the end user side of things, the Appearance dialog has been simplified without removing any features or capabilities, and Haiku now also comes with a dark mode. The little power/battery widget in Deskbar has also been overhauled to provide more accurate battery information, and it'll load automatically if a battery is detected in the system. Tracker (the file manager) and Icon-O-Matic have seen improvements, there's a rewritten FAT driver, a brand new UFS2 driver, and much more. There's also a ton of new application ports from the Qt and GTK world, especially if the last time you've tried Haiku was one of the previous betas. Thanks to all of these ports, it's much more realistic now to use Haiku as a daily driver. Haiku now also offers experimental support for .NET and FLTK, which provides further avenues for ports. This is just a small selection, as there is so much more contained in this new beta release. If you've been running the nightlies this new beta won't mean much to you, but if you've been out of the running for a while, Haiku R1/beta5 is a great place to start to see what the platform has to offer.

To empower tablet users to get more done, we're enhancing freeform windowing, allowing them to run multiple apps simultaneously and resize windows for optimal multitasking. Today, we're excited to share that desktop windowing on Android tablets is available in developer preview. For app developers, the concept of Android apps running in freeform windows has already existed with solutions like Samsung DeX and ChromeOS. Updating your apps to support adaptive layouts, more robust multitasking, and adaptive inputs will ensure your apps work well on large screens across the Android ecosystem. Francesco Romano on the Android Developers Blog The long-running saga of Google trying to develop proper freeform windowing support for Android seems to finally be bearing fruit. Countless attempts came and went, usually in developer releases, hidden behind flags, rarely, if ever talked about, but now it's finally not only part of an Android beta release anyone with a Pixel Tablet can install and try out, Google is also openly talking about and touting it as a feature, so we might actually perhaps maybe see this in a non-beta release at some point. The way it works is both surprising and rather unsurprising. Instead of the Apple approach, which seems to entail a deep disdain for traditional windowing, Google is pretty much embracing the things we expect a windowing system to have, from window titlebars with close and maximise widgets, to a traditional dock-like taskbar permanently available at the bottom of the screen. If you click or tap on a little downward arrow on the titlebar, you can choose options like displaying windows side-by-side, much like on Windows. A very welcome feature' is the ability to tear off Chrome tabs and turn them into their own windows, just like in a traditional desktop environment. Google also opted for an interesting approach that reminds me somewhat of the desktop" mode on Windows RT. Since Windows RT was ARM-based and entirely locked-down, the only classic Win32 applications you could run were those bundled with Windows as well as Microsoft Office. To access these, Windows RT would launch a full-screen tablet application that contained the entire traditional Windows desktop, and you'd run your classic Win32 applications in there. Android's new windowing system seems to be doing something similar: once you enter the freeform windowing mode, all future applications will also launch as windows. In the task switcher, however, they're all contained within a single desktop" entry that you can close if you want to. That desktop entry seems to take the shape of a live view of the desktop", including the various windows you have opened. This way, you can have a dedicated desktop" with freeform windows alongside any fullscreen tablet applications you also happen to be running. It's perhaps not the most integrated or elegant approach, but it's dead-simple and easy to grasp. This new windowing environment also provides application developers with the option of allowing multiple instances of a single application to be launched, say launching two text editor windows side-by-side. This seems to be a specific property developers need to enable, though, and considering Android's tablet adoption history, that's anything but a given at this point. Of course, it shouldn't come as a surprise that applications need to be able to resize gracefully, too. If you want to play with it, you'll need a Pixel Tablet running Android 15 QPR1 Beta 2, or just use the simulator. I really hope this takes off and developers support the various APIs for optimal integration (I'm not getting my hopes up), since proper freeform windowing that doesn't feel like an ugly, barely functional hack is something I've been wanting on Android for a long time.

The consequences of the massive CrowdStrike failure for Windows are slowly coming into focus. Microsoft recently held a security summit with some of the large security software vendors, and the company is making several rather vague promises about what it's going to do to make sure an incident like CrowdStrike never happens again. A key part of these promises is the realisation that security software really shouldn't be running in the kernel, and to make that possible, MIcrosoft will need to add several security features in userspace. Both our customers and ecosystem partners have called on Microsoft to provide additional security capabilities outside of kernel mode which, along with SDP, can be used to create highly available security solutions. At the summit, Microsoft and partners discussed the requirements and key challenges in creating a new platform which can meet the needs of security vendors. David Weston at the Windows Blogs This is easier said than done, as moving things from kernel to userspace tends to incur a performance penalty, as well as making it harder to detect software with bad intentions early enough. Microsoft is going to have do some serious reworking of both the kernel and userspace when it comes to security before it'll be able to completely close up the kernel and make it impossible for security software to mess around in kernelspace. Microsoft doesn't offer any concrete steps or measures quite yet, so we'll have to wait and see just how far they're willing to go. There's really not much else to say at this point - empty platitudes, vague promises, and tons of marketing speak don't secure an operating system, after all.

It seems Google is hell-bent on removing anything from Android that makes the platform stand apart from iOS. One of the features of Android and the Play Store that users of rooted and/or de-Googled phones will be familiar with is SafetyNet Attestation, something that Android applications can use to check, among other things, if the device it's running on is rooted or not, and take any action from there based on that information. Notoriously, some banking applications on Android will refuse to work on rooted and/or de-Googled devices because of this. Earlier this year, at Google I/O, the company unveiled the successor of SafetyNet Attestation, called the Google Play Integrity API, and it comes with a whole lot more functionality for developers to control what their application can do on devices based on the status of the device and the application binary in question. Play Integrity will let the developer's application know if its binary has been tampered with, if Google Play Protect is enabled, if the Android device it's running on is genuine", and a whole lot more. Based on that information, the application could decide to warn users when they're about to do something sensitive that their device is rooted, or it could just throw up its hands entirely and refuse to function at all - and there's really not much the user can do about this. A new capability of the Play Integrity API is that developers can now also determine where it came from - i.e., if it was sideloaded or installed through a non-Play application store - and then throw up a dialog allowing the user to switch to the version from the Play Store instead. Doing so will delete the original binary and all its data, and replace it with the Play Store version. The problem here is that the only other option is to cancel, and not have the application load at all. As you can see, the remediation dialog tells you to get this app from Play" in order to continue using it. There's an option to close the dialog, but there's no way to bypass it entirely. If you close the dialog, a response is sent to the app that lets the developer know so they can decide whether to continue blocking access. Mishaal Rahman at Android Authority Several applications appear to already be using this new capability, and while it won't mean much for people running Google's, Samsung's, or any other blessed by Google" version of Android on unrooted devices, people running, say, /e/OS, GrapheneOS, LineageOS, or any other de-Googled and/or rooted device is going to be having a very bad time if more and more applications adopt this capability. If you're running a device without Play Services, relying solely on the vast and varied library of applications from F-Droid, for instance, while also sideloading a few applications only available in the Play Store, you could very well be running into problems. We'll have to see just how widespread this capability becomes, but I can already foresee this becoming yet another major headache for anyone trying to use a smartphone that isn't from blessed by Apple or Google. Personally, I'm lucky in that Swedish banking and ID applications worked on de-Googled Android phones, but with the expanding reach of the Play Integrity API, as well as possible let's enable this by default" shenanigans by Google, I'm definitely worried about this remaining so in the future.

This summer, I embarked on a side project to create a brand-new Palm OS game, and after less than two months of intermittent coding, I'm excited to announce that it's ready to be released to the public! Captain's Quarters The game in question is a top-down minigolf game, and works on devices running Palm OS 3.5 and higher, in both monochrome and colour, and there's high-resolution support for devices running Palm OS 5.0 and higher. Sadly, my own Palm OS devices were all drained of battery so I couldn't quickly load it up and play it on real hardware in time for this post (rest assured, my T|X is currently charging), but you can play it in your browser if you want to. Like any other top-down minigolf game, it's simple and fun to play. The game's creator, whose real name I can't find so I'll just refer to them by their blog's name Captain's Quarters, also wrote a published a post about the process of developing a Palm OS game in 2024. Especially the section on what is needed to code for Palm OS today is important if you're also interested in picking this up. The best news is that developing a Palm OS game can be done on modern hardware, that saves me a lot of time not having to deal with virtual machines or having to set up an old PC running Linux. For getting a working compiler, I used prc-tools-remix, which is the same old compiler as in the old days, but it's updated to work on a modern day Linux or OS X system. Captain's Quarters People in general are often oblivious to just how advanced and capable both Palm OS and Windows PocketPC PDAs really were - most people never had one - and even more people are oblivious to just how vibrant the gaming scene on Palm OS was. My Palm OS devices were some of the best gaming handhelds I've ever had, and my love for jewel-matching games still goes strong today on Android, but it all started on Palm OS, the original mobile home of the original Bejeweled. Palm OS games got me through quite a few boring lectures and classes in university.

And the hits just keep on coming. After buying an ad tech company and working with Facebook to weaken Firefox' privacy features, Mozilla is now integrating AI chatbots straight into Firefox with the recent release of Firefox 130. People are understandably big mad about this, and as such the calls for switching to alternatives is growing stronger. Considering the only true alternative to Firefox is Chrome and its various skins, those of us looking to send Mozilla a message are kind of relegated to trying out Firefox skins instead. Switching to what are essentially Firefox distros" to collectively try and nudge Mozilla back to making more sensible decisions instead of AI hype chasing is an eminently reasonable one. There's more reasons than just that. Part of the reason I use Firefox-based browsers rather than Chromium browsers is because I want to preserve some choice and diversity in browser engines. The existence of a choice of different Firefox derived browsers may allow space for experimentation in designingbetterbrowsers. In Chromium land,Archas shown that there's an opportunity for quite radically rethinking how browsers work. Same forOrionin Mac/iOS-land. This isn't a detailed review of the different browsers, just a few comments and observations having tried them. Tom Morris I have my reservations about using Firefox skins, mostly because no matter what you do, you're still entirely dependent on the choices Mozilla makes during the development of the venerable browser. If Mozilla keeps deviating from the traditional goals more and more, the amount of work these Firefox skins need to perform to reign the browser back in will start to increase, and who knows if they have the manpower, experience, and skills to do so? More worryingly, will they be able to keep up with Mozilla's release schedule, including important bugfixes and security patches? My worries go beyond those basic things, though. Considerably fewer eyes will be going over any code changes these Firefox-based browsers make, and as recent history has shown us, infiltrating a small, understaffed open source project for nefarious purposes is a thing that happens. Another issue to consider is nebulous ownership of such Firefox versions, as are questions around who financially supports such efforts. Your browser is a massively important and crucial piece of software that holds and has access to a lot of your personal data, and you should be particularly careful about who owns your browser. This is not to say each and every one of them is bad - just that you have to be careful about who you trust. Several Chrome skins, like Brave and Opera, have time and time again shown to be shady, untrustworthy companies pushing crypto bullshit, ripping off websites, have shady owners, and more - don't use Brave, don't use Opera - and there's no guarantees the same won't happen with Firefox skins riding the wave of unhappiness with Mozilla. Please be mindful. I don't have an answer for this issue, either - I just want to caution against throwing the browser out with the bath water and switching to a project you might not know a lot about.

Not too long ago, Mozilla announced it was going to extend its support for Windows 7, and was mulling over extending support for Windows 8.x as well, without providing any time frames or details. Well, we've got the details now. According tothe Firefox Release Calendar website, Firefox 115 ESR, the latest Firefox version with support for Windows 7, 8, and 8.1, will continue receiving updates until April 1, 2025. Firefox 115.21 ESR is expected on March 4, 2024, which means users with old Windows versions have at least seven more months of support from Firefox. Taras Buria at Neowin The same extension to March 2025 for Firefox 115 ESR also covers macOS 10.12-10.14. The reasoning behind the extension is simple: there's still enough users on these older operating system version for Mozilla to dedicate resources to it, despite how difficult backporting security fixes to 115 ESR has become. Firefox is pretty much the only mainstream browser still supporting Windows 7 and 8, and that's definitely commendable.

With the recent Rust in Linux events in the last couple of days, it's a good time to write up Rust in illumos. Both to spread the word a bit and also to set expectations for both sides (Rust and illumos/OpenIndiana devs) what is currently possible and what work would need to be invested to make things smooth. And also to let the Rust community know about what illumos people were talking about. What most of the talk currently is about, are the technical details. But we must not leave the social aspects out of it. Software distributions are not made by lone walkers but by groups of people. Bringing in a new language means facilitating change. And that means there are more topics to discuss than just API design. We are talking about impacts on the whole software lifecycle. Till Wegmuller (Toasty) I try to steer clear of all the Rust-related drama, mostly because it's outside of my wheelhouse, but also because I don't think anything I can highlight here will help anyone get anywhere or solve anything. In this particular case, there's no drama, and it's just a good ol' discussion about what Rust as a programming language can contribute to the illumos community and code. I can't program so here my useful contributions end.

Earlier this year, I reviewed the excellent and unique MNT Reform laptop, an (almost) fully open source, very hackable laptop. MNT has just unveiled the upcoming follow-up to the Reform, called the Reform Next. Being highly performant, modular, and upgradeable, MNT Reform Next gives you more freedom than any other laptop. Swap modules, print your own case, customize your keyboard. Since we are committed to open hardware, allsources are public. While Classic MNT Reform is a portable device, we felt like a sleeker, more lightweight design would increase portability and make for a more flexible laptop. MNT website The focus seems to have been on both performance and size, and I think the latter is especially important for a lot of people who might not have been too enamored with the original Reform's chunky, brutalist design. The device has been made thinner by splitting the motherboard up into several connected, separate boards, that also happen to improve the repairability and upgradeability of the device. The battery pack has been redesigned for a smaller physical size, too, and the trackball option is no longer available - it's trackpad-only. The Reform Next is compatible with MNT's latest processor module, the RK3588, and as such, packs a bigger punch. This SoC has four ARM Cortex-A76 cores up to 2.4 Ghz, and four power-efficient ARM Cortex-A55 cores up to 1.5 Ghz. This SoC is also available as an upgrade for the MNT Reform and the MNT Pocket Reform, and ships with either 16 or 32 GB of RAM and an ARM Mali G610 MP4 GPU. Of course, the Reform Next will be as open as humanly possible, both software as well as hardware-wise, and it's looking like a worthy successor to the MNT Reform. I'm incredibly delighted that MNT seems to have found a niche that works for them, and enabling them to keep developing and releasing hardware that goes against every trend in the industry, giving us entirely unique devices nobody else is making.

For certain use cases, it's advisable to set up a read-only root file system, which ensures better reliability in case of system issues. Think of scenarios like a router (critical for network access) or a caching reverse-proxy, such as the one described in my seriesMake your own CDN. WhileFreeBSD natively supports this configurationand some Linux distributions offer custom solutions (e.g.,Alpine Linux),NetBSDstands out as an excellent choice for such devices. It supports nearly all embedded devices, is lightweight, and its stability minimizes the need for frequent updates. Stefano Marinelli Exactly what it says on the tin. Friend of the website (a new term I just made up and will use from here on out for some people) Stefano Marinelli, fresh from his series about making your own CDN using the various BSDs, explains how to set up a NetBSD system with a read-only root filesystem for the special use cases where this makes sense.

I had a chance to speak to Jack Huynh, AMD's senior vice president and general manager of the Computing and Graphics Business Group, during IFA 2024 in a question and answer session. Due to speculation that AMD won't launch flagship GPUs for its next-gen lineup, I pressed Huynh for information regarding the company's plans for the high-end GPU market with the RDNA 4-poweredRadeonRX 8000-series. His comments sketch out a plan focused specifically on gaining market share in the GPU market above all else, and this strategy deprioritizes chasing Nvidia's highest-end gaming cards - at least for now. Paul Alcorn at Tom's Hardware Reading through the actual comments, it seems that AMD is not going to chase the very, extreme high-end that NVIDIA serves, like the 4090 level of GPUs. Honestly, I'm completely okay with that - those high-end GPUs are insanely expensive, and unlike what YouTube and tech websites might suggest, nobody buys these GPUs. Consistently, for more than a decade now, it's the xx60-xx70 levels of cards that dominate the market, and it's smart of AMD (and Intel) to focus on that segment if you want to sell as many GPUs as possible. The very top of the GPU market just doesn't make a lot price/performance sense. You pay considerably more for a 4090 compared to a 4080, but the price increase does not correspond to a similar increase in performance. It simply makes a lot more sense to save that money and spend it elsewhere, such as on a better CPU, more RAM, more storage, or a new display. I'd rather AMD not waste time and energy on making these high-end GPUs nobody buys, and instead focus on improving the GPUs people actually buy. And of course, AMD just hasn't been able to match NVIDIA at the top end, and that's probably not going to change any time soon. Releasing a high-end, expensive GPU, only to be trounced by your one competitor every single time is not a good look, so why even try?

It's been two years, but we finally have a proper new Redox release: the Redox team released version 0.9.0 today. Since we've been covering all the monthly progress reports from this Rust-based operating system for a long time now, we've already covered most of the improvements in this new release, so if you've been following along there shouldn't be any major surprises in here, but let's do a quick summary anyway just so we're all up to speed. I think the primary thing anyone moving from the previous release to the new one will be massive performance and stability improvements, as well as the arrival of the first few applications from System76's new COSMIC Desktop. Redox is led by Jeremy Soller, a System76 engineer, and since COSMIC uses Rust as well, it only makes sense for the two projects to start benefiting from each other's progress. Porting Linux and BSD programs has also become a lot easier, which is also evidenced by a whole slew of new ports from those operating systems. Redox works in both virtual machines and on real hardware, but the former is definitely advised over the latter. In the latest monthly progress report, which was published only a few days ago, it's mentioned that Redox performance in virtual machines has improved greatly. The team discovered that reading the system time was a huge bottleneck in the context switching code, which affects virtual machines particularly hard because it needs to be read from outside oft he VM. Redox now reads the TSC using KVM's paravirtualized system time API to remove this bottleneck. Running in a VM, Redox is now becoming slightly faster than Linux at certain synthetic benchmarks, for example the same-core context switch latency when using POSIX pipes (tested with mitigations=off). More exciting optimizations are coming, both to reduce context switch overhead further towards the hardware limit, and to reduce unnecessary context switches overall. Ribbon and Ron Williams As time moves on and both Redox and COSMIC improve, my excitement for this operating system grows along with it. It seems the people working on both projects have their priorities quite straight, and while I'm obviously not going to make any idiotic grand statements about how Redox will replace anything, I wouldn't be surprised to see it become a fairly solid option for those of us willing to deal with the issues that come with running something that isn't Windows, Linux/BSD, or macOS.

AppSumo is a marketplace where software developers and other entrepreneurs can launch their products, giving special offers to early adopters. Many AppSumo deals offer lifetime licenses, so you can throw in your support for an up-and-coming product and be rewarded with a deal-for-life that will save you up to 95% compared to paying monthly. If you're a developer, AppSumo is a great way to get attention for your launch, and quickly find a cohort of savvy paying customers. AppSumo deals are all limited-time offers, but this week they're doing their Last Call" event, where crowd favorite deals are brought back for a limited time (but only for members paying for the Plus tier).

How does Linux move from an awake machine to a hibernating one? How does it then manage to restore all state? These questions led me to read way too much C in trying to figure out how this particular hardware/software boundary is navigated. Jacob Adams So this is a lot deeper of a dive than I expected, and it blows my mind just how complex sleep, hibernating, and waking a computer really is. Instinctively you know this, but seeing it spelled out like this really drives that point home - and this only covers going into hibernation. It also highlights how hard it must be for the developers involved to keep this working at all, especially on the wide variety of machines and hardware combinations Linux runs on. It wasn't too log ago that pretty much the only platform where sleeping and waking worked reliably was Mac OS X with its controlled, small hardware selection, so it's kind of remarkable this works at all on Linux now. I haven't had to worry about sleeping and waking with Linux for quite a while now, and it's one of those things that just works" so I never have to think about it. This definitely wasn't always the case, though, and on both Linux and Windows I would just turn the whole feature off since it rarely worked reliably, especially on desktops. I'm sure it still breaks for people, but for me, it's been rock solid, and reading through the linked article, I'm even more amazed about this than I already was.

The KDE project is currently having its yearly conference - Akademy - and at the conference, the project announced its goals for the coming years. The KDE community has charted its course for the coming years, focusing on three interconnected paths that converge on a single point: community. These paths aim to improve user experience, support developers, and foster community growth. Farid Abdelnour on the KDE Blogs First, the project intends to make it easier for developers to build KDE applications. They want to do this in various ways, but most notably they want to improve the developer experience for people writing KDE applications in languages other than C++, such as Rust or Python. This is a very welcome goal, as I feel there's definitely a bit of a lack of new KDE applications, and as any other open source project, KDE can always use more developers. Second, KDE is going to focus on improving the input experience, as in the various ways you interact with your computer. Accessibility, and the more complex input methods people with accessibility needs require, are also part of this goal, but it also covers simpler things like mice with tons of buttons, drawing tablets, 2-in-1 laptops, and so on. I'm assuming this also includes controlling the various RGB stuff found in every keyboard and mouse these days, as this is something KDE has already been making inroads into. The third and final goal is one strongly related to the first goal, as it involves community outreach to attract new contributors. This covers not just individual contributors, but also support from institutions, organisations, and I'm guessing companies, too. With Valve opting for KDE for its Steam Deck, I wouldn't be surprised to see some more involvement from that direction, too, which meshes well with the input goal mentioned above. If you all keep becoming Patreons and donating to us, I might be able to actually go to Akademy next year and be a fly on the wall for some more in-depth reporting from such a conference. I can't guarantee anything - especially since I have two small children, live far away from everything here in the Arctic, and have serious anxiety problems to take into account, but it's definitely a goal for me for next year.

Paul Weissmann's OpenPA, the invaluable archive on anything related to the HP's PA-RISC architecture, devices, and operating systems, has branched off for a bit and started collecting information on RISC laptops. Technical computing in the 1990s was mostly done on RISC workstations with Unix operating systems and specialized applications. For mobile use cases, some of the popular RISC vendors built RISC Laptops for mobile Unix use in the 1990s. Often based on contemporary Unix workstations, these RISC laptops were often marketed for government and military uses such as command, technical analysis and surveillance. Paul Weissmann at OpenPA OpenPA has always had content beyond just PA-RISC (like HP's Itanium machines), so this is not entirely surprising, and it also happens to be something that's sorely needed - there's remarkably little consolidated information to be found on these RISC laptops, and it's usually scattered all over the place and difficult to find. They were expensive and rare when they were new, and they're even rarer and often more expensive today. What we're talking about here are laptops with PA-RISC, SPARC, (non-Apple) PowerPC, and Alpha processors, running some variant of UNIX, like HP-UX, SunOS/Solaris, AIX, and even Windows NT. A particularly interesting listing at the moment is the Hitachi 3050RX/100C, a laptop based on the Hitachi PA/50L PA-RISC processor that ran something called HI-UX/WE2, a UNIX from Hitachi I can't find much information about. The most desirable laptop listed is the amazing Tadpole Viper, which was the most powerful SPARC laptop Tadpole ever made, and I'm pretty sure it's the most powerful SPARC laptop, period. It was powered by a 1.2Ghz UltraSPARC IIIi processor, and was also sold as the Sun Ultra 3, in 2005. I would perform some seriously questionable acts to get my hands on one of these, but they're most likely virtually impossible to find. Anyone who can help Weissmann find more information - feel free to do so.

The MAS project, a group of people working on an open source Windows and Office activator featuring HWID, Ohook, KMS38, and Online KMS activation methods, discovered quite a neat and interesting bug in the code responsible for licensing in Windows. In our ongoing work to bypass Windows licensing checks, we occasionally stumble upon bugs that we choose to keep secret. This decision allows us to preserve potential future activation methods by avoiding bug fixes, while also giving us valuable tools for testing or developing new methods. One such discovery, which we've named Keyhole", turned out to be a highly effective DRM bypass. It gave users the ability to license any Microsoft Store app or any modern Windows edition with ease. The MAS project There were quite a number of roadblocks to overcome here, such as Microsoft's code obfuscation tool, called Warbird, which was already done by someone else, after which they could really start digging into the code responsible for handling Microsoft Store and Windows licenses. They then discovered that circumventing the license blocks that hold the actual license information was dead simple - every license block is followed by a signature block covering all the data that comes before it. It turns out that messing with the licensing system was as simple as... Adding data after that signature block. That was it. As it turns out, data after the signature block isnt checked at all... and it can even override data that came before it. Whenever two blocks of the same type are stored together, the last one overrides all the others before it. So, if we want to change any license data, we can just make a block for it and put it after the signature block! This method lets us make licenses for anything sold on the Microsoft Store, including Windows, from any other Microsoft Store license. And since there are so many free apps with licenses, we now had the ability to make as many as we wanted for whatever we wanted. This bug essentially punched a hole straight through CLiP's DRM, so we decided to name it Keyhole". The MAS project This opened up a massive hole in Microsoft's licensing tools and DRM, and allowed the MAS project to pretty much do whatever they wanted. They could even do things that used to be impossible, such as activating Enterprise LTSC with a digital license, or even activating a legitimate KMS server with a generic key". Sadly, the fun didn't last long, as right around the same time, Cisco TALOS discovered this same bug, reported it to Microsoft, who then proceeded to fix it. the MAS project also discovered something else incredibly interesting, something which further highlights the seemingly terrible lack of quality assurance and code quality inside Microsoft. They noted that the kernel driver responsible for licensing looked incredibly shoddy, full of what they call odd choices and compromises". In fact, they soon realised that they had seen this code before: it was a straight-up copy/paste job from the licensing DRM found on the Xbox One. And there's the same bug that's in CLiP, but in Xbox code. In fact, we weren't too surprised to find this, as we found that almost all of CLiP, from the XML format of the licenses to the TLV-based license blocks, is copy-pasted straight from the Xbox One's DRM system. The MAS project Code reuse obviously makes sense in some situations, but the fact Microsoft even copy/pasted entire sections of code from the Xbox One straight into the Windows kernel as a kernel driver seems rather irresponsible. Shouldn't code added to the Windows kernel and installed on billions of devices be vetted a little better than this?

So given that, xmem can be useful as a monitoring tool.Fluffy(my main server) runs both squid and apache, and given that fluffy only has 64MB of RAM, things can get a little cramped. If I suddenly see that the whole of xmem turns blue (i.e. the swap file's thrashing), then I know that something is odd, and I can easily find out which processes are eating up so much RAM. I said earlier that xmem can brighten up one's desktop. Indeed, as I useFVWMin a rather archaic fashion, it seems fitting I should like xmem. Here's a full screenshot showing xmem (plus other applications) in action. Thomas Adam This is basically just an excuse to show off this awesome FVWM desktop shown off in this short little article about xmem, written by one of FVWM's core developers. It just looks neat.

We are proud to announce that version 1.6 of the Windows App SDK is now available! Whether you're looking for the incredible performance boost and footprint reduction of Native AOT support, enhancements for deploying your package, or quality of life improvements for controls like PipsPager and RatingControl, WinAppSDK 1.6 offers a raft of new features, performance boostsand structural changes that enable you to make your native Windows apps better than ever before. The Windows App SDK providesa rich set of APIs and tools to help you build beautiful and fast Windows desktop apps, including any C++ Win32 or C# .NET app. You can harness the modern controls and polish of WinUI 3, which ships as part of the WinAppSDK, or if you have an existing app that uses Win32 such as WPF, you can take advantage of only the parts of the SDK that you need. The WinAppSDK also stays up to date with frequent and OS-independent releases so your app can always access the latest innovations. Duncan MacMichael at the Windows Blogs There's actually quite a few nice and welcome updates in version 1.6, most prominently the aforementioned Native AOT. This stands for native Ahead-Of-Time (AOT) compilation, and, as the name suggests, compiles your application ahead of time for the architecture it's going to run on. This reduces the size of the application package and greatly improves the startup time. Another welcome improvement is that the embedded Edge WebView2 SDK is no longer hard-coded, but a NuGet reference, so developers can choose to use any version of the webview they want, preferably the newest version. There's a lot more in here, so if you're a Windows developer trying to use the latest set of tools from Microsoft - this one's for you.

Unsurprisingly, this change has not been met with a lot of enthusiasm by the average Windows user, and with Microsoft nowofficially recommending users migrate over to the Settings app, it seems that before long we may have to say farewell to what used to be an intrinsic part of the Windows operating system since its first iterations. Yet bizarrely, much of the Control Panel functionality doesn't exist yet in the Settings app, and it remain an open question how much of it can be translated into the Settings app user experience (UX) paradigm at all. Considering how unusual this kind of control panel used to be beyond quaint touch-centric platforms like Android and iOS, what is Microsoft's goal here? Have discovered a UX secret that has eluded every other OS developer? Maya Posch I like the Windows Control Panel, and approaches like it. They're easy to use, they allow you to have multiple settings panels open at the same time, they can be easily extended by third parties - for better or worse - and they make it easy to find things with colourful, recognisable icons. The current Windows Settings application is a massive regression, as is the change from macOS' iconic and incredibly user-friendly System Preferences to the new System Settings application. KDE also moved to a sidebar design I'm not a fan of, and GNOME has had a similar unpleasant, monochrome sidebar, too. It's not big enough of an issue to make a huge deal out of, and the KDE sidebar settings application is at least marginally usable, but I really do wish someone would have the guts to undo this general trend, because it's getting harder and harder to find the settings I want at a glance, and not allowing you to open multiple settings panels at the same time is a huge loss. And a small note: this article uses the Windows 3.x Control Panel as its starting point, but both Windows 1.x and 2.x had a Control Panel as well. It's an old concept, for sure.

The Internet Archive has lost its appeal in a fight to lend out scanned ebooks without the approval of publishers. In adecision on Wednesday, the Second Circuit Court of Appeals ruled that permitting the Internet Archive's digital library would allow for widescale copying that deprives creators of compensation and diminishes the incentive to produce new works." The decision is another blow to the nonprofit in theHachette v. Internet Archivecase. In 2020, four major publishers - Hachette, Penguin Random House, Wiley, and HarperCollins -sued the Internet Archiveover claims its digital library constitutes willful digital piracy on an industrial scale." Emma Roth If you're a library and scan books and offer a lending service, you're committing willful digital piracy on an industrial scale". If you scan the entire goddamn internet without any regard for licensing or copyright and regurgitate chunks of it on command, you're a visionary, a revolutionary, a genius. Make it make sense.

A. Wilcox, the original creator of Adelie Linux, has ported systemd to musl, the glibc alternative. I have completed aninitial new portof systemd to musl. This patch set does not share much in common with the existing OpenEmbedded patchset. I wanted to make a fully updated patch series targeting more current releases of systemd and musl, taking advantage of the latest features and updates in both. I also took a focus on writing patches that could be sent for consideration of inclusion upstream. The final result is a system that appears to be surprisingly reliable considering the newness of the port, and very fast to boot. A. Wilcox I absolutely adore Adelie Linux as a project, even if I don't run it myself, since they have a very practical approach to software. Systemd is popular for a reason - it's fast and capable - and it only makes sense for Adelie to offer it as a potential option, even when using musl. Choice is a core value of the open source and Linux world, and that includes the choice to use systemd, even for a distribution that has traditionally used something else. The port is already quite capable, and Wilcox managed to replace OpenRC on her system with systemd in-place, and it booted up just fine, and it also happened to boot in about a third of the time OpenRC did. It's not ready for prime time yet, though, and most services are not yet packaged for systemd, an effort for which Adelie Linux intends to rely on upstream and cooperation with systemd experts from Gentoo and Fedora. They're also working together with systemd, musl, and others to make any switching a user might want to do as easy as possible. A beta or anything like that is still a ways off, but it's an impressive amount of progress already.

Today we're releasing Android 15 and making the source code available at theAndroid Open Source Project(AOSP). Android 15 will be available on supported Pixel devices in the coming weeks, as well as on select devices from Samsung, Honor, iQOO, Lenovo, Motorola, Nothing, OnePlus, Oppo, realme, Sharp, Sony, Tecno, vivo, and Xiaomi in the coming months. We're proud to continue our work in open source through the AOSP. Open source allows anyone to build upon and contribute to Android, resulting in devices that are more diverse and innovative. You can leverage your app development skills inAndroid StudiowithJetpack Composeto create applications that thrive across the entire ecosystem. You can evenexamine the source codefor a deeper understanding of how Android works. Matthew McCullough at the Android Developers blog While it's great that we're still getting open source Android releases, the reality of it is that Google has eroded so much away from the Android Open Source Project that AOSP has become effectively useless. Back in the olden days, AOSP was a complete mobile operating system, but those days are long behind us. Google has moved so much from AOSP over to proprietary frameworks, applications, and cloud services that running that it's no longer a complete package, which is a huge shame. Still, AOSP plays an important role for the custom ROM community and the various companies and communities making privacy-first, de-Googled Android versions, and for that reason alone it's good that it still exists, even in its gutted state. Android 15's AOSP release will surely find its way to LineageOS, /e/OS, GrapheneOS, and the countless other alternatives to butchered Android OEM versions and people seeking a more private smartphone experience. As for when Android 15 will hit Pixels - that's going to be a few weeks from now, later than usual after the source release.

That's the 1983 Convergent WorkSlate, a one-of-a-kind handheld system from some misty alternate history where VisiCalc ruled the earth. Indeed, even the software" packages Convergent shipped for it - on microcassette, which could store voice memos and data - were nothing more than cells and formulas in a worksheet. The built-in modem let you exchange data with other Workslates (or even speak over the phone to their users), and it came with a calculator desk accessory and a rudimentary terminal program, but apart from those creature comforts its built-in spreadsheet was the sole centre of your universe. And, unlike IAI and theCanon Cat, I've yet to find any backdoor (secret or otherwise) to enable anything else. That means anythingyouwant to program has to be somehow encoded in a spreadsheet too. Unfortunately, when it comes to actually programming the device it turns out the worst thing a spreadsheet on an 8-bit CPU can be is Turing-complete (so it's not), and it has several obnoxious bugs to boot. But that doesn't mean we can't make it do more than balance an expense account. Along the way we'll examine the hardware, wire into its peripheral bus, figure out how to exchange data withtoday'sfuture, create a simple game, draw rudimentary graphics and (with some help) even put it on the Internet with its very own Gopher client - after we tell of the WorkSlate's brief and sorrowful commercial existence, as this blog always must. Cameron Kaiser The amount of knowledge, skill, and sheer passion Cameron Kaiser displays in every one of these articles he writes is astonishing, and I'm incredibly grateful websites like OSNews can benefit from the work of people far, far smarter and more skillful than I'll ever be. The code for the projects detailed in the article is available on GitHub, and more technical information can be found on Kaiser's website.

Kim Carver, a legislator in the US state of Louisiana, added a provision to a child safety bill forcing Apple and Google to enforce age restrictions on downloads in their application stores. In other words, it would force Apple to make sure minors could not download gambling and casino applications - i.e., 99% of mobile games - that make up the vast majority of Apple's services revenue. It would also make application stores play a role in enforcing age restrictions on social media applications, which makes sense because Apple and Google know the age of every one of their users. Well, it turns out Apple was not happy. They sent out an absolute army of lobbyists - including a guy known for lobbying on behalf of truck-stop casinos, in case you were wondering about the type of people Apple uses for lobbying - to kill this specific provision. Carver's provision would have breezed through the Louisiana senate, but it needed a key committee approval before being put up for a vote. And it's this committee that Apple started heavily influencing and pressuring. Carver began hearing rumblings that Apple was making inroads with the committee-his amended bill might be in trouble. Uncertain on how to proceed, he approached the chairwoman of the committee, Sen. Beth Mizell, for advice. He declined to describe the substance of the conversation to The Wall Street Journal, but in the end, he promised not to object if she removed the app store provisions or support restoring them on the Senate floor. I made the choice to take the win that we could get," Carver said. Jeff Horwitz and Aaron Tilley at The Wall Street Journal This is not the first time Apple has pressured legislatures to drop bills it didn't like. A famous case is the state if Georgia, which intended to pass a number of application store bills to open up the App Store in much the same way the European Union did with the DMA. Apple went absolutely mental in Georgia, including threatening to cancel a $25 million investmentin a historically Black college in Atlanta". Apple won. The way these sleazebag companies get away with such blatant corruption is by using third-party lobbyists, which technically are not employed by the companies in question, so no matter how low and sleazy these lobbyists go, the companies they lobby for can wash their hands in innocence and absolve themselves from any responsibility for the various financial and legal threats levied at underfunded, understaffed local legislatures. Spending a few millions on a local development project or whatever is peanuts for Apple, but a massive boon for a small community somewhere, so Apple pulling out means nothing to Apple, but would massively affect such a community. It's not surprising local legislatures fold. Circling back to the age restriction provision itself - telling stores what they can and cannot sell is an entirely normal thing to do, and happens all the time all over the world. It's why in, say, The Netherlands, supermarkets are only allowed to sell light" alcohol like beer and wine, with hard alcohol moved to separate liquor stores that have to be separate from the supermarket, so age restrictions are easier to enforce. There's also just an infinite number of things you're just not allowed to sell, period. As always, Silicon Valley believes it's a very special snowflake to whom regular, normal, widely accepted rules do not apply. Why shouldn't a store selling gambling applications and similarly addictive and damaging applications have to do the absolute bare minimum to protect minors? Imagine the massive outcry if a Costco or Walmart was found to sell massive amounts of hard liquor to children - why should Silicon Valley companies be treated any differently?

For years now, people believe that their smartphones are listening to their conversations through their microphones, all the time, even when the microphone is clearly not activated. Targeted advertising lies at the root of this conviction; when you just had a conversation with a friend about buying a pink didgeridoo and a flanel ukelele, and you then get ads for pink didgeridoos and flanel ukeleles, it makes intuitive sense to assume your phone was listening to you. How else would Google, Amazon, Facebook, or whatever, know your deepest didgeridoo desires and untapped ukelele urges? The truth is that targeted advertising using cross-site cookies and profile building is far more effective than people think, and on top of that, people often forget what they did on their phone or laptop ten minutes ago, let alone yesterday or last week. Smartphones are not secretly listening to you, and it's not through covert microphone activation that it knows about your musical interests. But then. Media conglomerate Cox Media Group has been pitching tech companies on a new targeted advertising tool that uses audio recordings culled from smart home devices. The existence of this program wasrevealedlate last year. Now, however, 404 Media has also gotten its hands on additional details about the program through a leaked pitch deck. The contents of the deck are creepy, to say the least. Cox's tool is creepily called Active Listening" andthe deckclaims that it works by using smart devices, which can capture real-time intent data by listening to our conversations." After the data is captured, advertisers can pair this voice-data with behavioral data to target in-market consumers," the deck says. The vague use of artificial intelligence to collect data about consumers' online behavior is also mentioned, with the deck noting that consumers leave a data trail based on their conversations and online behavior" and that the AI-fueled tool can collect and analyze said behavioral and voice data from 470+ sources." Lucas Ropek at Gizmodo Looking at the pitch deck in question, you can argue that it's not even referring to smartphones, and that it is incredibly vague - probably on purpose - what active listening" and conversations" are really referring to. It might as well be simply referring to the various conversations on unencrypted messaging platforms, directly with companies, or stuff like that. Smart devices" is also intentionally vague, and could be anything from one of those smart fridges to your smartphone. But you could also argue that yes, this seems to be pretty much referring to listening to our conversations" in the most literal sense, by somehow - we have no idea how - turning on our smartphone microphones, in secret, without iOS or Android, or Apple or Google, knowing about it? It seems far-fetched, but at the same time, a lot of corporate and government programs and efforts seemed far-fetched until some whisteblower spilled the beans. The feeling that your phones are listening to you without your consent, in secret, will never go away. Even if some irrefutable evidence came up that it isn't possible, it's just too plausible to be cast aside.

Since we're on the topic of BSD, what about yet another helpful guide on what to do after first installing OpenBSD? We've covered a few of these already, but more can never hurt, and OpenBSD is a great platform that would suit a lot more of us than you might think. Despite some persistent rumors, installingOpenBSDis both quick and easy on most not too exotic hardware. But once the thing is installed, what is daily life with the most secure free operating system like? Peter N. M. Hansteen This guide by Hansteen focuses primarily on the various basic system management tools you'll be needing to keep OpenBSD up to date after initial installation, and how to install anything else you might need.

After covering setting up your own CDN with both FreeBSD and OpenBSD, it's now time to learn how to set up your own CDN wit NetBSD. This article is a spin-off froma previous post on how to create a self-hosted CDN, but this time we'll focus on usingNetBSD. NetBSD is a lightweight, stable, and secure operating system that supports a wide range of hardware, making it an excellent choice for a caching reverse proxy. Devices that other operating systems may soon abandon, such as early Raspberry Pi models or i386 architecture, are still fully supported by NetBSD and will continue to be so. Additionally, NetBSD is an outstanding platform for virtualization (usingXenorqemu/nvmm) and deserves more attention than it currently receives. Stefano Marinelli All the same from my previous post still applies, and it's a great thing that Marinelli covers all three of the major BSDs (so far). If you want to run your own CDN on BSD, you can now make a pretty informed decision on which BSD best suits your needs.

Thanks to open source, no technology ever has to become obsolete, so long as a community remains to support it. You can sync Newtons and Palm Pilots with modern desktops, download web browsers for long-discontinued operating systems, or connect vintage computers like the Apple IIeto the modern internet via WiFi. Every year, new cartridges are releasedfor old-school video game consoleslike the Nintendo Entertainment System and Game Boy. People keep old software and online platforms alive as well. TheDreamwidthteam forked an old version of the early social networkLiveJournal's source codeand built a community around it. The dial-up bulletin board system softwareWWIVis still maintained and there areplenty of BBSesstill around. Teams are working to restore aspects of early online services like AOL and Prodigy. And you can still use Gopher, the hypertext protocol that was-for a brief period in the early 1990s-bigger than the web. Klint Finley Retrocomputing is about a lot of things, and I feel like it differs per person. For me, it's a little bit of nostalgia, but primarily it's about learning, and experiencing hardware and software I was unable to experience when they were new, either due to high cost or just general unavailability. There's a lot to learn from platforms that are no longer among us, and often it helps you improve your skills with the modern platforms you do still use. The linked article is right: open source is playing such a massive role in the retrocomputing community. The number of open source projects allowing you to somehow use decades-old platforms in conjunction with modern technologies is massive, and it goes far beyond just software - projects like BlueSCSI or very niche things like usb3sun highlights there's also hardware-based solutions for just about anything retro you want to accomplish. And we really can't forget NetBSD, which seems to be the go-to modern operating system for bringing new life to old and retro hardware, as it often runs on just about anything. When I got my PA-RISC workstation, the HP Visualize c3750, I couldn't find working copies of HP-UX, so I, too, opted for NetBSD to at least be able to see if the computer was fully functional. NetBSD is now a tool in my toolbox when I'm dealing with older, unique hardware. Retrocomputing is in a great place right now, with the exception of the ballooning prices we're all suffering from, with even successful mainstay YouTubers like LGR lamenting the state of the market. Still, if you do get your hands on something retro - odds are there's a whole bunch of tools ready for you to make the most of it, even today.

Mouse is an interpreted stack orientated language designed byPeter Grogonoaround 1975. It was designed to be a small but powerful language for microcomputers, similar to Forth, but much simpler. One obvious difference to Forth is that Mouse interprets a stream of characters most of which are only a single character and it relies more on variables rather than rearranging the stack as much. The version for CP/M on theWalnut Creek CDis quite small at only 2k. Lawrence Woodman (2020) Even with very little to no programming experience I can tell that this language looks a lot smaller and more compact than other code I've seen. I'll have to leave it to the actual programmers and developers among the OSNews audience to provide more valuable insight, but I feel like there's definitely something here that'll interest some of you.

Despite reports to the contrary, Microsoft has stated that Recall will not be uninstallable after all. The feature did show up in the Windows Features dialog, but apparently, that was a bug. We are aware of an issue where Recall is incorrectly listed as an option under the Turn Windows features on or off' dialog in Control Panel," says Windows senior product manager Brandon LeBlanc in a statement toThe Verge. This will be fixed in an upcoming update." Tom Warren at The Verge The company is not committing to saying it will not ever be uninstallable, probably because the European Union might have something to say about that. At the very least you'll be able to turn Recall off, but it seems actually removing it might not be possible for a while.

Telegram doesn't hold up to the promise of being private, nor secure. Theend-to-end encryptionis opt-in, only applies to one-on-one conversations and uses a controversial homebrewn' encryption algorithm. The rest of this article outlines some of the fundamentally broken aspects of Telegram. h3artbl33d Telegram is not a secure messenger, nor is it a platform you should want to be on. Chats are not encrypted by default, and are stored in plain text on Telegram's server. Only chats between two (not more!) people who also happen to both be online at that time can be encrypted". In addition, the quotation marks highlight another massive issue with Telegram: its encryption" is non-standard, home-grown, and countless security researchers have warned against relying on it. Telegram's issues go even further than this, though. The application also copies your contacts to its servers and keeps them there, they've got a People nearby" feature that shares location data, and so much more. The linked article does a great job of listing the litany of problems Telegram has, backed up by sources and studies, and these alone should convince anyone to not use Telegram for anything serious. And that's even before we talk about Telegram's utter disinterest in stopping the highly illegal activities that openly take place on its platform, from selling drugs, down to far more shocking and dangerous activities like sharing revenge pron, CSAM, and more. Telegram has a long history of not giving a single iota about shuttering groups that share and promote such material, leaving victims of such heinous crimes out in the cold. Don't use Telegram. A much better alternative is Signal, and hell, even WhatsApp, of all things, is a better choice.

If you're reading this, you did a good job surviving another month, and that means we've got another monthly update from the Servo project, the Rust-based browser engine originally started by Mozilla. The major new feature this month is tabbed browsing in the Servo example browser, as well as extensive improvements for Servo on Windows. Servo-the-browsernow has aredesigned toolbar andtabbed browsing! This includes a slicknew tab page, taking advantage of a new API that lets Servo embedders registercustom protocol handlers. Servo's blog Servo now runs better on Windows, with keyboard navigation now fixed,--outputto PNG also fixed, and fixes for some font- and GPU-related bugs, which were causing misaligned glyphs with incorrect colors on servo.org and duckduckgo.com, and corrupted images on wikipedia.org. Of course, that's not at all, as there's also the usual massive list of improved standards support, new APIs, improvements to some of the developer tools (including massive improvements in Windows build times), and a huge number of fixed bugs.