515 karma · joined April 17, 2017
There is an large amount of history backwards in time, and not a large amount of reliable documentation regarding the amount of partners people had.
Doesn't this just mean that your own preconceptions about those demographics matches the language models preconceptions? How would we know that is matches reality when presented with novel ideas/concepts that we want to get feedback on?
/s
Take for example a database over all mobile phone positions over time, this can be 'anonymized' by removing all connections from the phones to information on who owns the phones.
But it can still be trivially deanonymized by analyzing where the phones are at night and during office hours, not very many persons work in the same building and sleep in the same house.
Here is a thread about it: https://twitter.com/pati_gallardo/status/1501211140310904841
https://twitter.com/oneunderscore__/status/15657972205318144...
See https://chargemap.com/cities/oslo-NO
It's not that hard to build infrastructure to support EVs, since electricity already is everywhere in a city.
https://www.reddit.com/r/counting/comments/ww3vr/i_am_the_be...
Their data model was not designed for very deep comment chains.
Cramming output intended for humans, and output intended for data transfer between processes into the same format makes the lives of both groups of recipients worse.
Maybe dominant is the wrong word, large might be better.
Russia is desperate to deter EU/USA from involving itself more in the war, and the only way it can do that is by treating to escalate to nuclear war.
But that threat is only effective if people actually think that you will do it, so they must play this so that they seem crazy enough to start a nuclear war.
It's a bit like someone blackmailing you for money for something illegal you did together, only way to get you to pay is to show that they are really willing to expose your secrets, even if they might be exposed also. And once you believe them and start paying they will continue to demand money from you.
You can reproduce this yourself with:
git clone https://github.com/cortex/ripasso.git
cd ripasso
git checkout release-0.5.1
cargo build --locked
On my arch system this fails to build with the same errors as the bug report i got, and my rustc version is: $ rustc --version --verbose
rustc 1.57.0 (f1edd0429 2021-11-29)
binary: rustc
commit-hash: f1edd0429582dd29cccacaf50fd134b05593bd9c
commit-date: 2021-11-29
host: x86_64-unknown-linux-gnu
release: 1.57.0
LLVM version: 13.0.0