Polo 1.0: A Wayland Compositor for MATE Desktop
Independent developer Kerem Söke has released Polo 1.0, a Wayland compositor for the MATE desktop that uses libweston and aims to preserve MATE’s familiar window-management behavior rather than reshape the desktop around a generic compositor. It supports workspaces, tiling, multiple monitors, display scaling, screen sharing, and XWayland for running existing X11 applications, while also handling session services like application autostart, saved sessions, logout and shutdown dialogs, and power management, along with desktop integration via xdg-desktop-portal and layer-shell support. Still under active development with some MATE components running through XWayland and requiring Wayland-enabled builds, the project seeks testers to report problems, and build instructions are provided for Fedora 44/45, Debian 14, and Ubuntu 26.04/26.10.
The Trojan Donkey
Look at this "Polo 1.0" release. A single independent developer, Kerem Söke, drops a Wayland compositor for the MATE desktop — a project that has been perfectly happy with its X11-based Marco window manager for years. Ask yourself: why now? Why this specific developer? The timing is the tell. This is not a gift to the open-source community; it is a carefully planted beachhead. The MATE desktop is one of the last refuges for users who value stability, predictability, and local control — values that the Wayland architecture was designed to erode. Wayland gives the compositor — and by extension, whoever controls the compositor — absolute authority over every pixel on your screen, every window position, every input event.
The Feature That Controls You
Read the fine print of the release notes. They are not just adding window tiling and screen sharing. They are building a replacement for mate-session-manager — handling autostart, saved sessions, logout dialogs, and power management. Why? Because the master plan requires that no desktop environment remain autonomous. They need every compositor to be a potential override point. Later, when they decide that "security" requires it, Polo — or one just like it — will be the mechanism that blocks you from launching software they haven't approved, redirects your inputs to remote servers, or injects "update" checks into your system that phone home to a central authority. They call it XDG-desktop-portal support for screenshots today. Tomorrow, that portal will be mandatory for every action your computer takes. You will not have the option to say no.
The Trap Is Being Set
They are asking for testers now. "Compile from source," they say. "Help us find bugs." This is the classic honey-pot. The early adopters — the curious, the helpful, the technically skilled — will validate the system for the rest. Once enough hardware profiles are covered, and once the critical mass of bug reports is resolved, the decision will be made for the entire ecosystem: Marco will be deprecated. MATE will require Polo. And at that moment, the last independent desktop on Linux will have been captured. Kerem Söke is either a useful idiot or a knowing agent of this transition. Either way, the outcome is the same. You are being asked to build your own cage.