But a check in or analytic counter wouldn’t stop you from receiving email. This is most likely due to Microsoft’s server (not your local computer) being the one fetching the mail.

It is normally probably more reliable; except when their server is down.

I’m not sure of a way around this. I’ve done it.

I need someone to do a specific set of tasks, but there’s also a wider group of tasks which I’d like someone to do, but it isn’t urgent.

The posting goes out for the task we NEED. If someone more senior applies, and they can do more than the role needs, we pay them more.

This is a non-problem: if a candidate approaches you for Role A, and you decide they'd be a great fit for Role A+B, then create Role A+B, and perform the perfunctory interview, then hire them at the new role.

There is no (and I feel comfortable with this absolute) scenario where you need to keep the salary range hidden, or where a published salary range prevents you from hiring a candidate for an expanded role. None.

The only thing transparent pricing does is result in an informed participant in the market, which is pricing signals and thus something Capitalism.

Once you go down the route of asking for special exemption to make your business work in an open market, you're not doing Capitalism anymore.

It's a bureaucratic problem. Getting a headcount approved for a specific role is a non-issue. Getting HC approved for something brand new might be impressively complicated. Especially at large companies, listed postings persist for many months sometimes and stagnate because functions, dynamics or org alignment shifts before anyone is hired. It's much easier to write a generic-ish job posting and just coach the recruiter/screener on updated specifics than it is to retract a posting, rewrite it, and repost it. This happened to me frequently when I was a hiring manager at Google, for example.

This works for some orgs but not for ones where roles require significant negotiation and sign-off. That can take weeks or months and by that point an attractive candidate has moved on.

To be honest, the places I’ve worked for that could do this were not the best jobs I’ve had. That flexibility can sometimes point to other organizational issues.

The only method left where people can legally spam us, with no legal possibility of opting out.

You can physically remove your mailbox, but then you won't get other mail you might want.

Attach a shredder to your mailbox along with a camera and image recognition. Shred everything that you don’t need.

Defrosting.

That said, there is no reason for that to be remotely activated. You need to empty the freezer first anyway. I’ve had this same fight dozens of times, and with things that could directly kill people.”But we want to be able to update software remotely, and control (dangerous feature) via software.” The only reason iI’ve been able to push back on it is due to mandated hazard logs, which won’t pass with the above implemented.

I was about to ask the GP why is this a ‘public health crisis’, so appreciative of your preemptive response a little scroll down.

I still don’t like calling personal self-inflicted non-chemical things a ‘public health crisis’ because it seems open to so many other things…. But if we ignore the terminology, we’d probably agree about the reality of it being a problem anyway. The lure of pointless semantic arguments is a public discourse crisis.

Along the lines of presentation layer being transient,I’ve been experimenting with LLM and accessibility and screen reader to generate cleaner UIs and APIs. Haven’t spent too long on it, but parts of it seem to work. Speeds the biggest issue.

I haven’t tried this with new LLMs yet.

Maybe won’t work for your site; I’ve been leaving flat files open, putting anything that needs processing (like search and login) behind Anubis.