One cafe in Tokyo is asking customers to leave negative reviews on Google and Trip Advisor to prevent over exposure (it mostly works but made me curious enough to visit).

Another specific $10 Michelin guide ramen restaurant only lets you order from a vending machine outside using a payment method you can’t access as a foreigner (one needs a physical JCB card or QUICPay - EPOS/Suica/Pasmo/Cash etc wouldn’t work).

A matcha place I like only lets you order from the real menu after you’ve unlocked enough visits from a punch card.

A resort slightly off but near the beaten path markets itself as an onsen but that’s maybe 4% of the amenities. That said, they’re serious about “no entry” if you have tattoos.

And a few more of the seedier bars just have the (time honored) “no foreigners” sign out front.

I have yet to find evidence of cmake solving a problem (or even having design), though I guess `ccmake` would be kind of cool if it weren't full of nonsense?

You entice the customer with the lower price, and once they have committed, you can hit them with another charge or fee without as much ramification.

Restaurant customers can be price sensitive, so tipping is a way to advertise a lower price that isn't actually real. Also, it's pretty ubiquitous, so unless you heavily advertise a no-tipping policy like Kroger delivery, most people will assume tipping is required, and factor that into your now higher price.

So it's better to have "api.example.com" and "www.example.com" kept separate, rather than using "www.example.com/api/", where API requests will have inflated headers.

/mnt came first. and distros started mounting stuff into it. but actually it was never meant to be used for that. it was supposed to be an always empty directory where a sysadmin could mount something temporarily if they needed it.

so distros moved away from /mnt and started using /media

then /run was invented as a place for all that semi-automatic temporary stuff that needs a place while the system is running.

by looking at where a distro mounts stuff, you can see how long they have not bothered to follow changing standards.

At MailPace we already enforce DKIM, it’s pretty basic stuff. But list-unsubscribe is optional for our senders.

We can make this a requirement and manage lists for senders who don’t / can’t implement a webhook to handle it (we already default to blocking resends to emails that hard bounce).

However I am curious how Google will track this. Just because the header is set, it doesn’t mean it’ll do anything. In fact it can be used by spammers to identify legit email addresses and spam them separately.

That doesn't make any sense. If it is a setting that influences the system it should be a system setting not in some different program I might or might not use.