t0k0l0sh

Agreed, perhaps it's easier on a mobile device but I found the first two levels after the tutorial way to fast using a touchpad and left a little frustrated :-(

Easing into the difficulty slower sounds like a good plan!

I don't think the specific section needs to mention it - the entire page is about Advertising on Steam, which according to the opening paragraph, includes in-game adverts. The rest of the page elaborates with examples of things they do and don't condone.

These ads are indeed paid for by the company itself, but seem to be permitted by the policy. The intent/spirit of the policy seems to be to prevent games showing ads for arbitrary other games/things, for example BL3 showing ads for Candy Crush Saga - this isn't allowed by this policy, i.e. games that are paid to show other people's ads.

Gearbox showing BL4 ads in BL3 etc, it seems to count as cross promotion, they're not being paid for the act of showing the ad and is OK according to Steam - "These types of promotions are encouraged and many customers find value in them."

Perhaps the wording of the policy could use some work to make things clearer.

That policy covers in-game content too - the same page mentions:

"Steam does not contain any paid advertising, nor are advertising models supported in games distributed on Steam. There are varying interpretations for what constitutes ‘advertising’ in a game, so the examples below are meant to help guide developers as to what is and is not supported on Steam."

Under not supported: "Developers should not utilize paid advertising as a business model in their game"

The Borderlands 4 adverts in BL3 are not paid adverts, and they don't advertise anything other than their own games.

I also have an @ alias on my domains, and give unique addreses to companies/services which identifies them. I'm only had a couple accusations of "fraud", but they were easily dispelled by asking them to explain what "fraud" I was committing (they couldn't) and explaining why I do this.

Addresses which have been lost/stolen and start receiving spam become spam traps, and I change the email address with the company/service to a new alias so their legitimate mail is delivered normally.

In some of the few cases where the loss/theft was identified, it didn't happen at company/service directly, but with one of their suppliers, for example, a breach at the marketing email provider they used.

The interference should be minimal as the microwaves should be contained within the units Faraday cage.

If your microwave is causing interference with your WiFi, it could be faulty and leaking EMR and if so, should probably be replaced as soon as possible!

Self-hosted for about 20 years now. Currently running a few VMs in a Hetzner cloud project built with terraform and managed with Ansible - dovecot proxy, postfix and rspamd on the public host, dovecot with encrypted-at-rest storage (mail-crypt) on the private host and another host running monitoring (Prometheus, graylog etc etc)

It isn't even a Google employee that the author is complaining about - it's a volunteer on the Google support forums. I agree, the author does not come across in a good light at all.

You mentioned receiving 10s of spam per day - are they being classified correctly and put in your spam folder or are you seeing them in your inboxes?

My mx hosted with hetzner also runs rspamd. Of the 32k mails received in the last month, 40% were rejected (postfix DISCARD, so the sender sees the mail as accepted but its sent to /dev/null - this only happens to mails scored very highly as spam, or sent to a spam trap address), 10% were greylisted and 1% were delivered to the spam folder.

So I'm also receiving 10s of spam per day, but they're all delivered to my spam folder with rare errors.

With the exception of an issue delivering to AT&T recently, I haven't had any outbound deliverability problems in a few years, but then again I don't send very much mail at all - perhaps I'd have more trouble if I did but most of my mail is incoming.

I've done the same for about 20 years, usually using <company>@<mydomain> or <theirdomain>@<mydomain>

When I start receiving spam at one of these aliases, I'll update my email address with the relevant site(s), then after a cooldown period to ensure no more legitimate mail arrives at the original alias, I'll use the original alias as a spam trap - any mail sent to it is learned as spam, then accepted and discarded by my MTA.