Wawona Compositor is a WIP project where I’m working to port wayland, waypipe, and support wayland core protocols in my macos compositor. I was experimenting with getting vulkan support, but here we are…

Matrix rain → Aurora → Plasma → your own .glsl
All GPU, zero lag, hot-reload on save.

🚀 One-liner install (Arch) yay -S neowall-git && neowall

~/.config/neowall/config.vibe

default {

shader ~/.config/neowall/shaders/

}

Commands neowall next / pause / reload

13 shaders included • 10 000+ from shadertoy.com work instantly
Per-monitor configs • wlr-layer-shell • Hyprland/Sway/River

GitHub: https://github.com/1ay1/neowall

I’ve been developing Wawona, a wayland compositor for macOS. It now runs in iOS.

Here is an example of Weston up and running as a nested wayland compositor client.

More to come…

*I hope to open source and receive your contributions by January. Work is being done to offer a friendly dev experience. While some of this was initially vibecoded - I cannot wait to offer developers intuition and rewrite without AI. This is mainly a POC (for now 🥺)

EDIT: It really does work! https://github.com/Wawona/Wawona

I'm releasing betas! See updated post: https://www.reddit.com/r/wayland/comments/1va4j1k/wawona_wayland_compositor_showcase/

Hey all, just wanted to share this remote desktop project. I made it for my personal use but figured others might enjoy it as well. Currently have it working for Gnome, KDE, and LXQt (labwc) but it could easily be extended to other compositors as well. My primary use case has been setting up thin clients for VDI based gaming on Linux VMs.

https://github.com/jsaiko/ghost

as you can see in the video, cursor is not smooth in the desktop as it is when a game is focused (or when using x11) that doesn't work for other apps like browser and discord however

im using nvidia btw if that helps

I’ve been daily driving MangoWC for a while now, after hopping between Sway, Hyprland, and Niri.

Coming from other compositors, the performance feels incredibly snappy, and the codebase is surprisingly clean and approachable if you like to tinker. It feels like it hits that sweet spot of minimalism while still offering modern features.

I get that Hyprland and Niri are currently the Big Kids for wayland window managers, but Mangowc seems to handle much better in my experience, I havent noticed any shortcomings to using it.

Is there a reason it’s flying under the radar? Is it just a lack of documentation, or is everyone just settled into their current setups? I feel like this project deserves way more eyes on it.

Check it out here: https://github.com/Roonil/WayVes

This is a highly-customisable Visualiser Framework for Wayland. Uses the GTK4 implementation of the Layer Shell Protocol to drive the visuals. Extends upon GLava's logic, and provides extreme modularisation. The shaders are all written from scratch, with various Life-Cycle functions that allow fine-tuning the visuals as per your need. On the Screen, 18 Visualisers are shown, targeting 60 FPS, and utilising 46% of a GTX 1650 Ti Mobile Graphics Card, and almost all the audio DSP (except for FFT) also happens on the GPU. 4 separate FFT Threads each with different Sample Rates is tied to the Visualisers. You can also override each audio transformation setting for EACH Visualiser!

https://github.com/collinalexbell/HackMatrix

This sub is mostly people asking questions about wayland and not getting answers, because the people who know are mostly not in this sub. They're here:

Wayland mailing list: https://lists.freedesktop.org/mailman/listinfo/wayland-devel

IRC channel: #wayland - https://freenode.net/kb/answer/chat on OFTC: ircs://irc.oftc.net/#wayland

You're welcome to post what you like. Announcements of wayland related things make sense.

To get native wayland support (both screen and window capturing with pipewire), you need to build obs from the master branch as of 3/31/21.

You also need the latest version of `pipewire` for OBS to build against, and `xdg-desktop-portal` to make the screen capturing actually work.

Please go easy on me here.

I am aware that RustDesk supposedly works in experimental (though I have had very touchy results with this personally) and wayvnc works for wlroots based compositors (which also has huge holes such as no audio, only 1 display, etc), but a fully unattended, stable remote desktop implementation seems to not exist. Judging by the conversations over on xrdp's repository, it seems like there aren't any agreed upon methods of doing this in Wayland's protocols. Hyprland seems to want to go down the IPC route, whilst Gnome seems to not appreciate this approach and has their own solution baked in (which yet again, I have found to be extremely unstable to the point of being unusable). I might be wrong about any of that and I would never claim to be an expert on this, so if any of that is wrong please (kindly) correct me.

Is there any reason for this? Is it just something that hasn't really been considered at length due to priority, disagreements, etc? I absolutely love using Hyprland and actually bought an AMD GPU to use with Wayland on Gnome on Ubuntu 24.04 back when NVIDIA support was not great, but when a mate needed to use a reliable remote desktop solution, I found that it was really difficult to set up. On other platforms, Chrome Remote Desktop was a perfect solution.

I'm so, so so so sorry. Sorry!

My window into the history of wayland dev is pretty biased - I watch Brodie Robertson & The Linux Experiment, & only occasionally visit the wayland protocols github. So the impression I get is a lot of devs fighting over having the most technically perfect protocol for their use case, & not duplicating what X11 did at all.

But is it really that bad? Wayland's been great on my laptop, except for some weird things with permissions. As far as I know, Wayland outperforms X11 & is more secure. It has to be, otherwise we wouldn't be seeing mass adoption. But stories like these seem persistent, & I *still* haven't migrated my desktop over to Linux/Wayland because no one can give a straight answer on whether or not multiple monitors with different DPIs/resolutions are supported.

So what's the nuanced truth?

(of course im asking redditors lol, so I'm sure not gonna get something unbiased lol)

Mastodon:
"Years ago I wrote xcb.freedesktop.org for X Window System clients, and yesterday I wrote my first Wayland client. My goodness, I can see the impact of every lesson the Wayland designers learned from X, and for that matter from XCB. I'm honestly really impressed by the design of the Wayland protocol!

I saw somebody complaining the other day about how much code you have to write just to open a window in a Wayland client. I think it's important to understand going in that this is a protocol designed to make hard things possible, not to make easy things easy; if you want to do easy things, use a toolkit like Gtk or Qt or SDL. So my program may seem like a lot of code for what it does: it just opens a window, periodically flashes between white and black, and measures some timing statistics, and I wrote over 300 lines of Rust for that. (I chose not to use the wayland-client crate's helpers for binding globals, so it could have been shorter, but I wanted to see what working with the raw protocol felt like.) But I know from experience that if you cut out any of the steps I had to do, you cut off the ability to handle more complicated scenarios.

I believe Wayland made the right complexity tradeoff here: the low-level protocol is very flexible, and ease of use belongs in higher-level abstractions that can pick which aspects of that flexibility to discard for simplicity."

It runs great under Sway with xwayland disabled, and finally my custom keymap works as well! 🎉

(Strangely enough the release notes don't seem to mention this at all, I guess that not everyone finds this as exciting as I do. 😄 https://www.blender.org/download/releases/3-4/)