lemmy.ml is hosted in EU, and lemmynsfw.com uses CloudFlare, which operates in EU. Worst case, issue a GDPR request to both.
I do not have notes from that time anymore, sorry. I do recall though that after following a chain of citations I ended up at the paper in the center of this controversy. Nobody sane would cite in now except to point out its flaws, but if there’s a modern paper that cites a 10 year old paper that cites a 30 year old paper that cites it—people usually won’t notice.
From my experience, despite all the citogenesis described in other comments here, Wikipedia citations are still better vetted than in many, many scientific papers, let alone regular journalism :/ I recall spending days following citation links in already well-cited papers to basically debunk basic statements in the field.
I’m surprised federation isn’t based on asymmetric cryptography. Let the public/private keys identify instances, as opposed to domains that risk being blocked by governments or bought by malicious third parties if the instance owner forgets to prolong it.
With that, implementing a change in domain names would be simple.
He likely couldn’t “just” do it. The synchronization overhead for federation is large, and with the amount of data Reddit has, you’d have to put a lot of effort into writing efficient code to handle that. Or pay for a lot of servers doing it.
BTW, it would be interesting to see whether current lemmy codebase could handle it as well…
We found that flakiness of e2e tests is usually caused by using libraries, frameworks and devops tools that were not designed for being integrated in e2e tests. So we try to get rid of them, or at least wrap them with devops magic. This requires a skilled devops team and buy-in from management.
At some point we were also solving the issue by having dedicated human reviews of e2e failures, it’s easy to train a junior QA engineer to have most false positives quickly retried.
But we would never give up on e2e.
Indeed. Most of the web is broken under GDPR’s privacy requirements.
GDPR believes an IP address is a private information. This can be used to mount a legal attack on EU-hosted lemmy instances.
This plea for help is specifically for non-coding, but still deeply technical work.