It’s no secret that I am very worried about the future of Firefox, and the future of Firefox on Linux in particular. I’m not going to rehash these worries here, but suffice to say that with Mozilla increasingly focusing on advertising, Firefox’ negligible market share, and the increasing likeliness that the Google Search deal, which accounts for 85% of Mozilla’s revenue, will come to an end, I have little faith in Firefox for Linux remaining a priority for Mozilla. On top of that, as more and more advertising nonsense, in collaboration with Facebook, makes its way into Firefox, we may soon arrive at a point where Firefox can’t be shipped by Linux distributions at all anymore, due to licensing and/or idealogical reasons.

I’ve been warning the Linux community, and distributions in particular, for years now that they’re going to need an alternative default browser once the inevitable day Firefox truly shits the bed is upon us. Since I’m in the middle of removing the last few remaining bits of big tech from my life, I figured I might as well put my money where my mouth is and go on a small side quest to change my browser, too. Since I use Fedora KDE on all my machines and prefer to have as many native applications as possible, I made the switch to KDE’s own browser: Falkon.

What is Falkon?

Falkon started out as an independent project called QupZilla, but in 2017 it joined the KDE project and was renamed to Falkon. It uses QtWebEngine as its engine, which is Qt’s version of the Chromium engine, but without all the services that talk to Google, which are stripped out. This effectively makes it similar to using de-Googled Chromium. The downside is that QtWebEngine does lag behind the current Chromium version; QtWebEngine 6.8.0, the current version, is Chromium 122, while Chromium 133 is current at the time of writing.

The fact that Falkon uses a variant of the Chromium engine means websites just work, and there’s really nothing to worry about when it comes to compatibility. Another advantage of using QtWebEngine is that the engine is updated independently from the browser, so even if it seems Falkon isn’t getting much development, the engine it uses is updated regularly as part of your distribution’s and KDE’s Qt upgrades.

The downside, of course, is that you’re using a variant of Chromium, but at least it’s de-Googled and entirely invisible to the user. It’s definitely not great, and it contributes to the Chromium monoculture, but I can also understand that a project like Qt isn’t going to develop its own browser engine, and in turn, it makes perfect sense for KDE, as a flagship Qt product, to use it as well. It’s the practical choice, and I don’t blame either of them for opting for what works, and what works now – the reality is that no matter what browser you’re choose, you’re either using a browser made by Google, or one kept afloat by Google. Pick your poison.

It’s not realistic for Qt or KDE to develop their own browser engine from scratch, so opting for the most popular and very well funded browser engine and strip out all of its nasty Google bits makes the most sense. Yes, we’d all like to have more capable browser engines and thus more competition, but we have to be realistic and understand that’s not going to happen while developing a browser engine is as complex as developing an entire operating system.

Falkon’s issues and strengths

While rendering websites, compatibility, and even performance is excellent – as a normal user I don’t notice any difference between running Chrome, Firefox, or Falkon on my machines – the user interface and feature set is where Falkon stumbles a bit. There’s a few things users have come to expect from their browser that Falkon simply doesn’t offer yet, and those things needs to be addressed if the KDE project wants Falkon to be a viable alternative to Firefox and Chrome, instead of just a languishing side project nobody uses.

The biggest thing you’ll miss is without a doubt support for modern extensions. Falkon does have support for the deprecated PPAPI plugin interface and its own extensions system, but there’s no support for the modern extensions API Firefox, Chrome, and other browsers use. What this means for you as a user is that there are effectively no extensions available for Falkon, and that’s a huge thing to suddenly have to do without. Luckily, Falkon does have adblock built-in, including support for custom block lists, so the most important extension is there, but that’s it.

There’s a very old bug report/feature request about adding support for Firefox/Chrome extensions, which in turn points to a similar feature request for QtWebEngine to adopt support for such extensions. The gist is that for Falkon to get support for modern Firefox and Chrome extensions, it will have to go through QtWebEngine and thus the Qt project. While I personally can just about get by with using the BitWarden application (instead of the extension) and the built-in adblock, I think this is an absolute most for most people to adopt Falkon in any serious numbers. Most people who would consider switching to a different browser than Chrome or Firefox are going to need extensions support.

