“Never buy a .online domain” 25 Feb 2026, 11:26 pm

I’ve been a .com purist for over two decades of building. Once, I broke that rule and bought a .online TLD for a small project. This is the story of how it went up in flames.

↫ Tony S.

An absolute horror story about Google’s dominance over the web, in places nobody really talks about. Scary.

You can add a menu bar to KDE title bars with this tool, for some reason 25 Feb 2026, 10:46 pm

Only a few days ago we talked about the concept of client-side decorations, and how more and more desktop environments and operating systems – specifically GNOME and macOS – are putting more and more buttons, menus, and other widgets inside title bars. How about we take this concept a step further?

This hides the AppMenu icon button and draws the menu in the title bar. It also includes a search button to find actions. It works on both X11 and Wayland. On Wayland, GTK apps don’t export the menu in a KDE-friendly way. You need to start them with GDK_BACKEND=x11 environment variable or you can try the experimental appmenu-gtk-module-wayland (GTK3 only).

↫ material-decoration’s GitHub page

So this little tool allows you to add an application’s menu bar (file, edit, view, etc.) to the titlebar of a KDE application. The way it works is that it adds an optional widget to KDE’s System Settings > Colors & Themes > Window Decorations > Configure Titlebar Buttons…, alongside regular staples like close, minimise, maximise, etc. You can then freely add said “menu bar” to the title bar of your applications. There’s some configuration options, too. For instance, you can disable the search button, or turn the entire menu bar into a hamburger menu instead.

It looks weird, and I’m definitely not the target audience for this, but I do find it intriguing. I’ve never seen anything like this before, and I doubt many people will like it since it takes up so much space if you don’t opt to use the hamburger menu option. That being said, I’m fairly sure KDE and Kwin allow you to edit the titlebars of specific applications and specific windows, which does open some interesting possibilities for, say, applications or windows which you always have maximised or whatever.

There’s an AUR package for Arch users, but everyone else will have to build it themselves.

New Windows update adds Sysmon to Windows 25 Feb 2026, 9:22 pm

Microsoft released an optional cumulative update for Windows 11, and for once, it actually includes something many of you might actually like: it adds Sysmon from Sysinternals to Windows natively, so you no longer have to install it manually. Here’s a refresher on what, exactly, Sysmon does.

System Monitor (Sysmon) is a Windows system service and device driver that, once installed on a system, remains resident across system reboots to monitor and log system activity to the Windows event log. It provides detailed information about process creations, network connections, and changes to file creation time. By collecting the events it generates using Windows Event Collection or SIEM agents and subsequently analyzing them, you can identify malicious or anomalous activity and understand how intruders and malware operate on your network. The service runs as a protected process, thus disallowing a wide range of user mode interactions.

↫ Mark Russinovich and Thomas Garnier

After installing the optional cumulative update in question, KB5077241, you can install Sysmon as an optional Windows component. Of course, this is Microsoft we’re talking about, so it’s not quite as straightforward as you’d think. In Windows 11, there’s two places to add optional Windows features, and in the case of Sysmon, you have to go to the old Windows features dialog instead of the new View or edit optional features one. And also, don’t forget to first remove the old Sysmon from Sysinternals in case you have it installed. After installation, run sysmon -i as an administrator to enable the feature.

If you’ve been holding on to a phone for a while, current phones are really disappointing 24 Feb 2026, 10:48 pm

This must be a universal experience at this point for people who aren’t swayed by the latest and greatest marketing hype around new phone models: there’s just nothing out there that fits one’s needs.

When I walked into a phone shop, I expected to witness with amazement how much technology has advanced in the present day compared to my eight-year-old model, and for the power of marketing to mind control me into buying a new phone that would bring all sorts of benefits to my life. But instead, I felt disappointed that I’d be forced to choose between two suboptimal devices, either of which would be a compromise compared to what I already have. I felt frustrated that my OnePlus 5T, which still meets my needs and is working wonderfully (apart from the volume buttons), is being taken from me by the 3G shutdown.

↫ Cadence

