Android userland is vastly different from ‘linux’ ie desktop linux people are used to. While there exists unshare/proot based containers (termux is an example) it might not be suitable for privileged features of kernel except for rooted devices.
Chromeos is much closer to desktop linux (init being upstart not systemd afaik) but still the ‘linux’ apps run inside crosvm to keep the locked down nature of the os intact.
My point was that unity was innovative, not just gnome with extras.
Back then I actually liked mir (also unity) personally more than wayland.
Unity was envisioned to become mir based eventually. So they invented a whole new display protocol when wayland was there, vastly immature though :)
It’s opening full for me. Probably geo paywalled…
Goes away with js disabled. Rest of page works fine.
This can be a soft limit where Youtube limits the connection rate so that artificially inflating view count becomes more costly. There are inexpensive ‘services’ especially in India or Pakistan where you can buy human (like a whole internet cafe) view times to your scam video to make it float in suggestions and to promote a channel.
I don’t work for youtube so it is just a guess.
Forget gpus. A framebuffer is all you need :)
Yeah ofcourse firewall is the good idea here. I personally have firewall on on every device so that I can manage what can connect and from where.
The point is though often people just disable firewalls (some distros do not install/enable by default too) to workarround certain issues quickly like kdeconnect not connecting, bridge not working and such. That’s how I think the whole ‘ipv4 NAT is the best (consumer) firewall’ concept came popular.
Say I host a malicious server with ipv6 only. You visit the site without NAT. I get your ip and ip:631 is open (unless firewall and listen is restricted to prefix). Usual attack afterwards.
Edit: You need to have ipv6, for example many mobile networks.
ipv6 doesn’t give the NAT. A malicious website can mount the attack.
newpipe
The text. And probably images too (but the only mistake being the wrong port depiction (all c) says more human).
ai generated lol
It always worked for me except in some cases the ‘hardware’ compositor (ie the wayland side) is a bit buggy for clipboards and inputs in general. I had issues with lxc network in past but that’s long ago.
I still don’t understand what borked your system. Waydroid downloads the images, mounts and runs them inside lxc just like normal android. It doesn’t touch your /usr or anything else. Works well in immutable os too.