It takes over port 22 on the Tailscale interface only. Only had problems with this when I’ve wanted to hit a host’s non-Tailscale ssh service via Tailscale. Otherwise it’s been great for me
I don’t think they were making that comparison, rather that touristy cities have more pickpockets, which is obviously true and expected.
You seem to be very sensitive when it comes to anyone that might deign to question the supremacy of the US and very quick to disparage those outside of it.
Steam machine is a console:
- homogenous and standardised hardware
- vendor backed compatibility certification programme
- standardised OS with atomic, image based updates
- plug in, login and play your library potentially without touching a mouse or keyboard
- HDMI CEC out of box
- controller integration with instant sleep/wake (as seen on steam deck)
- operates quietly
Steam machine is a PC (not like a console):
- not priced as a loss leader
- runs any desktop OS
- it’s a PC
You can do all of this out of box, it’s turnkey, it’s primarily a console experience but a PC if you need it. My point was that comparing this to a prebuilt or BYO PC is like comparing a console to a PC. Different value prop.
This is false in my experience. You can use the cli to clear the quarantine bit, or you can take the (admittedly annoying) trip to system preferences to override. This is rarely something I need to do; most software is already signed and notarised.
Also not at all equivalent to being forced into linking an online account before being allowed to use your computer at all.
The sugar you get from fruit is also accompanied by fiber, water and other nutrients. Also harder to overeat and generally gets released into the bloodstream more slowly. I think the argument here is to eat less (highly) processed food in favour of whole foods.
Agreed. Recommendations to use Arch-based distros especially. My personal recommendation, which has ended up sticking for a few Linux-curious gamer friends, has always been Bazzite.
> Vercel’s internal OAuth configurations appear to have allowed this action to grant these broad permissions in Vercel’s enterprise Google Workspace.
This was an interesting tidbit too. If true, this means that Vercel’s IT/Infosec maybe didn’t bother enabling the allowlist and request/review features for OAuth apps in their Google Workspace.
On top of that, they almost certainly didn’t enable the scope limits for unchecked OAuth apps (e.g limiting it to sign-on/basic profile scopes).
The universe didn’t offer a manual, but mankind has largely arrived at some orthodoxy for the most efficient and ergonomic ways to fret, bend, pluck, tap, strum, etc. In many cases, these are objectively better techniques to use once mastered, but they’re not the only way.