It’s remarkable how a market that was once rife with competition and choice, has now been reduced to well I guess I’ll settle for this one then in such a short time frame. There’s barely any competition, the number of device makers in (western or western-adjacent) countries has dropped to two, maybe three, and all of them are making what is essentially the exact same device with only the smallest of differences between them. For most average, normal people, it’s some model by either Samsung or Apple.

There’s definitely more choice once you’re willing to leave local stores (and thus, easy and quick repairs) behind, but most normal people who just want a phone aren’t going to do that. You can also spend like twice or thrice the amount of money to get some foldable thing, but again, if you’re just looking for a bog-standard normal-person phone, that’s not a realistic option either. Smaller devices, headphone jacks, SD card slots – so many things have just disappeared from the face of the earth for most people, something that will definitely come as a huge, unpleasant surprise if you’ve been happy with an older phone that just had those things.

It’s like driving the same car for a decade and needing a new one, but you can only choose between a Toyota and a Volkswagen that look and feel entirely the same. And also the seats are now candles, door handles are gone, and there’s no trunk.

The age-verification trap: verifying user’s ages undermines everyone’s data protection 24 Feb 2026, 8:21 pm

Social media is going the way of alcohol, gambling, and other social sins: Societies are deciding it’s no longer kid stuff. Lawmakers point to compulsive use, exposure to harmful content, and mounting concerns about adolescent mental health. So, many propose to set a minimum age, usually 13 or 16.

In cases when regulators demand real enforcement rather than symbolic rules, platforms run into a basic technical problem. The only way to prove that someone is old enough to use a site is to collect personal data about who they are. And the only way to prove that you checked is to keep the data indefinitely. Age-restriction laws push platforms toward intrusive verification systems that often directly conflict with modern data-privacy law.

This is the age-verification trap. Strong enforcement of age rules undermines data privacy.

↫ Waydell D. Carvalho

The answer to the dangers of social media is not to ban social media use among minors, for a whole variety of reasons. There’s data privacy, as the linked article goes into, but there’s also the fact that for a lot of people, including minors, who live in regressive, backwards environments and/or are victims of abuse, social media is their only support network. Cut them off from social media, and you cut them off from the very people who can save them from further abuse.

The problem isn’t social media in and of itself – it’s profit-seeking social media. Companies like Facebook and TikTok spend billions to hyper-optimise and hyper-target vulnerable people, much like how tobacco companies and drug dealers do, to feed and worsen their addiction because keeping people addicted is how they maximise profits. The solution to the dangers of corporate social media is to strictly regulate their behaviour, something we already do with countless dangerous products and services.

I’m obviously not qualified to come up with specific measures that would need to be taken, but I think we can all agree that whatever corporate social media have been and are doing is dangerous, unethical, should be stopped.

GTK-NoCSD: an LD_PRELOAD library to disable CSDs 23 Feb 2026, 11:25 pm

While Libadwaita applications running in a GNOME desktop environment look great and nicely consistent, they look utterly out of place and jarring when run in Xfce, Pantheon, KDE, and others. The biggest reason for this is GNOME’s insistence on using client-side decorations, which feel at home inside a GNOME environment, but out of place in environments that otherwise do not use them. On top of that, Libadwaita’s/GNOME’s CSDs can interfere with non-GNOME window managers and their functionality, causing a whole host of problems.

But what if you could turn CSDs off?

GTK-NoCSD is an LD_PRELOAD library to disable CSD in GTK3/4, LibHandy, and LibAdwaita apps.

CSD is client side decoration, there is also server side decoration, SSD, both serving as the titlebar of windows. GTK3 adopted CSD, where this thick headerbar is used with application controls embedded.
This continued into the platform library, LibHandy, then into GTK4 and the platform library of that, LibAdwaita. This looks good on Gnome and makes these applications alike, but looks off everywhere else and can potentially break window managers and remove window manager provided functionality.

This library restores the server side decoration, getting back the window manager titlebar, and moves the controls from the CSD to under it, into the window content.

↫ GTK-NoCSD’s Codeberg page

This isn’t the first attempt at such a solution, and certainly won’t be the last, and I’m glad they exist. Do note that if you decide to use this library, any problems or bugs you run into in an application ‘modified’ by it should never be reported to the application’s developer, but to the developer of this library. If you encounter a bug in an application modified by this library, test the application in its unmodified state to ensure it’s actually a bug in the application before reporting it to the application’s developer. Developers who choose to use client-side decorations are not responsible for bugs and issues arising from you removing the CSD.

