Not okay.
1,140 karma · joined September 15, 2009
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.)
ML/LLM does not fundamentally understand the code. It has to be trained based upon contextual information as to what the code is doing. There are already researchers experimenting with "poisoning" ML models.
For the industry, it just means that a lot of people who _cannot_ code (IE, they haven't the skill, training, or experience to do it) will "start coding" and launch products. Then, when it breaks they'll have to rely upon someone who actually understands why the edge-case bug happened.
ML/LLM are awesome foot-cannons. They have their place, but like a firearm — their 90% use-case will be to cause harm to other individuals (directly, or indirectly).
I'm thinking of various sites that need a "script" condition for domain logic. Like, "this coupon applies when your cart contains 5 items worth at least $5 each". If the client tried to write the logic for that they'd have no clue how. But a graph editor would be make that user-friendly.
There's just not a lot of FBP stuff for PHP, even though it's a popular language.
However, most our use cases would be in PHP apps. I see that you’re working on a code generation API. Would that be the step necessary for generating the PHP invokable code?
> * Professional dishwasher rinse aid causes cellular cytotoxicity and directly impaired barrier integrity of gut epithelial cells by damaging TJ and AJ expressions in daily exposed concentrations. > * The underlying mechanisms of epithelial barrier disruption in response to rinse aid were cell death in 1:10,000 dilutions and epithelial barrier opening in 1:40,000 dilutions. > * The alcohol ethoxylates, an ingredient of the rinse aid that remains on washed dishware, caused the gut epithelial inflammation and barrier damage.
It appears to be the rinse aid when used in professional dishwashers utilized in restaurants, etc, due to high concentration of the rinse aid contaminating the "clean" dishes.
Not all bread is made the same. Not all bread ingredients are the same. Those individual ingredients can be processed as well. The more processing on the ingredients and end product, the more "processed" a food is. I'm not even touching "highly processed" or "ultra-processed" foods in this short post.
2002 Corolla (used) - rock solid reliability, only cosmetic issues with vinyl and a need for break pads.
2013 Elantra (brand new) - reliable, except for an electrical issue caused by an off-brand Rocket Fish (Best Buy in-house brand) car charger for my phone. The charger would send dirty electrical signals back into the car, and the new 1st generation power system would trip up... and I wouldn't have climate controls, defrost, wipers, stereo, etc for a random amount of time. I eventually reproduced it for the dealership, but was told by Hyundai that they wouldn't do anything since it wasn't a "defect". I traded it in ASAP for the next car, while it still had trade-in value.
2013 Civic (used, current daily driver) - so far rock solid, except for a tendency to burn up the brake's rotors. I had to replace calipers, pads, and rotors shortly after purchase of the vehicle (they were brand new at purchase IIRC). Occasional power system (maybe the battery?) issue where the airbag system shuts off randomly at start up.
I'm definitely cautious about buying a newer car now. I always try to review the lists at CarComplaints.com when considering what I might want to look for.