Curious about what’s new? I’ve covered the key features and changes in this major release.

If you’re currently on Ubuntu 24.04 or even 25.10, you probably have a few questions about upgrading. Should you do it now? Is it worth it? I’ve addressed those in a dedicated article.

On a related note, Fedora 44 faced another delay but is now expected to release tomorrow, April 24.

Here are other highlights of this edition of FOSS Weekly:

• A young Polish developer fixing 20 year old Linux bug.
• A new privacy-first cloud service.
• Russian CPUs being dropped from Linux.
• And other Linux news, tips, and, of course, memes!

📰 Linux and Open Source News

Linux 7.1 is dropping support for Baikal SoCs, the Russian ARM-based processors that were intended to give Russian state enterprises a domestic alternative to Intel and AMD.

Cal.com, the open source Calendly alternative, has gone closed source. The stated reason is that AI can now scan public repos and find exploitable vulnerabilities far faster than before.

A 20-year-old bug in the Enlightenment E16 window manager, introduced in 2006, was found and fixed this month by a 21-year-old graduate student who daily drives the 1999-era window manager.

MZLA Technologies, the Mozilla subsidiary behind Thunderbird, has launched Thunderbolt, an open source, self-hostable AI client aimed at organizations that can't send sensitive data to third-party AI services.

Elsewhere in the world of Mozilla, Firefox's new mascot Kit generated more drama than any browser mascot should've. A Reddit post used they/them pronouns to introduce the cartoon Firefox character; someone noticed a few weeks later, and the predictable cycle followed.

And some positive news. After months of advocacy by System76, Colorado's age verification bill is set for an amendment to exclude open source. At least that's what it looks like for now.

🧠 What We’re Thinking About

If you're already using Tuta for email and calendar and have been wondering where the cloud storage was, it's now in closed beta. Tuta Drive uses the same post-quantum hybrid encryption as the rest of the suite, is hosted in Germany, and is zero-knowledge by design.

Is the OS-level age verification all about protecting children? Theena does not think so and expresses his opinions in this article.

🧮 Linux Tips, Tutorials, and Learnings

Chapter 7 of our Terminal Basics series covers everything you need to know about the cp command for copying single files, multiple files, renaming during a copy, using -r for directories, and handling overwrites safely with -n and -i.

If your Linux Mint desktop feels a bit plain and you have RAM to spare, we have covered nine Cinnamon extensions and built-in effects worth trying for anyone who wants to make the desktop feel a bit more alive.

Compiling your own kernel sounds intimidating, but it's mostly a long sequence of well-defined steps. The journey involves fetching and verifying the source, configuring with menuconfig, building and installing modules, headers, and the kernel itself.

Markdown has become essential. From Git repositories to AI skills to personal knowledge base, knowing the basics of Markdown helps a lot.

👷 AI, Homelab and Hardware Corner

Linux gamers rejoice! A gaming console has been announced that runs an Arch-based distro.

✨ Apps and Projects Highlights

Managing a handful of containers from the terminal is fine until it isn't. Pods is a clean Adwaita-native GUI for Podman and Docker that handles the everyday tasks.

📽️ Videos for You

And I share the new features in Ubuntu 26.04 in this video along with my opinions on (some of) them. Please watch it here.

💡 Quick Handy Tip

In many Linux terminal emulators like GNOME Terminal, Ptyxis, etc. You can press CTRL+SHIFT+F to open a search interface for going through your scrollback history. This typically contains options for matchcase, whole words, and regular expressions.

🎋 Fun in the FOSSverse

Take your container knowledge for a test with this members-only puzzle.

Who said that? Let me enlighten you. 🧐

🗓️ Tech Trivia: On April 21, 1988, Tandy Corporation announced it would clone IBM's PS/2, which was made possible only because IBM had opened up the license to its proprietary MCA bus patents after years of trying to lock competitors out.

The PS/2 was IBM's attempt to retake control of the PC market it had accidentally given away by publishing open hardware specs in 1981. It failed completely.

Within four years IBM was a minor player in its own market, and by 2005 it had exited PC manufacturing entirely, selling the division to Lenovo.

🧑‍🤝‍🧑 From the Community: FOSSers are deliberating whether CAMM2 memory will be the next thing in computer hardware.

I have tried to answer those frequently asked questions about Ubuntu 26.04 here. I hope it helps clear your doubts if you had any. And if you still have questions, feel free to ask in the comment section below.

What are the system requirements for Ubuntu 26.04?

Ubuntu 26.04 requires a 2 GHz dual core processor or better, a minimum of 6 GB RAM and at least 25 GB of free disk space. These stats for the default GNOME version. KDE and Xfce flavors may work with 4 GB RAM.

If you are dual booting it with Windows, you should at least give it 50 GB or even 100 GB. 25 GB will be filled way too soon.

How long will Ubuntu 26.04 be supported?

It is a long-term support (LTS) release and like any LTS release, it will be supported for five years. Which means that Ubuntu 26.04 will get security and maintenance updates until April 2031. Flavors get supported for three years only.

You can enable Ubuntu Pro, free for personal use, and get extended support for five more years. This will give you just security and maintenance updates; new features and software versions will mostly not be available.

There is also the option for legacy add-on for Ubuntu Pro that will add five more years to extend the life.

These extensions are suitable for people who do not seek new features as much and happy to have a computer that works for most of their day to day need of browsing internet, manage photos and document etc.

There are other options in "Ubuntu 26.04"?

Ubuntu has various flavors based on the desktop environments they provide. Kubuntu is with KDE, Lubuntu is with LXQt, Xubuntu is with Xfce desktop. I hope you are familiar with the concept of desktop environments. This is what determines how your Linux system looks by default.

Where can I download Ubuntu 26.04?

You can get the ISO image of Ubuntu 26.04 GNOME from its website. You have both direct download and torrent options. Other official flavors will be available on their official websites.

Note: if you don't see the option to download Ubuntu 26.04, you can get it from the daily build page.

Can I download Ubuntu 26.04 via torrent?

Yes. you can. If you have an inconsistent or slow internet, you can download Ubuntu ISO image via torrent as well. Just go to the Ubuntu download page and look for alternative downloads. Scroll down a bit and you’ll see the torrent options.

How can I install Ubuntu 26.04?

Just like any other version. You download the ISO, make a live USB and use it to install Ubuntu on your system. You can dual boot it as well. The detailed steps are demonstrated in our Ubuntu installation guide.

