fredsted

There's an exploit freely available already, by the way. You can't contain things like this.

If not, you or our agent could build an exploit from the information that's already out.

I've used Safari since I switched to Mac in 2009. It's always been fast and smooth, and the integration - like password sync and SMS 2FA keys - works great.

It's wild that you are on antidepressants because of your job. Have you looked in to side effects and how hard they are to quit? I think you should quit both the antidepressants and the job. If you can't quit the job, don't make it the source of your personal worth, like other commenters say. You're selling your time for a salary. It's not that serious. If you're not getting any negative feedback, they're probably happy with your effort.

I see EU always regulating all sorts of things, ostensibly to help consumers, but why aren't they doing something about scam airlines like Ryanair?

It's a little too on the nose, isn't it?

We simply can't have an Internet where you'll need to comply with 100% of legalisation of all 193+ countries at all times; it's untenable.

For ofcom, 4chan is just a sticking their toes in the pool. If they fall, ofcom will have complete freedom to censor the entire Internet as they wish. It's madness.

That is released in May

It's wild because saying that NAT is required kind of admits your machines are vulnerable on the LAN! You should have good firewall rules no matter what.

Cool post. So much could be done on a couple hundred megabytes of ram back in the day, with spinning rust as storage to boot!

What you connect to first is the exe.dev jump server/management interface. You can ssh into your vm from there. Try typing help

It's kind of funny our experiences are so diffent. I almost immediately surmised it's some sort of on the fly generated vm you can access via a ssh jumpserver. Which it is! It's actually really neat. It's quite obvious that the authors want us to just ssh into it and try it out first.

> After that incident, I created an incident review document and suggested a small review of the tasks that should be prioritized to prevent it from happening again. I got carried away and created an initial presentation for the other backend Chapter Leads with a backend strategy. I do not remember it perfectly, but it included hexagonal architecture, a testing pyramid with contract tests to avoid breaking APIs used by mobile apps, and more

Definitely got carried away. When coming to a new org, it's always good to learn the ropes a bit before fatiguing the team with more work, processes, and burdens.