It’s a delightful PR gimmick by a most definitely not a tech company, since there’s not much cutting edge technology going on in the world of “flamethrowers are perfectly legal in America and that’s our business model”.

In addition to strapping a flamethrower to a generic quadruped robot, they also strapped one to a drone.

Totally agree on the hard line stance on human rights.

I guess I’m just not seeing what you’re seeing. They’re both pictures of people mostly holding signs and peacefully marching. A woman holding a sign and smiling doesn’t scream face smashing to me.

If that was the point they were trying to make, then maybe actually using an image from the stonewall riots might have conveyed that a bit better than two sets of images of people peacefully marching.

Usually this format implies highlighting a significant change between “then” and “now”, but I really think it just highlights “the first picture was taken before 1978”, and and “the specific of the struggle have changed, but not the presence”

I’m not entirely sure what they were trying to highlight.

I kinda like a little thingy that has a USB plug on one end under a cap, and a salt shaker on the other. Or maybe like a little hot sauce shaker, if we’re moving away from salt.

Yeah, look at image before title, wondered if it was a salt shaker and what language uses kalt for salt.

Hrm, USB stick salt shaker…

A partition for each thing you might want to change the size of is my rule, or to be able to wipe independently of the others.

I usually prefer lvm over actual partitions, since it does a better job letting me think about volumes as opposed to devices.

Boot gets a partition because it’s basically required. Home gets one so I can reinstall without mucking things up. The database directory gets one for similar reasons, a d because I might need to scale it up. The system itself gets one because it’s most likely to get wiped or need more space.
Most of these are actually lvm volumes.

fuck like rabid apes

You mean painfully, with jerky twitches, difficulty swallowing and ultimate brain death?

Yup, that’s a really good pattern to follow. Not only does it minimize your exposure behind a secured entry, it also makes sure that all of your access is uniformly authenticated.

You have to do some shenanigans to do something similar with other, non-http based services, but it’s possible with most of them.

It’s not a simple task, so I won’t list many specifics, but more general principles.

First, some specifics:

• disable remote root login via ssh.
• disable password login, and only permit ssh keys.
• run fail2ban to lock people out automatically.

Generally:

• only expose things you must expose. It’s better to do things right and secure than easy. Exposing a webservice requires you to expose port 443 (https). Basically everything else is optional.
• enable every security system that you don’t have reason to disable. Selinux giving you problems? Don’t turn it off, learn how to write rules to let your application do the specific things it needs. Only make firewall exceptions where needed, rather than disabling the firewall.
• give system users the minimum access they require to function.
• set folder permissions as restrictively as possible. FACLs will help, because it lets you be much more nuanced.
• automatic updates. If you have to remember to do it, it won’t happen. Failure to automate updates means your software is out of date.
• consider setting up a dedicated authentication setup like authellia or keycloak. Applications tend to, frankly, suck at security. It’s not what they’re making so it’s not as good as a dedicated security service. There are other follow on benefits.
• if it supports two factor, enable it.

You mentioned using cloud flare, which is good. You might also consider configuring your firewall to disallow outbound connections to your local network. That way if your server gets owned, they can’t poke other things on your network.

Weird, sucks you had a rough time. I’m mostly perplexed about the network card issue, and the monitors. I haven’t had any trouble like that in more than a decade. I’ve honestly actually had more trouble with a new install of windows failing to detect hardware than Linux recently.

References through former coworkers usually.

I met a person at a party who referred me to a job, so I applied. At that job I met another person and worked with them for a bit. They left for a new company after someone they worked with previously got a job there and referred them, and later he referred me. I’ve since referred other people I’ve liked working with in the past to the new place as well.

I’m starting to think we might have different experiences or be in different markets and my advice might not be applicable to everyone. I don’t think I’ve ever actually “looked” for a job, just picked the one I wanted.

I would disagree that devs need a professional linked in profile.
I’ve never had one, and I’ve never looked at one for anyone I’ve interviewed. I don’t think I’ve heard of any of my coworkers doing so either.

Probably all you need to do is check to make sure things look right, and actually test it.

I can’t think of anything else that would be common that you’d want to check. If you’re running weird virtualization setups on your laptop you might have to do more. :P

There are different schemes that different distros use. Some user partition id, some use fire system id, and some use device serial number and partition index.

It might work, but probably not without a little tweaking.

A lot of things will reference drive identifiers or drive path to know where to mount them. These things don’t get copied by dd.

It’s meant as an anti snoring aid. Forces you to breathe through your nose.

It’s a perfectly normal product, if questionable in efficacy since it’s basically anecdotal at best if it actually works.
They’re just leveraging the shock value of the name to get people to click and maybe buy them, since they’re more expensive.

‘Bessie’ is a preposterous name for a chicken.

Ubuntu, mint, fedora, Manjaro are all pretty much in the same class, and it’s largely irrelevant which you pick. They’re all supported, have decent UI for most of what you want to do, and have good documentation for how to do it.

It’s not too difficult to change distros without having to move all your data once you’re switched, so it doesn’t matter too much, and you’ll probably try a couple before finding the one with the best menus for you.

Particularly when they don’t have to be. These relationships are rarely symmetric.

Yellow means it’s complicated, so… It’s complicated.

Positive relations are important to their national defense, and as a NATO member they’re way more likely to let in US bases, and historically have because of fear of the USSR.
Recently, they’ve been interested in close relations with Russia since they’re a nearby economic power, and the US hasn’t been entirely thrilled with that.
They also want close relations with Ukraine, and so have been pushing for a peace with expediency as the goal, which would result in Ukraine losing land. The US is less interested in brokering peace at any cost, and so there’s conflicting objectives.
The US supported Turkish operations in Syria, but has recently taken the stance that those operations pose the risk of destabilizing things further. Similarly for Iraqi operations.

Above all else, the US is committed to liking the positioning of that base in Turkey for the regional positioning it gives them, and Turkey is supremely appreciative of US assets making any attack on them hilariously unlikely.

Each party gets something out of the relationship, but it’s far from a given that they’ll be working towards the same goals outside of “the US should be positioned to protect Turkey”.