Money laundering at the high level works as unless you are on the USA watchlist, it's the USA and it's allies that are the vehicle which facilitates it.
Offshore vehicles? Most are British islands.
Onshore vehicles? Delaware and similar
Unless the west puts you on a list, it's professionals will happily help anyone in the world.
There is no device ID, only ones tied to a user login on a phone, and the app must request a permission to get it. You can, for example, know that the user ID (which you obviously also need to have a permission to retrieve), is being used on the same device as was used to access your service in the past. Or you can know that this particular otherwise-anonymous user/device combination is being used again. I'm pretty sure that's likewise possible on iOS, but folks can chime in.
Not familiar with how Android does it anymore, but sounds fairly similar to iOS.
The main difference is it's opt in on iOS, but opt out on Android I believe.
On iOS, when the app pops up and asks to track, if the user says no, the app can't access the system advertising ID at all, and also is not permitted to track activity via other means like email address, user ID, etc (but the only thing that's technologically enforced is the system advertising ID, it's only forbidden by policy to not use other tracking methods).
Given the huge fit Meta threw after Apple implemented this, while they were silent about Android, I'm inclined to believe Apple's method has more of a privacy impact.
Also worth noting Google is hoping to move away from device-level advertising IDs with their "privacy sandbox" thing.
Yes, specifically both have some variant of "advertising ID", which is shared across all apps. The difference between iOS and Android is that iOS requires you to opt every app into receiving it, whereas Android is opt out. However on top of this Android has a "gsf" id, which is shared between apps, and can't be changed without a factory reset.
YugabyteDB is also a fork of PostgreSQL. Last year, they got around to rebasing from 11 to 15, and spent some time working on better isolating their changes to make that easier going forward.
> When we set out to make YugabyteDB Postgres-compatible, we took a fork of Postgres, and modified all of the operations that use shared memory or storage to instead talk to our LSM- and Raft-based distributed storage and transaction layer.
I take one look at our smartphone/social media addicted society and the damage that does and think of the parallels of forcing opium on a population in the 19th century
Not that the rural third world don’t already have phones. Whether they are engineering to be as addictive as crack like in the west I’m not sure.
Oh, they are already as addictive as crack because Zuckerberg has successfully pushed his social media onto them. And it's very hard to compete with Zuck. The network effect is a very wide moat.
Tesla already buys wholesale electricity for it's charging network and so is leveraging that and it's brand/customer database to diversify and enter the reliable revenue stream that is domestic utility bills?
Perhaps Tesla share price isn't that silly if they are going to be so innovative in their thinking.