Or they changed the headline and due to caches CDNs or other reasons you didn’t get the newer one.

archive.today has your original headline cached.

Thanks for posting. While it’s a needlessly provocative headline, if that’s what the article headline was, then that is what the Lemmy one should be.

That is odd. It’s not what I see:

A very poor Lemmy article headline. The linked article says “alleged” and clearly there were multiple factors involved.

deleted by creator

Inflation has been falling for a couple years and is fairly low right now, though not as low as it was back when interest rates were zero.

https://www.statista.com/statistics/273418/unadjusted-monthly-inflation-rate-in-the-us/

The dollar has been fairly strong in recent years.

https://www.marketwatch.com/investing/index/dxy/charts

Inflation in 2022 was likely due to price gouging with companies like Exxon Mobil reporting record or near-record profits at that time.

https://www.macrotrends.net/stocks/charts/XOM/exxon/gross-profit

By late 2022, companies had jacked up prices high enough that the demand curve had likely reached the “crossover” point. Since then prices and inflation have been falling back to normal.

Plenty of adblocker extensions on iOS Safari.

For YouTube, I’d recommend Vinegar, although the more general adblockers will also work.

deleted by creator

Arctic has keyword filtering.

Your wish is granted.

https://www.cnn.com/2024/07/31/investing/boeings-losses-new-ceo/index.html

As announced earlier key board members are also resigning.

Have they rotated the deck chairs on the Titanic, or is this a meaningful change?

It’s about guys who deliver money to banks.

But chiles are hot!

It’s a PR issue not a legal one.

This draft spec was eventually published as RFC 9562. Compared to the previous spec it adds versions 6, 7, and 8, plus best practices guidance.

Basically, there are a bunch of UUID alternatives that arose to fix the problem that UUIDs are bad for use as database keys in large tables (here’s the perspective of MySQL experts Percona). A bunch of these alternatives are actually linked from the RFC, which I haven’t seen done before. Version 7, in particular, is meant to address this use case.

Successful malls have an Apple Store, Tesla, and Louis Vuitton, which tells us something about who can still afford to shop there.

Apparently there’s a recipe on that page. Here’s the same page without the crud: https://www.justtherecipe.com/?url=https://houseofnasheats.com/brazilian-lemonade-limeade/

There also needs to be some way to indicate that a JSON construct is a Set, Map, plain object, or array. You’d want a date/time type as well.

Without breaking existing JSON parsers, the way to do that is to add metadata like a _type field to an object, or to add a “sidecar” object like superjson does. Which works but is ugly IMO.

Then there’s BSON, YAML, JSON Schema, and the one we don’t mention ₓₘₗ. To my knowledge all of those could be extended in a way to support new types, but require the producer and consumer to both understand and follow whatever convention you use. They lack the universal interchangeability of JSON.

Set and Map would be more useful if they were compatible with JSON. I see a lot of people using an object as a dictionary or an array as a set because of that.

Sometimes it’s the only option or the preferred option.

I haven’t. Maybe someday I’ll be willing to, but not today. It’s a hassle and extremely intrusive to provide my bank statement and photo ID to a company whose security I don’t trust.

That’s usually how I pay if someone requests money. Venmo is owned by PayPal but my account there works just fine.