The second major thing you’ll miss is any lack of synchronisation support. You won’t be synchronising your bookmarks across different machines, let alone open tabs. Of course, this extends to mobile, where Falkon has no presence, so don’t expect to send your open tabs from your phone to your desktop as you get home. While I don’t think this is as big of an issue as the lack of modern extensions, it’s something I use a lot when working on OSNews – I find stories to link to while browsing on my phone, and then open them on my desktop to post them through the tab sharing feature of Firefox, and I really miss it. There’s a longstanding feature request for this one, too, and I suggested something like this could possibly be made to work using KDE Connect.

From here on out, the shortcomings and issues I’ve personally noted fall in the category of minor issues and bugs, mostly stemming from what seems to be a lack of attention in the development of Falkon’s UI. For instance, it’s one of the very few official KDE applications left that hasn’t received the Plasma 6 overhaul to reduce the number of frames, tidy up the spacing a bit, and generally give it a bit of a spruce. This makes Falkon look a bit outdated compared to the rest of your KDE desktop (but not massively so), while also containing some odd UI elements that are quite non-standard. I filed a bug report/feature request about this.

Even smaller bugs are random things like the cursor often not changing to a hand cursor when hovering over a link, favicons in the bookmarks toolbar not updating consistently, or (more annoyingly) screens and laptops going to sleep modes while video is playing. I’m no developer so don’t put too much faith in what I’m about to say, but it feels like things like these are not the most complicated bugs to handle, and looking at the lack of activity in the bug tracker for Falkon, it feels like even within KDE itself, Falkon isn’t exactly used a lot. This is a shame, because other than the issues I’ve mentioned, Falkon is remarkably full-featured and capable.

Think of any feature a modern browser has, and Falkon probably has it. There’s a password manager built-in that can use both encrypted and non-encrypted databases as well as Kwallet, a Greasemonkey-compatible extension, web inspector tools, extensive privacy controls, spell check, address bar search with support for every search engine under the sun, advanced tab management, and much, much more.

And of course, it has a Qt/KDE graphical user interface that integrates better with KDE, both visually and behaviourally, than any other browser – including support for things like the global menubar widget, something Firefox does not support (but Chrome weirdly does). This means Falkon will respect your font choices, colour settings, light and dark mode options, and everything else. Where Chrome and Firefox feel like they’re not at all at home in KDE (or GNOME, for that matter), Falkon is just another KDE application, and looks and feels almost entirely integrated.

Combine all of this with the excellent rendering and performance thanks to QtWebEngine, and Falkon is simply a far more capable and solid browser than most people seem to know. I’ve switched all my machines to it a little over a week ago or so now, and for me, the benefits of having a truly native, KDE-first browser far outweigh some of the shortcommings I’ve had to deal with. Relying on the BitWarden application instead of the extension is a bit more cumbersome, but not massively so. No longer having tab sharing sucks, but since switching to GrapheneOS and its Vanadium browser, I had to give that up anyway.

KDE is on track

My goal with writing this article, talking about Falkon on Mastodon, and filing bug reports – I’ve got a few more extremely minor niggles coming – is to let people know that Falkon is in a far better, more usable, and capable state than most people know. Hopefully, this article will get a few more people to try it out, file bug reports, or even become a contributor to this very capable but seemingly a bit of a neglected official KDE application.

At this rate, I give Firefox (the Linux version in particular) a few more years, at most, before its various advertising and other anti-user additions make it incompatible with the idealogical and license requirements of most Linux distributions, and KDE should be ready for when this day comes. I don’t have any illusions about my influence here – OSNews is relatively small and the inertia to switch browsers is very real and understandable – but I think that with how good Falkon already is, KDE is much closer to not having to rely on Firefox or Chrome than even KDE itself seems to know.

And with how things are going, that’s very good news.

Back in December 2019, Microsoft finally killed off Windows 10 Phone as it announced the end of support. The company’s grand plans with Lumia and Windows Phones sadly never became the success it needed to be in order to be able to compete with the likes of Android or iOS.

Thus Windows 11 Phone never became a real official thing outside of concepts. However, there is a free unofficial way that makes it possible, albeit the experience may not totally be free from flaws. Dubbed Project Renegade, the mod enables users to try Windows 11 on Qualcomm Snapdragon phones, among other devices.