Can I install KDE or some other desktop environment on Ubuntu 26.04?

Yes, you can. Linux gives you the flexibility to install the desktop environment of your choice. However, I recommend that if you have a fresh Ubuntu install where you don't have important data, it is better to install the official flavor instead. This is because some times, desktop environment elements conflict with each other. So if you want KDE, go for Kubuntu.

I am already using Ubuntu. Can I upgrade to Ubuntu 26.04?

Yes. Ubuntu allows you to upgrade from one version to the next or one long-term support (LTS) version to next. If you are already using Ubuntu 24.04 LTS or 25.10, you will have the option to upgrade to Ubuntu 26.04 LTS.

If you are using Ubuntu 22.04 LTS, you'll have to upgrade to 24.04 LTS first and then upgrade to 26.04.

Please check your Ubuntu version. If you are using any version other than 22.04, 24.04 or 25.10, chances are that it has reached end of life. A fresh install will make more sense.

Why don't I see the upgrade to 26.04 option?

A new Ubuntu release is gradually rolled out to users. You'll see it eventually, just keep your system upgraded.

If you cannot wait, you can force update manager to look for "development release" and that should give you the option to upgrade to 26.04 immediately.

Should I wait or upgrade to Ubuntu 26.04 right away?

In my experience, a new Ubuntu release often brings up bugs and issues that have gone unnoticed in the testing phase. If you easily get annoyed and don't want to troubleshoot, I would advise upgrading for a few week from the release. If you want to take it even more slow and comfortable, you can wait till the first point release of Ubuntu 26.04.1. Most of the discovered bugs are fixed by then.

Do I need to back up before upgrade?

Upgrading from existing Ubuntu version to new version is generally safe. In my 17 years of Ubuntu usage, I have never experienced a broken system while upgrading it.

That said, it is not impossible to encounter issues. It's rare but rare events do happen. So, if you have important data, make a backup with timeshift or simply copy the data on an external disk.

Before upgrading, if these things have not been backed up, I copy most of the contents from the home directory to my SanDisk external SSD (partner Amazon link) shown in the picture below. SSD with USB 3 or Thunderbolt have very good copying speed.

Should I upgrade to 26.04 or do a fresh install?

That is up to your technical abilities and convenience. Personally, I feel that a fresh install works better, specially if you have been upgrading to newer versions for the past several versions. Still try the upgrade first and if you feel it is sluggish, you can go for a fresh install.

Remember that you'll lose your data on the disk if you go for a fresh install. So, please make a backup of your important data on an external disk.

If I upgrade to Ubuntu 26.04 can I downgrade to 25.10 or 24.04?

No, you cannot. While upgrading to the newer version is easy, there is no option to downgrade. If you want to go back to Ubuntu 24.04 or 25.10, you’ll have to do a fresh install of the desired version.

Should I be concerned about Wayland only Ubuntu 26.04?

That is really up to you. If you are using a software that is important to your workflow and that software does not support Wayland, then you will have issues.

While it is still possible to install the legacy Xorg display server on KDE, GNOME 50 has completely removed Xorg support. As far as I know, you cannot use Xorg on GNOME 50 or higher anymore.

So, please check which applications are essential for your workflow and then check from their website or forum to verify if they support Wayland or not. Make a decision accordingly if you have to keep on using 24.04 or switch to 26.04.

How do I know if Ubuntu 26.04 supports all my wifi and printer drivers?

While a newer version brings newer kernel that supports more hardware, it is not unheard to encounter wifi connectivity issues.

More questions?

I have tried to answer the common doubts an Ubuntu beginner usually have about a new release. This is coming from seventeen years of using Ubuntu and fourteen years of running this website. But then I am not a beginner anymore and I may not be able to think of all the questions a new Ubuntu user might have. So, if you still have doubts, please ask them in the comments and I'll try to help you out.

It has also found its way into places that have nothing to do with traditional computing. Smart TVs run some variant of it. Cars run it. If something has a processor and a purpose, there is a good chance Linux is involved somewhere.

Over the years, we have also seen some interesting experiments involving Linux and Windows together. loss32 runs an entire desktop as Win32 software under Wine, and Microsoft's WSL has made Linux a part of Windows 10 and beyond.

Now, Hailey, an open source developer, has taken that idea and turned it around. Instead of Linux hosting Windows apps, she has made Windows 9x host Linux.

WSL9x: Overview ⭐

The project brings a Linux subsystem to Windows 9x, covering 95, 98, and ME, with Linux kernel 6.19 running alongside the Windows 9x kernel, letting both operate on the same machine at the same time.

As for how it works, a patched kernel from Hailey's win9x-um-6.19 branch sits at the core, which is compiled using the User Mode Linux architecture and loaded at a fixed base address of 0xd0000000.

A VxD (virtual device driver) handles initialization, loads the kernel off disk and manages the event loop for page faults and syscalls. Since Win9x lacks the right interrupt table support for the standard Linux syscall interrupt, WSL9x reroutes those calls through the fault handler instead.

Rounding it all out is wsl.com, a small 16-bit DOS program that pipes the terminal output from Linux back to whatever MS-DOS prompt window you ran it from (as shown in the screenshot above).

In her Mastodon post (linked above), Hailey pointed out that WSL9x requires no hardware virtualization, and that it can run on hardware as old as the i486. The same architecture that you might remember is being dropped from the Linux kernel.

Get WSL9x 📥

WSL9x doesn't ship a pre-built binary, so you'll need to build it from source and deploy it on a Windows 9x system (95, 98, or ME). The source code and build instructions are on Codeberg.

💬 Do you think that this is something that you would play around with? Or is just a gimmick?

The proposed amendment would exclude open source operating systems and apps, code repositories like GitHub and GitLab, and containers like Docker and Podman.

We covered this bill back in February, when it made no such distinction. Carl has been working directly with Colorado Senator Matt Ball, the bill's co-author, to push for these exclusions since then, and it looks like his efforts are paying off.

When Neal Gompa (of Fedora fame) followed up, asking whether there was any outreach to California and New York over their age verification bills, Carl replied by saying that the community now has a template to take the fight elsewhere.

And that the next step is a letter to Colorado representatives to pass the bill with the amendments in place, and then adapting that letter for other states while working with the open source community to raise awareness.

Before any of that, though, Carl has to testify. 🏛️

He's scheduled to appear before lawmakers today, on April 23, and is asking the community for backup. He's specifically looking for stories where kids have built or made things thanks to having unhindered access to open source software.

