- You want to know this before water is on the floor.

- Sump pits tend to be splashy in heavy water flow.

- The float switch will correctly return to "it's fine" status when the problem is no longer occurring.

Liquid sensors are great for "my basement is flooding", float switches are great for "I need to fix my pumps before my basement floods.

And a key aspect that modern setups often forget: Every single different UI your users see makes them easier to phish. One of the reasons Entra is so easily phishable is Microsoft uses like 500 different domains for their cloud platform, so the one in the mix they don't actually own isn't obvious to the average user.

1. Finding out a company wants several grand to flip the "allow SAML" switch on the tenant config, and a few thousand a year in additional licensing to leave it on. (I had a vendor both tell me it "takes five minutes" to get it set up, and then quote me $4,800 to "implement" it.)

2. Having to yell at the SaaS vendor for routing the identity connection between two or three other identity providers in different various clouds because, you know "modern stuff". (A vendor I am working with has not less than five different accounts to access various parts of their infrastructure, none of which are connected at all. I assume people there listened to "switch to OIDC" nonsense, completed half the job, and now have OIDC sites and SAML sites forever.)

3. Discovering the SaaS vendor knows how Entra works, how Okta works, and how Google auth works, and having no idea how SAML works. Or OIDC or anything else for that matter.

4. Eventually finding an engineer far enough from the sales and implementation teams who can answer how the product actually works. :D This point is reached after a lot of yelling.

https://www.war.gov/News/News-Stories/Article/Article/428899... (Microsoft has solely discontinued this practice for the DoD tier. Commercial, GCC, and GCC High are still impacted because foreign labor is cheaper than the risk to your security.)

(Or to be more clear, it is mostly unacceptable for an enterprise product to have opinionated decisions about what authentication it works with. You either work with what we use or you are not viable as a product for our need. It's kinda simple. I would expect someone whose authentication was OIDC-based to be similarly dismissive if you told them you only would do SAML.)

Your best case scenario with fines is getting them into the narrow definition of compliance just until a new "innovation" gives them a different way to conduct the same abuse while evading the letter of previous judgments.

But again, if the advertised price must be the total price, it doesn't matter if there's a mailbox access fee or not. It's no different than if they eliminate the fee but raise the price the same amount. Make the advertised price be the highest price, and say "hey, you can advertise discounts off of that".

Nobody's going to advertise you can save $5 a month by eliminating your mailbox.

A similar effect, would be no longer advertising a plan's price if you enable paperless billing and autopay. You'd have to advertise the price without, and then can offer discounts for those things.

Or movie ticket prices being required to be listed with the convenience fee included, and if a theater wants, it can advertise a discount for buying a ticket some other way. More than likely that would just kill convenience fees.

A friend of mine has recently lamented the idea gas stations can advertise "with car wash" pricing on top with what is "fine print" on the sign, which looks good but isn't when you factor in the cost of the car wash.

Another favorite is the personal loan ad, saying you're preapproved for a loan as low as 6% APR but actually you can be denied and the loan could be up to 36% APR even if you get approved. Nonsense.

I don't have a huge problem with a discount for car washes but the advertisement should be an out the door price or rate. Similarly I don't mind capped or content-restricted data plans, but the advertised price should be the unlimited one.

I don't think we should decide what businesses can sell, but we should make it very hard to mislead on the ad. Force advertisements to be the highest price instead of the lowest price, and you'll find companies finding ways to remove fees from the table themselves.

Technologists need to aggressively reject solutions which don't spread freedom to ordinary users as well.

Playing at their table is a losing game, the house always wins.

It's a joke, but like, after nearly two decades of engineering I have something break on me, due to updates. I figure the updates broke it, call the vendor, and they go... did you try rebooting it again?

Rebooting it a second time fixed it.

I think you are missing the point. When I state my Exchange server is more reliable than Exchange Online, I don't think I'm a better engineer. I recognize Microsoft has harder problems to solve than I do. I think building overengineered, oversized SaaS environments is introducing extreme risk. It's an inherent flaw of the current approach.

Smaller is, in fact, better, because it's easier to operate reliably.

Paradoxically, as long as WebKit is mandatory on iOS, the open web is safe: Websites have to build for a lowest common denominator standard instead of building for Chrome proprietary APIs.