↫ Sayan Sen at Neowin

Windows Phone 7 and 8 were amazing, and probably my favourite mobile platform of all time. I’m still sad that the duopoly made it impssible even for Microsoft to gain a foothold, because their efforts definitely deserved it. They didn’t just blindly copy Android or iOS, but came up with a truly original, unique, and in my view, superior mobile operating system, and in a fair market, they would’ve been rewarded for it, and Windows Phone would have a perhaps small, but profitable segment of the market.

In the vein of Bernie can still win, I still have this faint belief that Microsoft hasn’t completely given up on the smartphone market. Now that they’re serious about Windows on ARM, they might use it as sneaky way to get application developers on board, so that their applications are ready for the big Surface Phone a few years from now, complete with Windows Phone-inspired features and UI. I know this won’t happen, but let me enjoy my non-existent future, please.

I don’t want to rely on big tech anymore, but I might make an exception for an up-to-date Windows Phone. I’m only human.

Every time a new Redox monthly report comes out, I’m baffled by the fact we’ve apparently rounded another month. They just keep on coming and going, don’t they? And I even turned 40 this 1 December, so it hits even harder this time. I’m now as old as I remember my parents were in some of my oldest memories, and now I’ve got two kids of my own. Wild. Time isn’t supposed to move this fast, and I strongly advise the Redox team to stop this madness.

Anyway, this month also saw the release of the 4th alpha of system76’s new COSMIC Linux desktop environment, and the parts of COSMIC available on Redox were updated to reflect that. This past months also saw a major milestone: the RISC-V version of Redox running in an emulator on the x86-64 version of Redox. That’s quite the feat, and highlights just how capable Redox has become in such a short time. There’s also the usual list of kernel, driver, and relibc improvements, as well as additional Rust programs ported to Redox.

Also highlighted in this report: a video detailing how to build Redox under Windows Subsystem for Linux. This could be a great avenue for operating system developers who use Windows to get their feet wet at building Redox on their own systems.

Today, we are announcing the availability of Vanir, a new open-source security patch validation tool. Introduced at Android Bootcamp in April, Vanir gives Android platform developers the power to quickly and efficiently scan their custom platform code for missing security patches and identify applicable available patches. Vanir significantly accelerates patch validation by automating this process, allowing OEMs to ensure devices are protected with critical security updates much faster than traditional methods. This strengthens the security of the Android ecosystem, helping to keep Android users around the world safe.

↫ Google Security Blog

Google makes it clear this tool can easily be adapted for other avenues too – it’s not locked into only working with Android and Java/C/C++. Since it’s now open source, anyone can contribute to it and make it compatible – for lack of a better term – with other platforms and programming languages as well.

This is my hobby operating system written in C++. Currently supports x86_64 and i686 architectures.

↫ Banan-OS git page

A hobby operating system as a learning experience, but for once not written in Rust, which in and of itself makes it more unique than you’d think. Despite being mostly a one-person hobby project, it’s ticked quite a few boxes already: SMP, network stack, copy-on-write memory, ELF loading, NVME and ATA support, PS/2 and USB peripheral support, a basic GUI, and a lot more.

Contributions are welcomed, too.

VEKOS is an experimental operating system written in Rust that focuses on verification and security at its core. This is the first alpha release (v0.0.1) that demonstrates the basic architecture and key features of the system.

↫ VEKOS GitHub page

Hobby and experimental operating systems written in Rust are not exactly a novel concept, but that doesn’t mean each new one that comes up isn’t cool. This one is still in its very early stages, but focuses on something quite interesting: every filesystem and memory operation is cryptographically verified using a proof system. It’s already got basic file system operations, signal handling and a scheduler, a shell, and more.

Contributions are welcomed.

14.2-RELEASE now includes OCI-compatible images, and the Podman toolkit on FreeBSD is ready to use them, on both amd64 and arm64 systems.

↫ Dave Cottlehuber

This article from Dave Cottlehuber goes into more detail about the OCI-compatible FreeBSD images and how to use them.