You can share them on the Fosstodon post linked above or DM him directly.

As for the bill itself, it passed the Colorado Senate 28-7 back in March and is currently waiting on a House vote.

Speaking up helps!

All this is proof that speaking up against something detrimental and fighting for your rights does work if there's enough noise and disruption surrounding it.

And while users of Linux distros and other open source platforms in Colorado will hopefully breathe a sigh of relief, those in the other states are still at risk of being affected by age verification laws.

Maybe Carl's template is something you could apply in your state? 😉

And then there's also the proposed federal bill pushing for OS-level age verification across the US, with no exemptions for open source, potentially overriding any state-level exclusions.

EmuDeck is an installation script that simplifies setting up emulators on the Steam Deck and other SteamOS devices. It handles emulator configuration, hotkeys, and most of the tedious setup work that retro gaming on Linux would otherwise involve.

Back in 2024, the project lead, Dragoon Dorise, launched an IndieGoGo campaign for EmuDeck Machines, a pair of Linux mini PCs built for couch gaming in a Dreamcast-inspired 3D-printed case. The idea was to make hardware as approachable as EmuDeck had made software.

But it never shipped. Funding fell short of what manufacturing required, and the project quietly died. Now, EmuDeck is rejoining the gaming hardware space with a Linux-powered gaming console that looks a lot like an Xbox Series S.

Playnix Console: For Linux Gamers

The Playnix Console is powered by a six-core AMD Ryzen 5 5500, which is running at 3.6 GHz and has a 65W TDP. Graphics duties are handled by an AMD Radeon RX 9060 XT. It is an RDNA4 card with 32 compute units, 16GB of GDDR6 VRAM, and a 150W TDP.

For the memory, 16GB of DDR4-3200 in dual-channel configuration is on offer, and given how absurd RAM prices have been lately, this seems like a sensible call over packing in more at added cost.

Cooling is handled by Noctua and Thermalright fans, with claims that the console stays around 65 °C during 4K gaming while maintaining quiet operation.

What makes it a Linux gaming console is that it ships with PlaynixOS, a custom Arch Linux-based distro developed by Playnix that boots straight into Steam's gaming mode, with updates being handled in the background.

Of course, if that doesn't suit your gaming needs, you can swap it out for other Linux-powered or proprietary OSes like Bazzite, Nobara Linux, SteamOS, and Windows.

As for what kind of games you can play on it, the official text points out that 4K 60 FPS at High settings using FSR or XeSS presets is possible in a resource-heavy title like CyberPunk 2077.

The Playnix team has also created Playnix KB, a portal that lets the community share game settings and tweaks for maximizing performance across different titles. It's already populated with many popular games, and updated information should come in as more people get their hands on the console.

The rest of the specifications include:

• Storage: 1x 512 GB NVMe and 1x empty NVMe slot.
• Ports: 2x USB 3.0 + 4x USB 2.0 + 1x USB C 3.1 + 1x Gigabit Ethernet + 1x HDMI 2.1 (HDR 4K 120hz and 8K 60hz support), 1x DisplayPort 2.1 (with HDR 4K 120hz and 8K 60hz support).
• Connectivity: WiFi 6E and Bluetooth 5.
• Power: Unnamed Flex ATX 600W PSU.

All of the above is enclosed in a 3D-printed case that encourages user repairability, as much of the internal components like the CPU, GPU, RAM, etc. can be repaired or upgraded, provided they fit inside the case.

Its measurements are 320 x 247 x 64 mm / 12.6 x 9.7 x 2.5 inches.

Want Yours?

Batch #1 and #2 are already sold out, and at the time of writing, #3 was up for order with a $1,179 price tag, which doesn't include shipping. These devices come with a 2-year warranty that covers repairs and replacement.

You can get yours by visiting the official store.

That's made them a staple for everything from running a home media server to deploying production applications. Spin one up, use it, and tear it down. The host machine stays clean all the way through.

Docker is where most people start, and for good reason. It has the ecosystem, the documentation, and years of community knowledge behind it. Podman is Red Hat's alternative, largely compatible with Docker on the command line but without a daemon running in the background, and it runs containers as a regular user rather than root.

Now managing containers can be a handful if you have got a bunch of them running, and this is where Pods comes in. It is built in Rust and uses libadwaita for its interface, following GNOME's design principles closely.

From a single window, you can pull and build images, create containers and pods, start and stop them in bulk, view logs, monitor processes, inspect details, and clean things up when you're done.

With Pods 3.0, the entire backend was rebuilt to support multiple container engines, with experimental Docker support being the first addition to come out of that change.

I took this release for a test run to see how it performed.

Pods: Easy Container Management

I ran Pods on a Fedora Workstation 43 system, which already had Podman pre-installed. Do keep in mind that I had no prior experience with containers going into this, so I stuck to simple images like PodmanHello, nginx, and BusyBox to get a feel for how the app handled the basics.

After enabling the Podman socket, I launched Pods and set up a new connection. Two URLs were already pre-selected, the Podman Unix Socket and the Docker Unix Socket, with the option to point to a custom URL if needed.

I gave the connection a name and a color, and Pods quickly populated with the available containers.

From there, I could see the telemetry of any running containers, along with options to kill, restart, start/stop, pause, and delete them. I tested the start/stop toggle with nginx, and it worked without a hitch.

I even double-checked that by running the podman ps command before and after I had used the start/stop toggle, and the results were positive. Pods was able to start and stop a container without much fuss.

I did notice that freshly pulled containers came with long, jargony names by default. That was easy enough to sort out though, as Pods lets you rename them directly from the interface.

You can click on the pen icon near a container's name to do so!

And in cases where I had pulled something by mistake or just didn't need a container around anymore, I could delete it just as quickly using the delete button.

Pods also let me batch manage containers through a "Multi-Selection" mode, which surfaces the same kill, restart, start/stop, pause, and delete options but across multiple containers at once.

This can come in handy when you have several containers you want to act on without going through each one individually.

You will find this mode in the top bar menu; just click on the checkmark button.

I could even create pods, which are groups of containers that share the same network and resources, but I stuck to focusing on containers for this one. I went into the Images page to see what options were on offer. Here, I could see each image's properties, like its ID, when it was created, how much storage it was using, and what command it had.

I could also inspect the image properties in structured text for a more detailed look under the hood, browse through the history of the image, and check the repository tags it was associated with.

