biscuitswalrus

Snaps are awesome, I need to be on 20.04, or 18.04 for humble, for ROS noetic and so being able to install generic snaps which are fully up to date with modern software is awesome.

I use Ubuntu for ROS and work specific tasks, but I get the fuck out when I want to game. Ubuntu looks like a job to me. Just like Windows looks like a job to me.

But the thing is, that's just me. Can't imagine being mad at someone else for using it, but Ubuntu makes me irrationally mad because it's associated to work.

When I read this first, someone commented that they'd never ever post this. It's like you're admitting you're incompetent.

I tried to read this, but after 30+ years in Brisbane I've never heard anyone utter such nonsense. Mind you, my best friends parents told him his Asian wife will ruin him and take his money. So I'll believe people say anything, but not everyone is worth listening to.

Oh you think you exist somehow outside the simulation and are not just a construct of it. The Truman of the show.

Perfect

What a great post. I haven't used pcsx2 since I wrote a yakuza guide probably decades ago. But that post was great to read.

I feel like you understand the text book but didn't know the application.

I've worked with Windows environments from 2003 until still today migrating to azure. The biggest skills gap with technicians and engineers administrating Windows is actually networking. This single point connects every single service server and user and yet dns, dhcp, routing and it's protocols, link layer technologies like vlans interface configurations aggregation and more is so poorly understood that engineers and technicians often significantly mistake problems. Almost all issues happen around network layers 2-4 or layer 8 (the end user).

It doesn't need to be first but no matter what os or component, networking is core and the single biggest return on investment for systems admin types.

Sure other basic skills are required but just being able to test TCP by telnet or understand each hop, and is the server listening? What process ID is listening? Did someone configure rdp off 3389 and that's why it doesn't work? Was the host file edited and that's why it's resolving some old ip for this hostname? Why is it going out the wan interface of the router when it should be going over an ipsec tunnel?

All this and more has nothing to do with Windows, and yet, anything that isn't just user training or show and tell about how to do something, there's a good chance it requires you to follow the networking layers to make sure behaviour is expected.

If dns resolved then it's not blocked. You need to look at your network.

Bypass dns connect to the ip and port. What happens?

This won't work, your wan ip isn't dynamic, it's on the ISP NAT network and your resulting ip to public services is shared across many customers. CG-NAT.

I don't know where you work but don't access your tailnet from a work device and ideally not their network.

Speaking to roku, you could buy a cheap raspberri pi and usb network port. One port to the network the other to roku. The pi can have a tailscale advertised network to the roku, and the roku probably needs nothing since everything is upstream including private tailscale 100.x.y.z networks which will be captured by your device in the middle raspberri pi.

I guess that'd cost like 40 ish dollars one time.