zig build

I think a DRE with a doctorate can tell for sure.

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.

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.

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

Afaik steam deck doesn’t have a gps module. You’ve to get any of their identifying information.

What you can do is perhaps sending memes with different cannery token redirects for each worker. Send them around when the device is being used. That way you can compare the grabbed ip with steam log and see which worker’s match. As the deck doesn’t have sim they either will use home wifi or mobile hotspot. Both will work this way.

I’ve a suggestion that might work depending on how honest the perspn hiring the worker is and on their contract. You can tell the person to send some questionnaire or feedback form etc to all of them which will track their ip and name/email (say unique form per worker). Then you can match the ip, as home ips are mostly static for short duration. Tell them to send the form at night or sometime when they’ll be at home and give it a short deadline.

the bad guys use bots or services and are done. regular users have to endure while no security is added

put in other words, common users can’t easily become ‘bad guy’ ie cost of attack is higher hence lower number of script kiddies and automated attacks. You want to reduce number. These protections are nothing for bitnet owners or other high profile bad actors.

ps: recaptcha (or captcha in general) isn’t a security feature. At most it can be a safety feature.

stopping automated requests

yeah my bad. I meant too many automated requests. Both humans and bot generate spams and the issue is high influx of it. Legitimate users also use bots and by no means it’s harmful. That way you do not encounter captcha everytime you visit any google page, nor a couple of scraping scripts gets a problem. Recaptcha (or hcaptcha, say) triggers when there is high volume of request coming from same ip. Instead of blocking everyone out to protect their servers, they might allow slower requests so legitimate users face mininimal hindrance.

Most google services nowadays require accounts with stronger (like cell phone) verification so automated spam isn’t a big deal.

And what will you do if a person in a CGNAT is DoSing/scraping your site while you want others to access? IP based limiting isn’t very useful, both ways.