Finally, I checked out the Prune Stopped Containers option, which lets you bulk remove containers that are no longer running. It even shows a calendar view to set a cutoff time, so you can prune only containers that stopped before a specific date rather than wiping everything at once.

You can find it via a dedicated button in the top bar that looks like an eraser.

Get Started

If you think Pods would be a good fit for your workflow, then you can install it from Flathub, or, alternatively, by running the following command:

flatpak install flathub com.github.marhkb.Pods

If you prefer building from source, then you can visit the project's GitHub repository.

The project is funded through investment from Mozilla and is a standalone product, separate from Thunderbird, built by a different team within MZLA that's focused on enterprise AI products.

Offered under Mozilla Public License 2.0, Thunderbolt offers an AI workspace where users can interact with AI through chat, search, and research, connect to enterprise data, and choose the models and tools that fit their needs.

It runs natively on Linux, Windows, macOS, iOS, and Android, with a web client also being made available.

A thing to note…

You should know that Thunderbolt ships with telemetry on by default.

According to the project's telemetry documentation on GitHub, it uses PostHog to collect usage data covering chat activity, model selections, settings changes, and location information.

This can be switched off in settings, and the project states no personally identifiable information (PII) is collected without explicit consent.

Who is it for?

The intended audience for this could be organizations with strict data residency or compliance requirements. So think healthcare providers, legal firms, and financial institutions that cannot afford sensitive internal data flowing through third-party AI services.

As for its competition, Thunderbolt is a direct challenge to Microsoft Copilot, ChatGPT Enterprise, and Claude Enterprise. In the open source space, it sits alongside tools like Open WebUI and LibreChat, both of which offer self-hosted AI frontends.

Announcing Thunderbolt, the CEO of MZLA Technologies Corporation, Ryan Sipes, added that:

AI is too important to outsource. With Thunderbolt, we’re giving organizations a sovereign AI client that allows them to decide how AI fits into their workflows – on their infrastructure, with their data, and on their terms.

What can you expect?

Thunderbolt connects to frontier models from Anthropic, OpenAI, and Mistral, handles local inference through Ollama, and accepts custom providers, with the workspace offering Chat and Search modes.

It can also handle scheduled work, pulling together briefings, tracking topics over time, or kicking off actions when set conditions are met.

deepset's Haystack integration ties the client into enterprise agent and RAG pipelines within the same architecture, whereas MCP (Model Context Protocol) support is in preview, and ACP (Agent Client Protocol) is in active development with an April 2026 target.

How to get it?

You can get started with Thunderbolt by visiting thunderbolt.io. Organizations interested in enterprise deployment, professional support, or custom development can get in touch with the team.

As for the source code, it lives on GitHub.

Other than that, the FAQ does mention that a Thunderbolt version for regular users is on the cards, but there's no release date for it yet.

I could not help taking a walk in Linkin Park ;)

Okay. Back to serious stuff. Weird but serious stuff.

So, last month, Mozilla unveiled the new Firefox mascot, named Kit. That's a cute-looking macot, by the way.

Mozilla shared a post in their official subreddit. A couple of weeks later, someone noticed the use of'pronouns in that post and all hell broke loose. What was supposed to bring "warmth and familiarity", brought heated arguments and boycott threats.

As you can see above, instead of "it", they/them was used in that post, potentially indicating the assignment of non-binary gender identity to them. More on this in the later section of this article.

Hi everyone, if you’ve been poking around our recent updates, you might have noticed a new mascot showing up a little more intentionally. We figured it’s time to introduce them properly. Meet Kit. And before you ask, Kit is neither fox nor red panda, they’re a firefox of course.

The discussion gained traction around April 11, when Brian Lunduke highlighted the pronoun usage and thus bringing the topic into wider debate.

How the Internet Reacted (Predictably)

As you can imagine, the internet reacted really well, being "very accepting and non-controversial". If you don't believe me, you're right. I've missed April's fool by a huge margin to even consider making that joke.

The “Woke” Debate and Boycott Calls

The outrage was very evident on X (Twitter) and Reddit. Some people immediately jumped ship, posting screenshots of them uninstalling Firefox.

Some posted about how it is all a part of the "rainbow" agenda, and how they're trying to infuse politics into something that has no need for it.

Some people started posting about using the "male lion" browser, Brave.

The word "woke" was used in almost every other tweet, claiming that it was being spread like a virus.

There was a smaller faction of the critics that brought up a few points of criticism about Firefox's past. The co-founder Brendan Eich had made a significant contribution to a cause in California that sought to ban same-sex marriages (he then proceeded to resign after the outrage, and founded Brave).

Other than that, their AI integration, and the CEO's statements in favor of censorship in 2020 were also brought up.

Counter-Reactions: “Why Does This Even Matter?”

The other side consists more of indifference than support, the most frequent point being that it doesn't matter what pronouns a cartoon fox mascot uses, that the outrage was misplaced and irrelevant to everyday usage of the browser.

The word "snowflake" was thrown around from both the sides, but more to emphasize how a part of the internet was offended by something very harmless.

While some users spoke of inclusion of a large faction of people, and brownie points for spreading awareness, other users claimed alienation of "half of the population".

On a different note completely, a part of the internet went all in with the jokes, my personal favorite as a physics student being that it is only obvious that Firefox is non-binary considering their codename "Quantum", in which a particle exists in two states at the same time.

It goes without saying that there were plenty of "what does the fox say?" jokes.

The Reality: Is Kit Even Non-Binary?

The important point to remember through all of this, however, is that Mozilla did not really claim that Kit was non-binary, but only referred to Kit with "they" later in the article.

You don't have to rely on a tweet for the reference. If you read the branding guideline from Mozilla, it clearly mentions this about Kit:

Kit (he/she/they/them/it) is the user’s constant companion. Wherever they choose to roam, Kit will accompany and guide them with clever, playful encouragement and support — giving the user the confidence to run free.

Basically, Kit has no gender. Or, should I say it has whatever gender you prefer. Perhaps the person who posted from Mozilla's official account prefered the 'they/them' pronoun? Personally, I would prefer calling it "it" because it rhymes with "kit".

Final Thoughts: Much Ado About Nothing?

So what’s the takeaway?

A mascot meant to feel friendly ended up triggering a familiar internet cycle:-interpretation, outrage, and counter-outrage.

Whether you see it as inclusion, overreach, or simply irrelevant, one thing is clear; even a cartoon fox isn’t safe from becoming a debate.

