If you're mixing a dedicated GPU and onboard graphics you need to set the dedicated GPU as primary somewhere, otherwise all screens get rendered on the onboard and "reverse PRIME'd" to the dedi GPU outputs.
I'll see if I can find the snippet that fixed this for me.
So add your user to the new docker group made on install of that package and you'll be able to docker without sudo.
You may need to relogin or newgrp docker before it works tho
Yeah I'm still not over losing my notification led either. Was a staple of the android experience imo
I find myself using this often when talking about Jr devs or Jr sysadmins
Can you really not read any of the compiled code tho? Like if I take the binary, put it in ghidra and use that to reverse engineer something, is that not clean room still?
I remember watching Halt and Catch fire where they had 1 group writing specs for what he REed and another group would write that code according to spec.
Holy crap I wasn't ready for that. Great rec tho
How'd you get my shell history?
N64, and no I'm still not sure how to hold it, I always end up walking funny.
Similar story for me, Ubuntu w/ wobbly windows and desktop cube in Jr High (I was a particularly nerdy kid), arch w/ i3 in HS and college, now I'm a DevSecOps Developer (engineer is a sacred term in Canada)
Learning to do naughty things to the WEP wifi around me is what led me to now doing penetration tests at my org.
Funny how goofing around on a computer as a kid can lead to careers and passions.
This also adds the benefit that any other devices that wanna VPN can just use the gateway
I've read some of the comments and it sounds like you've already tried installing proton VPN and tailscale on the same machine, but depending on your setup maybe you could make a "VPN gateway"
Like take your pi, install protonvpn, then enable IP forwarding and use a little nat IP tables script to nat your lan to your proton VPN interface like a home router would with the wan and lan ports.
Then on your tailscale gateway set the default route to be that box instead of your normal router. Then just use the tailscale node as the exit node on your client and check your IP.
In theory this would be similar to a qubes type setup which is what I tend to use for this kind of work.
We use gitlab ultimate at my work, I'm the main admin of the instance. Like 2 weeks ago when there was the cvss 10 vuln, gitlab sent us a .patch file to apply to the instance instead of releasing a new minor cause they didn't wanna make the vuln public yet. I guess that's coordinated disclosure, but I still found that remarkably jank.