17,079 karma · joined December 26, 2015
Adding friction to the process (on the advertiser side) means less money for Google: 1) due to the cost of implementing the checking, 2) because some legitimate advertisers will be falsely denied, 3) because the scam ads were still paying money.
Not adding the friction doesn't seem to come with any serious downside. One would expect that it would, e.g. due to publishers removing the most profitable properties from the ad network or governments legislating this out of existence, but that doesn't seem to happen.
So, given these incentives, the outcome is inevitable.
If Google had to pay a massive fine for every scam ad that gets through, or was liable for the damages the ads cause, etc. - or otherwise had a strong incentive - suddenly there would be enough resources to make sure every ad is reviewed, advertisers that push scam ads get fully banned on the first offense rather than being given second, third, and fourth chances, etc.
Now you can't load the page and can't easily (using only the browser UI) get a link to paste into archive.org or archive.is to read the page.
This tends to be something we see in most incidents, because the cases where someone makes the right choice at one of the points tend to not become incidents.
An interesting thought is that the more obviously bad/incompetent/terrible decisions or (in)actions were involved in an incident, the better it is, because it means more things had to go wrong for a disaster to occur (more slices of cheese in the Swiss Cheese model).
That's the key difference.
The fact that it's illegal limits large scale commercial exploitation, leaving enough room for legitimate distribution that pays the author.
With no copyright whatsoever, there would be a well-organized company with a better marketing department selling their version of your work, taking all the profit, and making it impossible to actually sell it yourself.
Probably not too many, because anonymous political speech from 10+ years ago isn't that interesting. Punishing people a decade after the fact isn't very effective for anything.
It's a completely different situation here.
Apple isn't going to let them build on top of iOS, and anything except those two is dead in the water because it'll never have users because it is missing a bunch of critical apps, and will never have those apps because it doesn't have users.
My goal is something that would work for startups that plan to grow beyond a single person/single server project. If you build the architecture for a too small size, you start running into walls as soon as you exceed that size.
But even if you are small, you probably want some kind of Grafana/Prometheus monitoring to tell you what's breaking. You want your framework pre-wired so it automatically reports data (e.g. requests/failures per service) without you having to set it up, because it it isn't automatic, you probably won't get around to setting it up until it's too late. You also want some kind of build system, CI/CD to handle deployment. An easy way to set up staging environments would be nice. If you don't want to use a hosted forge, then a self-hosted forge connected into all this.
My idea is to have one somewhat commonly adopted stack, where most of the stack "self-deploys" so you don't have to set up, connect, and coddle all of these services. If you want to deploy something within the stack, you're somewhat limited because you have to do it "the stack's way", but in exchange, once you've set it up, adding a staging environment consists of not actively disabling the default staging environment that the stack would set up for you otherwise, and once you've deployed your service, it's already pre-wired into your monitoring.
Popular packages would then over time likely get packaged for this stack, with service-specific monitoring exports (e.g. the postgres container could export query details rather than just the default-collected values like CPU usage and requests-through-the-standardized-RPC-framework).
Is there something similar in progress for a "tech company tech stack"? As in, rather than trying to assemble your own custom infrastructure by finding an RPC system, permissions/group manager, credential management, storage, database, service discovery, job management, monitoring etc. one "opinionated" stack that you can easily deploy, as long as you're OK accepting their choices, with all these parts already bundled and wired up.
https://dafyddvaughan.uk/blog/2025/why-some-dvla-digital-ser...
At all-inkl.com (no affiliation except being a happy customer) I pay something like 8 EUR to get "unlimited" bandwidth (I'm sure if my site caused a problem I'd hear about it, but I can be sure that there won't be surprise bills, and I know I don't have to worry about "background noise"), static hosting, dynamic and database (which I don't use) hosting, and 5 domains included which makes the net cost of the hosting nearly free.
Without penalties, e.g. Hertz has little reason not to keep 10+ years of drivers licenses just in case they come in useful in a fraud case or as ML training data later. If having the data was a $153 million liability, they'd think twice.
The Android/iPhone duopoly is nearly impossible to break because very few people want to carry two personal phones, and it takes only one app that they can't do without being only available on Android/iPhone to make it impossible to choose anything else. The app providers likewise have no incentive to support anything else because everyone has one of these two.
Bank apps are the prime example here that's unlikely to start supporting other systems. Public transit (and in some places parking) is another potential problem where even the unhinged "well just change banks to the one that does support your favorite phone" argument fails. ID apps (either governmental or de facto standards like the Swedish BankID) are coming too.
Running certbot on a random PLC isn't happening.
It's also roughly 2800 nautical miles from Kuwait to Diego Garcia, so regardless of where the carrier group is, it should be at most a ~6 day round trip at 20 knots for a supply ship from the closest of the two.
That assumes there is no way to airdrop watertight pallets of food (e.g. steel drums loaded with cans and MREs) into the water, then retrieve it with RHIBs or helicopters.
If they are caught doing it repeatedly without taking adequate measures to stop it, treat them as an accessory to the crime.