What do you think? Overreaction or valid concern?

Jurors found Meta and Google negligent for the way Instagram and YouTube are designed; not for any particular piece of content (the 20‑year‑old plaintiff, identified as Kaley/KGM), happened to see on them. They awarded her $6 million in compensatory and punitive damages and explicitly described these platforms as deliberately addictive “machines” that harmed her mental health.

This is more than a sympathetic jury and a moving story. It is the first time a US jury has effectively treated major social platforms as defective consumer products whose design – infinite scroll, notifications, algorithmic recommendations – can be a “substantial factor” in harming young users. In doing so, the case skirted the traditional shield of Section 230 by focusing not on user‑generated content, but on product design and failure to warn.

For critics of big tech, and I am one of them, that sounds like justice delayed finally arriving. I was happy.

Briefly.

But if we are not careful, the legal and policy response to this big tobacco moment will harden the already rapidly enshitified internet we already have: centralized, identity‑hungry, and surveillance driven. These are precisely the conditions that made these products so powerful in the first place.

From Bad Content to Bad Machines

For nearly three decades, legal debates about platforms have orbited around content: who is responsible for extremist propaganda, self‑harm photos, misinformation. Section 230 in the US enshrined the idea that platforms are not publishers of third‑party speech. Even when courts and regulators pushed, they pushed on content moderation, not on the underlying machine.

The Kaley verdict is a reorientation of this conversation. Jurors heard company documents and expert testimony describing Instagram and YouTube as addiction machines” designed to maximize engagement, time‑on‑site and data extraction from children who were never supposed to be there in the first place.

They found negligence not only in failing to keep under‑13s off the platforms, but in failing to warn about the risks of the core design itself.

This shift from “we hosted bad content” to “we built a dangerous machine” matters. It opens the door to product‑liability style reasoning that could travel, in principle, to other design patterns: streaks, loot-boxes, recommendation systems, dark patterns in on-boarding. It also resonates with developments outside the US, where the EU’s Digital Services Act is already scrutinizing addictive design at the level of interface and recommender algorithms. Earlier this year, the European Commission issued preliminary findings that TikTok’s reliance on infinite scroll and weak “screen time breaks” breaches its duty to mitigate addictive design risks under the DSA, and told the company to change “the basic design of its service”.

But if the machine is on trial, the question becomes: what kind of machine do we build next?

“Addiction” as Legal Story and Medical Dispute

In both law and media, the Kaley verdict has been framed as proof that social media is simply addictive and toxic to teens. The courtroom narrative is clean: a straight line can be drawn: a vulnerable child to the manipulative machine.

The scientific picture is messier.

On one side, the 2026 World Happiness Report carries a chapter by Jonathan Haidt and Zachary Rausch arguing that there is now “overwhelming evidence” that social media is harming adolescents at a scale large enough to shift population‑level mental health, drawing on seven lines of evidence ranging from cross‑sectional studies to natural experiments. The authors argue that ordinary use – often five or more hours a day – functions as a product safety failure, especially for girls.

We further argue that when these lines of evidence are considered alongside the timing, scope, and cross-national trends in adolescent well-being and mental health, they can help answer a second question: was the rapid adoption of always-available social media by adolescents in the early 2010s a substantial contributor to the population-level increases in mental illness that emerged by the mid 2010s in many Western nations? We call this the “historical trends question”. We draw on our findings about the vast scale of harm uncovered while answering the product safety question to argue that the answer to the historical trends question is “yes”.

On the other, another chapter in the same report, by Helliwell and colleagues, emphasizes that the relationship between youth well-being and internet use is more nuanced: some types of online activity (communication, learning, content creation) correlate with higher life satisfaction, while heavy social media and gaming correlate with lower well-being, particularly at extreme usage levels and in English‑speaking countries. They caution that youth well-being trends cannot be reduced to a single cause.

In other words: there is strong evidence of risk and harm, but causality, dose, and mechanism are still contested.

Safety as a Pretext for More Surveillance

Politicians around the world have not waited for the science to settle. They have moved quickly to do something about youth and social media – and the measures they are choosing tell us a lot about the political economy of the internet they are entrenching.

In Australia, world‑first social media age restrictions now require major platforms – Facebook, Instagram, TikTok, X, YouTube, Snapchat, Threads, Reddit, Kick, Twitch – to take “reasonable steps” to prevent under‑16s from having accounts, backed by fines of up to A$49.5 million for non‑compliance.

In practice, they are expected to deploy multiple age assurance technologies: ID checks, facial or voice analysis, behavioral age inference.

Children and parents themselves are not fined; the pressure is entirely on platforms to ramp up identity and behavioral surveillance in order to demonstrate diligence.

In the US, California’s Digital Age Assurance Act pushes the same logic down into the operating system itself. From January 2027, OS vendors are required to collect an age or age bracket at account setup and expose it via an API so that app stores and online services can query a system‑level age signal.

The law is written broadly enough that free and open‑source operating systems – Debian, Fedora, BSDs, Pop!_OS – are, on paper, on the hook alongside Apple and Microsoft.

System76’s CEO, writing about this wave of laws in Colorado and California, warns that the effect is to turn OS vendors into identity brokers and gatekeepers, and to “encourage children to lie” about their age for fear of being confined to a “nerfed internet”

Layer these developments on top of each other and a pattern emerges: won't somebody please think of the children?

We've heard this moral argument before: with video games, heavy metal, rap. What happens next is history rhyming:

• pushing age‑verification and age‑bracketing ever deeper into the stack – from app sign-up forms, to OS APIs, to network‑level checks;
• incentivising large platforms and OS vendors to collect, infer, and share more information about who we are and how old we are;
• creating compliance burdens that small, de-centralized, or non‑profit projects can barely navigate, effectively nudging regulators and industry towards a small club of compliant, centralized providers.

Safety becomes the moral language through which a more identity‑locked, surveilled, and centralized internet is made to feel inevitable.

Regulators Discover “Addictive Design” – But For Whom?

The EU’s preliminary findings on TikTok’s addictive design under the DSA are a good example of this ambivalence. On one level, it is encouraging to see regulators finally target infinite scroll, frictionless autoplay, and weak screen time nudges as systemic risks requiring product changes, not simply more content moderation. The Commission is, at least in principle, saying: design patterns that exploit compulsive behavior and harm children can be unlawful. This is a good start. Unfortunately that's where the good news ends.