Keep that in mind.

That being said, whatever pixels appear on your screen is entirely up to you as a user, and you have the right to theme, alter, butcher, or mangle whatever application is running on your computer. If you dislike the way CSDs look and feel on your computer, you can opt to resort to a solution like this one, and that’s entirely fair game. There’s packages for Arch, Fedora, and Gentoo, and of course, you can build it yourself.

As for my personal opinion – well, let’s just say I prefer KDE for many, many reasons, and my disdain for CSDs is certainly one of them. Call me old-fashioned and out-of-touch, but I like the classic distinction between titlebar, menubar, and toolbar.

OpenBSD: anatomy of bsd.rd 23 Feb 2026, 9:46 pm

Every OpenBSD admin has booted bsd.rd at least once — to install, upgrade, or rescue a broken system. But few people stop to look at what’s actually inside that file. It turns out bsd.rd is a set of nested layers, and you can take it apart on a running system without rebooting anything.

That’s what we’ll do here. We’ll go from the raw gzip file all the way down to the miniroot filesystem, exploring each layer with standard tools. Everything is documented in the man pages — we’re just following the trail.

↫ Wesley Mouedine Assaby

What am I supposed to add here?

Microsoft announces ESU program for Windows Server 2016, 10 Enterprise LTSB, and 10 IoT Enterprise 2016 LTSB 21 Feb 2026, 1:59 pm

The regular, consumer version of Windows 10 isn’t the only Windows release reaching or having reached end-of-life, now middling on under the Extended Security Updates program for the many people sticking with the venerable release. Windows 10 Enterprise LTSB 2016 (October 13, 2026), Windows 10 IoT Enterprise 2016 LTSB (October 13, 2026), and Windows Server 2016 (January 12, 2027) are all reaching end-of-life soon, too. On the listed dates, these versions of Windows will receive their final monthly security updates.

As with Windows 10 for consumers, however, there’s a way out: the Extended Security Updates program will also kick in for these versions, offering critical and important security updates, and support relating to just those. The program will be offered for up to three years after official support ends, and won’t be free. For Server 2016 and and Enterprise LTSB 2016, pricing will be $61 per year, but it would double for every year after the first. Pricing for IoT Enterprise 2016 LTSB is available upon request.

Of course, Microsoft urges you to upgrade to newer versions – Windows Server 2025, Windows 11 Enterprise LTSC 2024, and Windows 11 IoT Enterprise LTSC 2024 – but if you’re happy with your current version, you can at least get a three-year reprieve, for a price.

Oracle Solaris 11.4 SRU90 released 21 Feb 2026, 12:09 pm

Despite continuous rumors to the contrary, Oracle is still actively developing Solaris, and it’s been more active than ever lately. Yesterday, the company pushed out another release for customers with the proper support contracts: Oracle Solaris 11.4 SRU90. Aside from the various package updates to bring them up to speed with the latest releases, this new Solaris version also comes with a slew of improvements for ZFS.

ZFS changes in Oracle Solaris 11.4.90 include more flexibility in setting retention properties when receiving a new file system, and adding the ability for zfs scrub and resilver to run before all the blocks have been freed from previous zfs destroy operations. (This requires upgrading pools to the new zpool version 54.)

↫ Alan Coopersmith

You can now also set boot environments to never be destroyed by either manual or automatic means, and more work has been done to prevent a specific type of bug that would accidentally kill all running processes on the system. It seems some programs mistakenly use -1 as a pid value in kill() calls.

Now in 11.4.90, the kill system call was modified to not allow processes to use a pid of -1 unless they’d specifically set a process flag that they intend to kill all processes first, to help with programs that didn’t check for errors when finding the process id for the singular process they wanted to kill.

↫ Alan Coopersmith

There’s many more changes and improvements, of course, and hopefully, we’ll get to see these in the next CBE release as well, so us mere mortals without expensive support contracts can benefit from them too.

Blue-light filters are pure quackery 21 Feb 2026, 7:33 am

