Not okay.

Remember back when it was controversial to apply sales tax to online shopping? The biggest lobbyist against it was Amazon, which they marketed as fighting for the market against the government. Then they got big enough to survive a reversal ... and swung the other way to weaponize the law against their smaller competitors.

They've done a lot more than this, including creating their own brands to inject into a successful niche product or segment. They did all that off of sales/product data they aggregated from all sales on their platform.

Amazon is a dirty player in the market, and everyone should remember that.

If AI crawlers want access they can either behave, or pay. The consequence will almost universal blocks otherwise!

I have some pretty old photos I may have to pull out and upscale. They're from back in the old 1MP camera days.

I want to see a security researcher play with it though.

So far, I'm not a fan of Windows 11, Windows+AI, etc.

We've built sites for clients both huge and small. Our clients like WordPress because it's well supported, easy to roll out, and easy to find someone to work on. Lots of people have experience with it, from having their own blog.

Even infrequently updated content can go through a logjam of revisions. And this is the failure of WordPress's versioning model: there's no way to "check in" a revision. So you can't mark what's approved/reviewed. Instead of a "check in" that nukes the middle revisions ... now you have 5-7 revisions where someone updated a button text.

Add in ACF fields (which uses approx 2.5 rows in post_meta PER FIELD) and now you've got a complex page with lots of rows that build it up. Now each "revision" is 1 post row + 20 - even 1000 post_meta rows. You see the problem.

Over time the DB bloats, and the index isn't partitioned in any way. That page a cheap dev built to query something? Runs 5x slower after a year, and the client doesn't know why.

The only reason we use WP over other platforms is: support, maintenance, but most importantly to the client COST.

But still. A lot of small companies only pay $20/mo for hosting …

But neither are highly customized WP hosting platforms.

Revisioning, especially since the post_meta table was added, is a huge burden on the DB. I’ve seen clients add 50 revisions, totaling thousands of revisions and 200k post meta entries. Important enough to call disabling it by default a “cancer”? Chill out Matt.

Revisions aren’t relevant past revision 3-5.

I bet they need to look at 30-45g sugar harder now. Maybe uncover some of that (big sugar suppressed) research that it causes heart disease.

Any time that happens to me, I flag sensitive content. And then I block the user—so I don't need to deal with it.

I see this as punishing people who're not following the terms, not gatekeeping.

> Please don't use HN primarily for promotion. It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity.

There's an entire "Show HN" part of the site for self-promotion of a project. https://news.ycombinator.com/show

You're simply posting your podcast as self-promotion of each episode, assuming that we're interested. I suggest you try a "Show HN" approach, and let _others_ post links to episodes they're interested in. If you don't, you'll hit a wall for self-promotion and get flagged/banned. (Eventually.)