Max-P

I got asked the same. I simply pointed out the test is a reproduction of last week’s bug that took down prod at 2am and got paged to fix, and is therefore as realistic as it gets of what they’ll need to be able to handle.

It’s always DNS, everyone should know that.

I went through hiring several times at several companies, being on the interviewer side.

Typically it’s not the talent pool as much as what the company has to offer and how much they’re willing to pay. I referred top notch engineer friends, and they never made it past HR. A couple were rejected without interview because they asked too high of a salary, despite asking under market average. The rest didn’t pass HR on personnality or not having all the “requirements”, because the really good engineers are socially awkward and demand flexibility and are honest on the résumé/CV, or are self taught and barely have high-school graduation on there (just like me).

I’ve literally seen the case of: they want to hire another me, but ended up in a situation where: I wouldn’t apply for the position myself, and even if I did, I wouldn’t make it to the interview stage where I’d talk to myself and hire myself.

Naturally the candidates that did make it to me weren’t great. Those are the people that do the bare minimum, have studied every test question (without understanding), vibe code everything, typically on the younger and very junior side. They’re very good at passing HR, and very bad at their actual job.

It’s not the technology, it’s the companies that hire that ultimately steers the market and what people study for. Job requirements are ridiculous, HR hires engineers on personnality like they’re shopping for yet another sales associate, now it takes 6 rounds of interviews for an entry level position at a startup. VC startups continue to pay wildly inflated wages to snatch all the top talent while established companies are laying off as much IT staff as possible to maximize profits.

The email used to be used to send you notices if your cert wasn’t renewed and other communications. They’ve just discontinued that feature, so the email isn’t super important.

It’s a good idea to provide a valid email address, but it’s not that important and doesn’t really matter for the purpose of issuing a certificate. It’s not part of the problem you’re having.

D’après moi il n’a pas intercepté en tant que tel, l’un des deux côté est infecté et quelqu’un dans les courriels ou active la fonction pour transférer tous les courriels entrant à une autre addresse. Ils pourraient aussi avoir ajouté l’adresse courriel dans une autre banque et supprimé les messages de confirmation, ni vu ni connu. Reste plus qu’à accepter le virement avant la vraie personne, puis virer l’argent dans un compte à l’étranger.

C’est possible d’avoir un compte avec plusieurs banques, alors quand tu reçois un virement tu veux pouvoir choisir quelle banque et quel compte, ouvrant la faille.

Ou bien, y’a pas eu de bug, se sont fait arnaquer. J’aurais jamais payé deux fois: c’est clairement le problème du propriétaire. Je te paye tu te fais voler ton portefeuille 2 min après, c’est pas mon problème.

At the very least I hope it’s hosted by someone outside the US so it’s out of reach to the authorities.

It seems to have picked up “circle” as the distro. You’ll need to replace that with the matching Ubuntu or Debian version of what this version of ElementaryOS is.

The default behaviour for SIGTERM (and most other signals) when unhandled is to terminate the process, so you might as well be sending SIGKILL. It won’t keep running unless specifically coded to catch the signal and do nothing with it.

A lot of GUI apps unfortunately don’t catch SIGTERM, so it doesn’t make much of a difference. A lot of them put their “exited normally” into the “the window was closed” handler.

For GQRX that might even be intentional, it’s very unstable at times, and you do kill it pretty often. So they probably assume if it got SIGTERM, it was frozen and the WM offered the user to kill it and clicked yes.