wayland-rs VS waylock

I was initially having some problems with kanshi and was thinking about contributing the new features I wanted. For some of the features I wanted, kanshi's internals would have to change considerably. Since kanshi consists of only ~1500 lines of C, I began writing a replacement for kanshi in Rust. After many hours of reading Wayland protocol specifications, working on shikane, some help from the Smithay project and their Rust implementation of Wayland protocols, shikane was able to replace kanshi on my machines. I have been using it for over 4 months now.

Yes, I agree. Since https://github.com/swaywm/wlroots-rs is deprecated, I'm guessing I should use https://github.com/Smithay/smithay or https://github.com/Smithay/wayland-rs. As soon as I find a library that can use the protocol, preferably without extra dependency, I'll switch it to that.

There's also https://github.com/Smithay/wayland-rs

Also there is an incomplete Wayland implementation in Rust, but that isn't very actively developed.

I meant that a standard of some sort is probably needed to handle both the desktop environment telling the display manager to lock the screen AND allowing said display manager to take over the screen and lock it. On Wayland at the moment I'm not aware of any screen locker that isn't part of the DE itself that works on GNOME or KDE (I only know of swaylock and waylock, and both require protocols that are only implemented by wlroots based compositors, at least according to Waylock's readme).

I only know about waylock, didn't try it though