@hipsterelectron@circumstances.run
2025-08-19 15:24 UTC
@astraluma@tacobelllabs.net @pypi@fosstodon.org they describe the number of users they've locked out of their accounts as if that indicated the prevalence of risk, even though they admit their domain expiration classifier is a third-party service which just makes up an answer since domain expiration cannot be determined by a third-party service. they don't seem to have evaluated the error rate of the third-party service, either for type I or type II errors, and since fastly's pypi cache broke support for negative range requests it's unclear whether this separate fastly offering will also break support for other web standards
Replies (1)
-
@hipsterelectron@circumstances.run 2025-08-19 15:28
@astraluma@tacobelllabs.net @pypi@fosstodon.org i loled at "(initial 1,500 excluded from chart)" as well as the "note:" which mentions the domain expiration status is completely made up placed immediately under the deterministic flowchart that takes up 3/4 of the screen. that's some certified data-driven decision-making