Re: Cosmic Progress

[colby@colbyt.com]

[-- Attachment #1: Type: text/plain, Size: 1730 bytes --]

Not sure why this email didn't send but trying again from my regular address! -- thanks for all the great updates - so speedy!

On Saturday, July 11th, 2026 at 1:32 AM, CCT <cct@protonmail.com> wrote:

> Thank you for posting this. Since our last conversation, I’ve been further prototyping a COSMIC-based downstream of Spectrum for PolymerOS, so there is useful overlap here.
> PolymerOS currently replaces the standard panel and dock with custom surfaces and carries several small cosmic-comp changes for trust decorations, presence attestation, and compositor readiness. I’ve attached screenshots from two stages of the prototype.
>
> A few notes and questions:
>
> - Immutable configuration: COSMIC’s configuration code attempts to write defaults when loading. Because our /etc/xdg is immutable, we currently seed a writable runtime copy from an administrator-owned immutable baseline. Is there an intended COSMIC location or pattern for this?
>
> - Socket and readiness: Our separately supervised services need a stable Wayland socket path and an explicit signal that the compositor is ready. Is the intended long-term API an absolute socket path supplied to cosmic-comp, potentially followed by service-manager socket activation? Would COSMIC accept a service-manager-neutral readiness signal, such as writing once to an inherited file descriptor, so s6-based systems do not need a downstream patch?
>
> - QEMU and VNC: The desktop is usable with software rendering, without making virgl mandatory. We would prefer both software and accelerated modes to remain supported. We normally use hardware acceleration, while software rendering is valuable for testing compositor security decorations and for headless builders.

[-- Attachment #2: Type: text/html, Size: 4698 bytes --]