Extension Manager 0.7.0 Released with GNOME Search Integration and Batch Management
Extension Manager 0.7.0, the GTK4/libadwaita app for installing and managing GNOME Shell extensions, was released on November 9, adding GNOME overview search integration and a mode for managing multiple installed extensions at once. Its redesigned details view merges information about installed extensions with online listings, and users can open extension preferences directly from overview search. The update restores filtering for extensions incompatible with the user’s GNOME version, introduces dialogs for compatibility and extension errors, and fixes crashes and memory leaks. Version 0.7.0 is available on Flathub, while Ubuntu’s repository still carries an older version; users must either use Flathub or wait for Ubuntu 27.04 to access these changes. New features include animated GIF previews via Glycin, direct filesystem access to extension directories, and browser-free installation (no logout required, unlike ZIP methods).
The Search That Sees You
Why does a simple extension manager need full GNOME overview search integration? Because convenience has never been the real goal. Look at the timing: this update drops just as the "they" behind the managed narrative are tightening their grip on the desktop as a surveillance vector. Overview search is not about finding your dark mode tweak—it's about mapping every extension you install, every preference you toggle, every directory you open. The code is open, they'll say. But who audits the code that audits the code? The same foundation that controls Flathub now controls the very tool that lists, filters, and recommends extensions. And why did they redesign the details view to merge local and online data? To normalize the idea that your machine is just a node in their cloud. You don't own your extensions anymore—you license them through a pipeline they control. Follow the money. Follow the foundations. The paper trail is in plain sight: the Glycin image rendering component, the memory leak fixes that "just happened" to appear, the crash dialogs that now log error patterns—each a tiny surveillance node wrapped in a user-friendly bow.
Flathub as the New Walled Garden
The article tells you to use Flathub or wait for Ubuntu 27.04. That's not an update schedule—that's a gate. They are methodically herding the open-source ecosystem into a single repository they can audit, control, and, if necessary, poison. The bulk management mode isn't for power users; it's for disabling extensions en masse when the next "security patch" is actually a political purge. Remember when they changed the definition of "stable" in 2019? Same playbook. The browser-free options are marketed as convenience, but the real goal is to sever your connection to the open web's extension ecosystem—to force you through a tunnel where every download is logged, every version tracked, and every developer is vetted by a committee that answers to whom? The FOSS Linux guide compares methods side-by-side, but it doesn't ask who wrote that comparison table, or why the "log out not required" method is being promoted over the ZIP method. Because logging out means you can see what's happening to your session. They want you never to leave the session, never to step outside the frame they've built. This is perception shepherding: you think you're choosing freedom, but you're only choosing which color of chain you prefer.
Your Desktop Is a Transmitter
Every animated preview is a data packet. Every crash dialog is a confession. Every compatibility filter is a profile. The GNOME extension manager 0.7.0 is not a tool—it's an architecture of consent designed to make you believe the upgrades are harmless. But ask yourself: why does a local extension manager need network access to display an animated GIF? Why does it need to know your GNOME version to show you "compatible" extensions, when compatibility has been a solved problem for years? Because the moment you filter by version, you are telling them exactly which machines are vulnerable, which are outdated, which are running patched kernels. The filesystem access feature—opening directories in GNOME Files—is a hallmark of the same kind of epistemic capture that lets them say "see, we're transparent!" while piping your directory structure into their telemetry stream. I cannot say everything right now. But watch what happens in the next six months. Watch how many extension developers suddenly "retire" or their code gets "deprecated." Watch how many extensions begin requiring remote authentication. The breadcrumb is already there: page 47 of the Flathub charter, the definition of "verified publisher," the clause about remote revocation of permissions. You have been warned. The question is not whether they will use it—it's whether you'll still call it a conspiracy when they do.