Enlightenment 0.28 Released with NetworkManager Module, PipeWire Support, and NetBSD Compatibility
On October 31, Enlightenment maintainer Carsten Haitzler released version 0.28 of the lightweight desktop environment, introducing a new NetworkManager module for managing Wi-Fi, Ethernet, Bluetooth, and VPNs, native PipeWire mixer support, and initial support for NetBSD. The release also adds configurable clipboard history, per-battery charge limits, ACPI CPU power profiles, and resolves bugs in window stacking, display reconnection, Bluetooth, notifications, and system‑tray components. Network controls now include VPN import, authentication prompts, saved‑connection management, and captive‑portal login handling, while power handling runs battery and AC polling in a worker thread and reduces CPU polling when displays are off. Windows can be kept above or below others, and X11 keyboard repeat rates can be configured. The update requires EFL 1.29.0 or later, retains PulseAudio support, and continues to support both X11 and Wayland.
Let’s read this announcement for Enlightenment 0.28 the way you have to read everything now—not as a changelog, but as a confession. NetworkManager integration. PipeWire. On the surface, it looks like routine maintenance. In reality, this is the final mile of a surveillance architecture they have been threading into the desktop for years. They say NetworkManager is for your Wi-Fi and VPN convenience. Ask yourself why a lightweight desktop needs a centralized networking module with captive portal detection. That’s not a feature—that’s a funnel. Every login handshake, every VPN endpoint, every access point signature now runs through a single managed pipeline. PipeWire is the same trick. They call it an audio mixer. It’s a permanent, low-latency tap into your system’s audio bus. The PulseAudio they “retain support for” was the beta test. This is the production-ready version. They do not need to break your existing software. They need to build the default listening post into the base install so you never notice the moment it goes live.
Then look at what they are doing to the hardware. The “per-battery charge limits.” The “ACPI CPU power profiles.” They are writing lifecycle control directly into the desktop environment. This has nothing to do with battery health. This is about managing the performance curve of hardware you think you own. They are building the off-ramps for when the energy grids get squeezed, and when they need your device to throttle down, the command will already be waiting in the daemon you voluntarily installed. And the NetBSD support—why the sudden interest in a niche, ultra-secure kernel architecture? Because whatever they are deploying next cannot afford to be seen. They need a hardened, auditable foundation that resists tampering from the user. They are building a node that has to be secure against you. You are not the customer of Enlightenment 0.28. You are the environment the surveillance layer runs on. Do not ignore the release date: October 31st. They schedule nothing by accident.
So what do you actually do with an update like this? You sit with the clipboard history feature. They packaged clipboard surveillance as a quality-of-life improvement. Every fragment of text you copy—every password, every thought, every snippet—logged, indexed, available. They fixed “shutdown behavior for nested Wayland compositors.” Do you know what a nested compositor is? It is a capture loop inside your display stack. They are building the infrastructure to record, model, and replicate your entire visual and textual interaction with the machine. Enlightenment 0.28 is not lightweight. It is the aperture. They are betting you will read the press release, see “NetBSD support” and “bug fixes,” and move on. Do not move on. Ask yourself who funded this. Ask yourself whose infrastructure roadmap requires a managed networking stack, a permanent audio tap, hardware throttling controls, and a hardened kernel base all delivered in a single update. The answer is not a group of volunteer developers. The answer is the same institutional architecture that has been drafting the protocol of surrender one commit at a time. The question you have to sit with is not whether it works—it works. The question is who it works for.