If you were secretly hoping Microsoft would lower the system requirements for Windows 11 so you could upgrade your or your family’s Windows 10 machines to Windows 11, you’re going to be in for some bad news. In a blog post, Microsoft detailed that its most stringent Windows 11 requirement – the Trusted Platform Module (TPM) 2.0 – is here to stay and crucial to the future of Windows.

By instituting TPM 2.0 as a non-negotiable standard for the future of Windows, we elevate the security benchmark. It allows you and us to better align with the growing need for formidable data protection in the modern digital sphere.

[…]

In conclusion, TPM 2.0 is not just a recommendation—it’s a necessity for maintaining a secure and future-proof IT environment with Windows 11. And it’s an important part of the larger Zero Trust strategy, alongside Secure Boot, Credential Guard, and Windows Hello for Business.

↫ Steven Hosking at the Windows IT Pro Blog

So no, if you had the hope Microsoft would lower Windows 11’s system requirements in the face of the oncoming end of support deadline for the 60% of Windows users still using Windows 10, your hope has just been dashed. A more likely outcome here is that as the deadline grows closer, Microsoft will extend the deadline by another year, and if needed another, because leaving 60% of users without security updates and little to no path to upgrade is not going to be a good look for the marketing and legal departments.

If you really do want to upgrade to Windows 11, there’s a few options. There’s the enterprise-focused Windows 11 LTSC 2024 release, which does not require a TPM 2.0, regarding it as an optional feature instead. On top of that, LTSC is much more bare-bones, shipping without much of the stuff many of us more nerdy users aren’t interested in anyway. The big downside is that getting your hands on a legal copy of LTSC will be difficult, as it’s only available to volume licensing customers, which you most likely are not. Of course, you shouldn’t give a shit about Microsoft’s rules, so you can always use unapproved methods of getting a license.

Another option is the one I took for my parts-bin Windows 11 PC which I only use for League of Legends: I bought a cheap TPM 2.0 module from eBay, slotted it into my motherboard, and was on my merry way. Due to League of Legends’ required rootkit, a TPM 2.0 module is needed, so a few euros and days waiting later, I was ready to go. Do make sure you get the right type of TPM 2.0 module for your motherboard, as they’re not universally compatible.

The final option is to use one of the few remaining ways to circumvent Windows 11’s system requirements, which are sadly dwindling with every major update. Right now that means using a tool like Flyby11, which uses the Windows Server installer to bypass Windows 11’s system requirements. We’ll have to wait and see for how long that trick remains possible.

This is a bit of an odd few days for Intel. Mere days after the board ousted its CEO Pat Gelsinger, once heralded as the chip giant’s messiah, they’re today launching two brand new desktop graphics cards. They’re aimed at the more budget-oriented consumer, and might very well be the last discrete graphics cards Intel makes, since this is one of the product lines on the chopping block.

Intel’s next — and possibly last — desktop graphics cards will begin arriving in just 10 days. Right on cue, the company has announced the budget $249 Arc B580 and $219 Arc B570, shipping December 13th and January 16th, respectively, as the “best-in-class performance per dollar” options in the GPU market.

They’re based on the same Xe2 “Battlemage” GPU architecture you’ll find in Intel’s Lunar Lake laptop chips but with more than double the graphics cores, up to 12GB of dedicated video memory, and up to 190W of power compared to their limited laptop forms — enough power to see the B580 slightly beat Nvidia’s $299 RTX 4060 and AMD’s $269 RX 7600, according to Intel’s benchmarks, but sometimes still trading blows.

↫ Sean Hollister at The Verge

As for Gelsinger’s dismissal, it seems the board forced him out after being frustrated with the slow progress the company was making in its turnaround. The fact that a finance person and a marketing person will together be interim CEOs seems to indicate the board is more interested in quick profit than a long-term turnaround, and with companies like Qualcomm being interested in acquiring Intel, the board’s short-term mentality might be winning out, and ousting Gelsinger is just paving the way for selling off parts of Intel until there’s nothing left.

Who knows, I might be reading way too much into all of this, but it feels like expecting an organisation as complex as a high-end processor makers to turn itself around in just a few years is incredibly shortsighted, and you’d think board members at Intel would understand that. If the goal is to maintain Intel as a separate, profitable entity making some of the world’s fastest processors, you’re going to need to give a CEO and leadership team more than just a few years to turn the ship around.

