I had good luck walking my nephew through installing and setting up arch. Great introduction into linux, he was 13 but thats close enough to the given range
it’s not unheard of, multimedia is actually a pretty decent target, however this is due to a lot of media libraries being ancient even in deployment (see the libwebp stuff recently in chrome). However with stuff like mkv which is something that gets updated often, the risk is significantly lower so long as one is up to date. There are lots of people running outdated software which could be susceptible to these attacks.
this is probably actually the fault of wayland and it’s fragmentation issue. Various wayland compositors have different methods of interacting with them and this includes remote/virtual input. Because of this fragmentation a lot of developers have just started to kinda give up, on wayland.
for this one specifically, I would assume any virtual input would work? there are a couple possible routes forwards, the easiest is probably using XDG’s RemoteDesktop. However not every compositor implements this, Sway will be getting it soon (or already has it using luminous). There are also numerous compositors that don’t support this.
you have wlr-virtual-{pointer,keyboard} which works on sway and mir, and thats it. I believe there was a compositor that could do this over dbus too?
the reality of wayland is, if it’s not in the core protocol, you aren’t guranteed to have support, and if it is in the core protocol, you still arent guranteed to have support, but the chances are better
interesting, do you know what they were using for input? if they have an encompassing solution that could be great. if they just use xdg remotedesktop, well thats about what I have now anyways T.T
I guess AOSP is barebones, but it’s not like anything is being abandoned that matters, AOSP itself is still alive, kicking, and thriving. Interesting to hear that people consider Android, AOSP + proprietary bits. It’s not something i’ve used myself