I was trading New Year’s resolutions with a circle of friends a few weeks ago, and someone mentioned a big one: sleeping better. I’m a visual neuroscientist by training, so whenever the topic pops up it inevitably leads to talking about the dreaded blue light from monitors, blue light filters, and whether they do anything. My short answer is no, blue light filters don’t work, but there are many more useful things that someone can do to control their light intake to improve their sleep—and minimize jet lag when they’re traveling.

My longer answer is usually a half-hour rant about why they don’t work, covering everything from a tiny nucleus of cells above the optic chiasm, to people living in caves without direct access to sunlight, to neuropeptides, the different cones, how monitors work, gamma curves, what I learned running ismy.blue, corn bulbs, melatonin, finally sharing my Apple Watch & WHOOP stats. What follows is slightly more than you needed to know about blue light filters and more effective ways to control your circadian rhythm. Spoiler: the real lever is total luminance, not color.

↫ Patrick Mineault

And yet, despite a complete and utter lack of evidence blue-light filters do anything at all, even the largest technology companies in the world peddle them without so much as blinking an eye. It’s pure quackery, and as always, we let them get away with it.

Windows 11 26H1 will be Snapdragon-specific 19 Feb 2026, 9:27 pm

As if keeping track of whatever counts as a release schedule for Windows wasn’t complicated enough – don’t lie, you don’t know when that feature they announced is actually being released either – Microsoft is making everything even more complicated. Soon, Microsoft will be releasing Windows 11 26H1, but you most likely won’t be getting it because it’s strictly limited to devices with Qualcomm’s new Snapdragon X2 Series processors.

The only way to get this version of Windows is to go out and buy a device with a Snapdragon X2 Series processor. Windows 11 26H1 will not be made available to any other Windows 11 users, so nobody will be able to upgrade to it. Furthermore, users of Windows 11 26H1 will not be able to update to the “feature update” for users of Windows 11 24H2 and 25H2, the regular Windows versions, planned for late 2026. Instead, Microsoft promises there will be an upgrade path for 26H1 users in a “future” release of Windows. Why?

Devices running Windows 11, version 26H1 will not be able to update to the next annual feature update in the second half of 2026. This is because Windows 11, version 26H1 is based on a different Windows core than Windows 11, versions 24H2 and 25H2, and the upcoming feature update. These devices will have a path to update in a future Windows release.

↫ AriaUpdated at the Windows IT Pro Blog

The same thing happened when Qualcomm releases its first round of Snapdragon processors for Windows, as Windows 24H2 was also tied to this specific platform. It seems Microsoft is forced to have entirely separate and partially incompatible codebases just to support Snapdragon processors, which must be a major pain in the ass to deal with. Considering Windows on ARM hasn’t exactly been a smashing success, one may wonder how long Microsoft remains willing to make such exceptions for a singular chip.

Undo in Vi and its successors 19 Feb 2026, 1:06 am

So vi only has one level of undo, which is simply no longer fit for the times we live in now, and also wholly unnecessary given even the least powerful devices that might need to run vi probably have more than enough resources to give at least a few more levels of undo. What I didn’t know, however, is that vi’s limited undo behaviour is actually part of POSIX, and for full compliance, you’re going to need it. As Chris Siebenmann notes, vim and its derivatives ignore this POSIX requirement and implement multiple levels of undo in the obviously correct way.

What about nvi, the default on the BSD variants? I didn’t know this, but it has a convoluted workaround to both maintain POSIX compatibility and offer multiple levels of undo, and it’s definitely something.

Nvi has opted to remain POSIX compliant and operate in the traditional vi way, while still supporting multi-level undo. To get multi-level undo in nvi, you extend the first ‘u’ with ‘.’ commands, so ‘u..’ undoes the most recent three changes. The ‘u’ command can be extended with ‘.’ in either of its modes (undo’ing or redo’ing), so ‘u..u..’ is a no-op. The ‘.’ operation doesn’t appear to take a count in nvi, so there is no way to do multiple undos (or redos) in one action; you have to step through them by hand. I’m not sure how nvi reacts if you want do things like move your cursor position during an undo or redo sequence (my limited testing suggests that it can perturb the sequence, so that ‘.’ now doesn’t continue undoing or redoing the way vim will continue if you use ‘u’ or Ctrl-r again).