Notice who is legible to this kind of regulation. The DSA presumes large, centralized platforms with access to vast behavioral data, capable of implementing complex risk‑assessment and age‑assurance regimes. The Australian and Californian laws do the same.

A federated social network run by a school, a youth center, or a community collective cannot cheaply plug into this machinery. A small FOSS OS project has neither the lawyers nor the telemetry to play at this table.

The risk is that addiction design becomes another compliance rubric that only the biggest players can afford to satisfy, while everyone else is either chilled out of existence or forced to rely on the same proprietary identity infrastructure.

The Missing Imagination: Community‑Run, Free and Open Alternatives

The saddest thing about this moment is how narrow the mainstream imagination of alternatives remains. The policy menu is filled with bans, curfews, and ID checks for the same extractive platforms. There is little serious talk of changing the infrastructure.

Yet we know from both history and present practice that other models are possible. Schools and libraries have run moderated online communities for decades. Federated platforms like Mastodon and Matrix, for all their flaws, show that it is possible to have social networks that are not controlled by a single profit‑maximizing entity. Community‑run game servers, forums, and fan communities have long been youth‑driven spaces with their own norms of care and accountability. My first years on the internet, circa 2001-2003, was spent in such forums. Social media trampled such online communities during their first decade.

A genuinely emancipatory response to the Kaley verdict would start from a different question: given that these products have now been recognized, in court, as dangerous by design, how do we:

• treat them like other dangerous consumer products – with warnings, design constraints, and liability – without making bio-metric and behavioral surveillance the price of entry to the digital world;
• redirect public money, regulation, and cultural attention towards building non‑exploitative, commons‑based digital spaces for young people;
• lower the barriers for schools, municipalities, youth groups, and co‑ops to run their own FOSS‑based platforms, with public funding and legal safe harbors, rather than locking them into corporate clouds that must, by their nature, maximize engagement.

This is where free and open source software is not just a licensing detail but a political stance. An internet where young people’s social lives unfold on community‑run, auditable, forkable software – hosted by institutions that have a duty of care, not a duty to shareholders – is not a Utopian fantasy. It is not merely a design choice.

It is a political choice.

Builders, Regulators, and the Rest of Us

For those who build technology, the Kaley verdict is a warning shot: engagement is no longer a neutral metric. If a design pattern is optimized to keep a 10‑year‑old scrolling past bedtime, courts may increasingly treat that as a defect, not an achievement. Engineers, designers, and product managers now have to think like people who might one day be cross‑examined about why they shipped this infinite scroll, this notification scheme, this recommender.

For regulators, the temptation will be to double down on what already feels familiar: more age gates, more identity checks, more compliance dashboards for big platforms and OS vendors. It is politically safer to demand better seat-belts from the existing car companies than to fund buses, bike lanes, or public trains. But if all we do is wrap the same addictive machines in ever tighter rings of surveillance and control, we will have saved some children from some harms at the price of deepening structural dependence on the very firms whose incentives created the crisis.

The LA jury has told us, in the blunt language of damages and negligence, that the machine is the problem. The real task now is to ensure that the fix is not simply a more paternalistic, more identity‑hungry version of the same machine, but an opening for something else: community‑run, free and open infrastructures where young people can be online without being harvested.

That is a harder story to tell in a courtroom. But it is the story the rest of us – parents, educators, coders, writers, legislators – will have to write.

Kamila, now a 21-year-old graduate student at Saarland University in Germany, daily drives a window manager that predates most of her classmates. That alone is a fun fact.

But what makes it remarkable is that she didn't just use it, she dug into its decades-old codebase, found a bug that had been hiding there since 2006, and fixed it.

What is Enlightenment E16, again?

For the uninitiated, Enlightenment is a window manager for Linux, the software responsible for drawing and managing the windows on your screen. It first appeared in 1997, making it older than a significant portion of today's Linux user base. E16, the version Kamila uses, arrived in 1999 and quickly gained a reputation for being highly customizable and visually impressive, at a time when most Linux desktops were far more utilitarian.

Enlightenment is not as well known as KDE or GNOME, and even LXDE has broader name recognition today. But it has a small, dedicated following and can be found in niche distributions like Pentoo or Bodhi Linux. Bodhi actually uses Moksha, a fork of Enlightenment, as its default desktop.

Over time, the Enlightenment team began a complete rewrite of the project using a new modular framework called EFL (Enlightenment Foundation Libraries). That rewrite took over a decade and eventually became E17, released in December 2012. E17 evolved from a simple window manager into a full desktop shell with modern compositing and improved hardware support.

But not everyone followed. A portion of the community stuck with E16, continuing to maintain and develop it independently. It reached the 1.0 milestone and, as of 2024, the latest release is version 1.0.30. It is very much alive, just quietly so.

Kamila is part of that quiet community.

The accidental bug discovery

She wasn't hunting for bugs. She was doing something mundane; preparing lecture slides for a course she teaches as a graduate student. She had a couple of PDFs typeset in LaTeX, opened one of them in Atril, a document viewer, and her entire desktop froze.

It wasn't a one-off glitch. The freeze was reproducible, which is both frustrating and, for a developer, oddly exciting. A reproducible bug is a bug you can actually chase down. So she did.

After digging through the codebase, Kamila traced the freeze back to the way E16 handled overly long file names.

When a window title was too long and needed to be truncated, the algorithm responsible for doing so had no iteration limit. So it would spin indefinitely, locking up the desktop entirely. The bug had been sitting there, dormant, since 2006, waiting probably for exactly the right set of circumstances to surface.

She patched it and the fix is available on her blog. I hope she made a pull request to the original codebase as well.

Why this story matters

On the surface, this is a niche story about an obscure window manager that most Linux users have never touched. But look a little closer and it is something more than that.

Kamila was born in 2004. The bug she fixed was already in existence when she turned two. She grew up, went to university, became a graduate student and a teacher and the bug just sat there, in a codebase maintained by a handful of enthusiasts, waiting. It took someone who actually uses E16 as a daily driver to finally stumble onto it and care enough to fix it.

That is the true open source spirit. Not a big company, not a bounty program, not a CVE filing. Just a person, their computer, a frozen desktop, and the curiosity to figure out why.

There are people who have been maintaining this codebase for decades. There are people who still use it. And every now and then, one of those users catches something no one else did and quietly makes the software a little better before moving on with their day.

That's not a small thing. That's the whole point.

Source: The Register