Within a few years we’ll know the board’s true intentions, but I wouldn’t be surprised to see Intel being sold for parts over the coming years.

FreeBSD 14.2 has been released, and as the version number suggests, this isn’t a major release with huge changes. Still, it does bring support for downloading and installing necessary firmware packages after installation, the latest versions of OpenZFS and OpenSSL, and much more.

FreeBSD 14.2 is available for the main architectures it supports – x86, PowerPC/POWER, ARM, and RISC-V, and can be downloaded from the usual location.

This is the Hall Research Technologies SC-VGA-2, sold as a “VGA/HDTV Video Processor.” In addition to slicing, dicing and pureeing, apparently, it will take any of a bundle of input formats and both rescale and resample them on the fly into the VGA or HDTV signal you desire, including 60Hz rates. This came from a seller specializing in teleprompter equipment and Hall still sells an HDMI version with additional resolutions … for around US$500. However, this or the slightly newer SC-VGA-2A and SC-VGA-2B are all relatively common devices and found substantially cheaper used. Let’s try it out and show some sample output, including those delicious NeXTSTEP system messages and some ST grabs.

↫ Cameron Kaiser

With the obscurity of some of the hardware Cameron Kaiser details on his website, I’m not surprised he has some seriously unique needs when it comes to taking screengrabs. He couldn’t very well not take the device apart, and inside it appears to be a system with two small processors, at least one of which is an Intel 8051 8bit microcontroller. Kaiser goes into his usual great detail explaining and showing how the device works.

If you’ve got unique screengrabbing needs, this might be of interest to you.

Within in the last release cycle we worked on adding and extending the support for the i.MX8MP SoC as also found in one of the SoM options for the MNT Pocket Reform and are happy to show-case a first preview version of Sculpt running on this handy computing device.

↫ Josef Söntgen

If you have a Pocket Reform – I reviewed its bigger sibling earlier this year – you can now run Genode on it. Not everything is working flawlessly yet – most notably audio and NVMe need work – but networking is operational, so you can actually browse the web. I’m not sure how much overlap there is between Genode users and Pocket Reform owners, but at least both groups now know it’s an option.

The Cinnamon Desktop, the GTK desktop environment developed by the Linux Mint project, has just released version 6.4. The focus of this release is on nips and tucks in the default theme, dialogs, menus, and other user interface elements. They seem to have taken a few pages out of GNOME’s book, especially when it comes to dialogs and the OSD, which honestly makes sense considering Cinnamon is also GTK and most Cinnamon users will be running a ton of GNOME/Libadwaita applications.

There’s also a new night light feature to reduce eyestrain, vastly improved options for power profiles and management, and more. Cinnamon 6.4 will be part of Linux Mint’s next major release, coming in late December, but is most likely already making its way to various other distributions’ repositories.

Recently, I’ve been moving away from macOS to Linux, and have settled on using KDE Plasma as my desktop environment. For the most part I’ve been comfortable with the change, but it’s always the small things that get me. For example, the Mail app built into macOS provides an “Unsubscribe” button for emails.

[…]

Apparently this is also supported in some webmail clients, but I’m not interested in accessing my email that way. Unfortunately, I haven’t found an X11 or Wayland email client that supports this sort of functionality, so I decided to implement it myself. And anyway, I’m trying out Kontact for my mail at the moment, which supports plugins. So why not use this as an opportunity to build one?

↫ datagirl.xyz

Writing a Kmail plugin like this feels a bit like an arcane art, because the process is not documented as well as it could be, and I doubt that other than KDE developers themselves, very few people are interested in writing these kinds of plugins. In fact, I can’t find a single one listed on the KDE Store, and searching around I can’t find anything either, other than the ones that come with KDE. It seems like this particular plugin interface is designed more to make it easy for KDE developers to extend and alter Kmail than it is for third parties to do so – and that’s fine.

Still, this means that if some third party does want to write such a plugin, there’s some sleuthing and hacking to be done, and that’s exactly the process this article details. In the end, we end up with a working unsubscribe plugin, with the code on git so others can learn from it. While this may not interest a large number of people, it’s vital to have information like this out on the web for those precious few to find – so excellent work.