↫ Chris Siebenmann

Siebenmann lists a few other implementations and how they work with undo, and it’s interesting to see how all of them try to solve the problem in slightly different ways.

F9: an L4-style microkernel for ARM Cortex-M 18 Feb 2026, 10:08 pm

F9 is an L4-inspired microkernel designed for ARM Cortex-M, targeting real-time embedded systems with hard determinism requirements. It implements the fundamental microkernel principles—address spaces, threads, and IPC, while adding advanced features from industrial RTOSes.

↫ F9 kernel GitHub page

For once, not written in Rust, and comes with both an L4-style native API and a userspace POSIX API, and there’s a ton of documentation to get you started.

Windows 11’s new MIDI framework delivers MIDI 2.0 18 Feb 2026, 9:54 pm

It’s been well over a year since Microsoft unveiled it was working on bringing MIDI 2.0 to Windows, and now it’s actually here available for everyone.

We’ve been working on MIDI over the past several years, completely rewriting decades of MIDI 1.0 code on Windows to both support MIDI 2.0 and make MIDI 1.0 amazing. This new combined stack is called “Windows MIDI Services.”

The Windows MIDI Services core components are built into Windows 11, rolling out through a phased enablement process now to in-support retail releases of Windows 11. This includes all the infrastructure needed to bring more features to existing MIDI 1.0 apps, and also support apps using MIDI 2.0 through our new Windows MIDI Services App SDK.

↫ Pete Brown and Gary Daniels at the Windows Blogs

This is the kind of work users of an operating system want to see. Improvements and new features like these actually have a meaningful, positive impact for people using MIDI, and will genuinely give them them benefits they otherwise wouldn’t get. I won’t pretend to know much about the detailed features and improvements listed in Microsoft’s blog post, but I’m sure the musicians in the audience will be quite pleased.

Whomever at Microsoft was responsible for pushing this through, managing this team, and of course the team members themselves should probably be overseeing more than just this. Less “AI” bullshit, more of this.

KDE Plasma 6.6 released 18 Feb 2026, 12:07 am

KDE Plasma 6.6 has been released, and brings with a whole slew of new features. You can save any combination of themes as a global theme, and there’s a new feature allowing you to increase or decrease the contrast of frames and outlines. If your device has a camera, you can now scan Wi-F settings from QR codes, which is quite nice if you spend a lot of time on the road.

There’s a new colour filter for people who are colour blind, allowing you to set the entire UI to grayscale, as well as a brand new virtual keyboard. Other new accessibility features include tracking the mouse cursor when using the zoom feature, a reduced motion setting, and more. Spectacle gets a text extraction feature and a feature to exclude windows from screen recordings. There’s also a new optional login manager, optimised for Wayland, a new first-run setup wizard, and much more.

As always, KDE 6.6 will find its way to your distribution’s repositories soon enough.

SvarDOS: an open-source DOS distribution 17 Feb 2026, 11:30 pm

SvarDOS is an open-source project that is meant to integrate the best out of the currently available DOS tools, drivers and games. DOS development has been abandoned by commercial players a long time ago, mostly during early nineties. Nowadays it survives solely through the efforts of hobbyists and retro-enthusiasts, but this is a highly sparse and unorganized ecosystem. SvarDOS aims to collect available DOS software and make it easy to find and install applications using a network-enabled package manager (like apt-get, but for DOS and able to run on a 8086 PC).

↫ SvarDOS website

SvarDOS is built around a fork of the Enhanced DR-DOS kernel, which is available in a dedicated GitHub repository. The project’s base installation is extremely minimal, containing only the kernel, a command interpreter, and some basic system administration tools, and this basic installation is compatible down to the 8086. You are then free to add whatever packages you want, either from local storage or from the online repository using the included package manager. SvarDOS is a rolling release, and you can use the package manager to keep it updated.

Aside from a set of regular installation images for a variety of floppy sizes, there’s also a dedicated “talking” build that uses the PROVOX screen reader and Braille ‘n Speak synthesizer at the COM1 port. It’s rare for a smaller project like this to have the resources to dedicate to accessibility, so this is a rather pleasant surprise.