Cal.com, a popular open source scheduling platform and one of the more well-known self-hostable alternatives to Calendly, has found itself in the second camp. After five years as an open source project, the company has announced that it is switching to a closed-source model, citing the growing threat of AI-powered vulnerability scanning.

What happened?

The co-founder of Cal.com, Bailey Pumfleet, has addressed why they went down this path, saying that AI has changed what it takes to exploit an application. Earlier, finding vulnerabilities meant real expertise and some serious time investment.

But today, an AI model can be directed towards a public repo and do the same job systematically without needing much manual labor.

He also cited a specific case to back this up, where AI tooling reportedly found a 27-year-old vulnerability in the BSD kernel and had working exploits ready within hours.

But, yeah, closed source it is. 😅

Another thing worth knowing is that the production codebase had already been drifting away from what was publicly available. Core systems like authentication and data handling had both gone through significant rewrites, making the public repo and what actually runs in production two fairly different things by the time this announcement came.

Does it make sense?

Cal.com isn't wrong that AI can be used to hunt for vulnerabilities in open source code. That's documented and real. But the provided argument treats AI purely as an attacker's tool, which is a selective reading of the situation.

Take the Linux kernel, for example. We recently covered how Greg Kroah-Hartman, the Linux stable kernel maintainer, has been running what looks like AI-assisted fuzzing on the kernel through a branch he calls "clanker," using it to identify bugs and patch them proactively.

There's even an official policy in place that governs the use of such AI tools for contributions.

Then there's the older argument that closing your source doesn't actually make you more secure. It just means fewer eyes on the code. Open source projects benefit from anyone, anywhere, being able to spot and report problems.

Heartbleed and Log4Shell were both found by external researchers precisely because the code was auditable. This just shows us that a private codebase doesn't prevent vulnerabilities; it just reduces the chances of catching them before someone with bad intentions does.

What's next?

For self-hosters and developers, Cal.diy is what's on offer. It's available now under the MIT license, with the documentation covering installation via Docker, Vercel, Railway, Render, and a handful of other platforms.

The project is described as "strictly recommended for personal, non-production use," with a "use at your own risk" disclaimer throughout. It is community-maintained, with no official backing from Cal.com.

Feature-wise, Cal.diy covers the personal scheduling essentials like event types, calendar integrations, video conferencing, webhooks, and API access.

But a fair bit is missing. Teams, Organizations, SAML SSO, SCIM directory sync, Workflows, Routing Forms, and the Insights Dashboard are all absent from the community edition.

If you're running Cal.com for anything commercial, the Cal.diy documentation steers you back to the paid product pretty explicitly, saying that "for any commercial and enterprise-ready scheduling infrastructure, use Cal.com."

All of that made me wonder, whether AI was the catalyst or the perfect scapegoat for a closed-source transition. Anyway, I like yapping like this every so often; don't mind me.

The first removal came with the ATA pull for Linux 7.1-rc1, merged by Linus Torvalds on April 15. It dropped the Baikal bt1-ahci DT binding and stripped Baikal-specific code from the ahci_dwc driver, with the ATA maintainer, Niklas Cassel, noting that upstreaming for the SoC "is not going to be finalized."

Furthermore, the code had been sitting unmaintained for some time now. Serge Semin, who contributed the bulk of Baikal's kernel support over the years, was among roughly a dozen Russian developers removed from the kernel MAINTAINERS file in 2024.

With no one left to maintain it and the hardware itself rare even within Russia, there appears to be no rationale for keeping the code around.

Some background info

The Baikal line of CPUs is the work of Baikal Electronics, which was founded in January 2012 as a spinoff of T-Platforms, a Russian supercomputer company.

It started with a MIPS-based chip for embedded applications, then pivoted to ARM for its later processors, all manufactured at TSMC. The plan was to supply Russian state-owned enterprises with domestically produced CPUs as an alternative to Intel and AMD.

But Russia's 2022 invasion of Ukraine ended that. Sanctions cut off TSMC access, 150,000 Baikal-M units already manufactured were seized in Taiwan, and ARM production licenses were lost. The company filed for bankruptcy in August 2023.

It did not stay down. By the end of 2024, Baikal had shipped a total of 85,000 processors since its founding and began serial production of the Baikal-U1000, a RISC-V microcontroller, in September 2025 (in Russian).

The current lineup consists of the Baikal-T (MIPS), Baikal-M and Baikal-S (ARM), and the Baikal-U (RISC-V).

Those already running Linux on Baikal hardware will need to stay on Linux 6.18 LTS or earlier, as newer kernel versions are dropping the support.

Suggested Read 📖: The Linux Kernel is Finally Letting Go of i486 CPU Support

That's pushed people toward privacy-first alternatives, and quite a few companies have stepped up to meet that demand. Tuta is one of the more recognizable names in that space, offering encrypted mail and calendar services to over 10 million users worldwide.

Now, the company is looking to round out its ecosystem with the one piece that's been missing, an encrypted cloud storage solution.

A haven for your files?

Tuta first laid the groundwork for this back in July 2023, when it announced the PQDrive project with backing from the German government. The initiative had received €1.5 million in funding through the KMU-innovativ program, a grant scheme that supports small and medium enterprises in research and development.

The goal was clear from the very beginning. It was to build a cloud storage service secured with post-quantum encryption, not just conventional algorithms.

To get there, Tuta partnered with the University of Wuppertal, which handled key research tasks including testing cryptographic algorithms and figuring out how to deduplicate encrypted data without punching holes in the security model.

All that effort has now produced a product ready for real-world testing. Starting today, Tuta Drive enters closed beta, with select users receiving early access to put it through its paces ahead of a public release.

It is an end-to-end encrypted cloud storage service that fits directly into Tuta's existing ecosystem alongside mail and calendar. Everything you store gets encrypted without any action needed on your end, and the zero-knowledge architecture means Tuta has no technical ability to read your files or share them with anyone else.

The encryption underpinning Drive is the same TutaCrypt protocol Tuta already uses for its mail service. It combines classical and quantum-resistant algorithms in a hybrid approach, so even if a quantum computer cracks one layer down the line, it still has to contend with the other.

And, the service is hosted in Germany, which brings strict GDPR protections into play on top of the technical safeguards.

Arne Möhle, CEO of Tuta, announced this by commenting that:

With Tuta Drive, we are taking the next step towards offering a full private digital workspace.

