![](https://lemmy.hogru.ch/api/v3/image_proxy?url=https%3A%2F%2Flemm.ee%2Fpictrs%2Fimage%2F8e697087-8375-4e61-a933-bddc9c495d44.webp)
![](https://lemmy.hogru.ch/api/v3/image_proxy?url=https%3A%2F%2Flemmy.ml%2Fpictrs%2Fimage%2Fd3d059e3-fa3d-45af-ac93-ac894beba378.png)
Successful malls have an Apple Store, Tesla, and Louis Vuitton, which tells us something about who can still afford to shop there.
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/
You live in a city, but most of the store chain’s customers live in the suburbs where gas is a major expense and fuel perks are a big incentive to shop at a particular store.
The store isn’t trying to promote fossil fuels. They only care about customer loyalty. Besides (they might rationalize), their customers have to buy gas somewhere so why not from us?
There’s no way Apple lets the automaker access app data from your phone. Apps on the phone can’t even see data from other apps on the phone.
There are two ways I can think of for the infotainment to get the messages. The first is by OCR-ing the CarPlay screen, which is shady as hell. The second is a feature like this one where the car has Bluetooth notification integration.
And of course there have been forges launched, including SourceHut, Gitea, Gogs, Forgejo…
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.