Today, more than ten million citizens and businesses, including journalists, whistleblowers and activists use Tuta Mail as an alternative to insecure email offered by mainstream providers.

Adding an encrypted cloud storage to Tuta will enable them to also store their files securely.

Test run

We were given early access to the closed beta ahead of its rollout today, and here's a look at what Tuta Drive is like right now.

The interface is minimal, which is fine. You get a familiar sidebar and a top bar that shows you the server connection status and houses quick-switch buttons for Mail, Contacts, Calendar, and Drive.

First, I uploaded two videos to see how Tuta Drive would handle them. Here, the upload speeds were noticeably slow when connected over a VPN, though that's more or less expected. Without an active VPN connection, file uploads were fast.

Moving those files to a new folder afterward was straightforward using the "Move" option from the right-click context menu. Drag and drop works too, and I could manually select specific files without any issues. Cut and paste for moving files around also worked well.

When uploading multiple files at once, a progress list appears, which is handy. The one catch is that you can't scroll through it to check which file is currently being processed, which was a bummer.

Files are shown with appropriate icons depending on type, so images, videos, and audio all get their own visual treatment. Folders display a cat emoji where the folder size info should probably appear, which looks like a work-in-progress placeholder more than anything else.

If you upload something by mistake or decide a file isn't worth keeping, you can delete it promptly either from the right-click context menu or by hitting Delete on your keyboard. The "Trash" page then gives you the choice to either restore it if it was a wrong call or permanently delete it if you're sure.

That said, folder uploads aren't supported yet, and the keyboard shortcut support is lacking. Ctrl+A to select everything in a folder, for instance, does nothing. No search tool either; those are the kinds of gaps that user feedback tends to sort out quickly.

Seeing that this is a closed beta, I am confident that the Tuta folks will listen to what people say about their newest offering and act accordingly.

💬 Would you give Tuta Drive a shot, or are you too committed to Proton Drive or other cloud solutions to even look its way?

Another major update, and not a pleasant one, is coming from the United States. A federal bill is now being discussed that proposes OS-level age verification. Until now, this was limited to a handful of states, but this could expand it nationwide.

Two very different directions. Both worth paying attention to.

Here are other highlights of this edition of FOSS Weekly:

• A new Linux kernel release.
• France replacing Windows with Linux.
• Microsoft locking out open source developers.
• And other Linux news, tips, and, of course, memes!
• This edition of FOSS Weekly is supported by Aiven.

📰 Linux and Open Source News

VeraCrypt, WireGuard, and Windscribe all had their Windows Hardware Program developer accounts suspended, cutting off their ability to ship signed driver updates for Windows.

Two related kernel AI stories this week. First, Linux has shipped an official AI coding assistants policy where AI help is allowed, but every patch needs a human accountable for it. Second, Greg Kroah-Hartman has been running what looks like an AI-assisted fuzzer on the kernel in a branch he calls "clanker."

A Valve contractor has put together a fix for the VRAM mismanagement problem that's been hitting Linux gamers on AMD GPUs with 8GB or less.

A bug report filed in 2005 asking for per-screen virtual desktops in KDE has finally been addressed. The feature lets each monitor show a different virtual desktop independently rather than all switching together.

Linux 7.0 landed this week with a wide spread of improvements. Intel gets Nova Lake audio and better Arc GPU temperature reporting. AMD gets early Zen 6 performance profiling support and GPU groundwork for future hardware.

🧠 What We’re Thinking About

Session has lost all its paid developers and is running on volunteers. Donations are keeping the infrastructure alive until July 8, but development is effectively frozen unless they reach their $1 million donation goal.

🧮 Linux Tips, Tutorials, and Learnings

Not everyone is a command line fan, but if you do spend some time in the terminal, these tips and shortcuts will save you plenty of time and make you more efficient.

And if you are absolutely new to Linux, it helps to start with the basics first. Not commands, but the kind of foundational things that make your early terminal experience far less confusing.

Moving from basics to everyday usability, we now have a beginner-friendly guide to taking screenshots in Linux Mint. It covers the built-in GUI tool, keyboard shortcuts, and even how to set up custom delayed screenshots.

Once you get comfortable with the essentials, you might start exploring distributions more deeply. But not all rolling release distros are made equal. Arch gives you everything and expects you to handle it. Manjaro smooths the edges. Void is independent and leans stable. Gentoo compiles everything. Which one would you go for?

And somewhere along that journey, you’ll inevitably hit the classic fork in the road: Vim or nano. Nano works exactly like you'd expect a text editor to work, with controls visible on screen. Vim, on the other hand, runs on modes, muscle memory, and a learning curve that takes real commitment.

📚 Linux eBook bundle (ending this week)

No Starch Press needs no introduction. They have published some of the best books on Linux. And they are running an ebook bundle deal on Humble Bundle.

I highly recommend checking it out and getting the bundle.

Plus, part of your purchase supports Electronic Frontier Foundation (EFF).

👷 AI, Homelab and Hardware Corner

At some point every homelab stops being manageable by memory alone. Our roundup of dashboard tools is the answer to that.

✨ Apps and Projects Highlights

Yantr is a self-hosted app store for your homelab that runs as a single Docker container on top of whatever OS you're already using.

📽️ Videos for You

Fedora 44 got delayed, but you can check out what's new!

💡 Quick Handy Tip

Firefox has a native color picker called Eyedropper that helps you know the exact hex color code of a specific color on a webpage. It is available inside Menu -> More Tools -> Eyedropper.

You can also right-click on an empty place in the toolbar and select "Customize Toolbar..."

Here, drag and drop the "Developer" tool to the toolbar. Now, you can access the Eyedropper from this button as well.

🎋 Fun in the FOSSverse

A new fun quiz where you have to guess the fake distros that do not exist.

Oops, let me hide my pile of trash. 🫠

🗓️ Tech Trivia: On April 16, 1959, John McCarthy gave the first public presentation of LISP at MIT. The list-processing language he built from scratch became the foundation of artificial intelligence programming and introduced concepts like garbage collection still used today.

🧑‍🤝‍🧑 From the Community: One of our regular FOSSers has posted about Hardware Freedom Day 2026; are you celebrating?

In fact, not all distros are created at all.

This quiz is simple. You'll be presented with a few Linux distros and their details. The twist is that they might not be a real thing. They could just be a fragment of my imagination.

Of course, this is valid only at the time when I created this quiz. The way we move in Linux world, there could be some new distros coming up right after I publish this quiz 😃