gslin

https://archive.is/O2BFs

https://archive.is/dR2J2

https://archive.is/YGPLM

https://archive.is/q3VyO

https://archive.is/3ZeOv

https://archive.is/TYcpI

* https://dagster.io/blog/fake-stars (2023) - Tracking the Fake GitHub Star Black Market with Dagster, dbt and BigQuery

* https://arxiv.org/abs/2412.13459 (2024/2025) - Six Million (Suspected) Fake Stars in GitHub: A Growing Spiral of Popularity Contests, Spams, and Malware

https://archive.is/Fz65d

https://en.wikipedia.org/wiki/Goodhart's_law

Any observed statistical regularity will tend to collapse once pressure is placed upon it for control purposes.

Using timezone not UTC for a global service is a crime, especially mixed with daylight saving.

archive: https://ghostarchive.org/archive/F9qjY

https://ghostarchive.org/archive/F9qjY

More similar optimizations: https://matklad.github.io/2025/12/09/do-not-optimize-away.ht...

Quote from the first paragraph:

Today, we’re announcing Amazon Route 53 Accelerated recovery for managing public DNS records, a new Domain Name Service (DNS) business continuity feature that is designed to provide a 60-minute recovery time objective (RTO) during service disruptions in the US East (N. Virginia) AWS Region. This enhancement ensures that customers can continue making DNS changes and provisioning infrastructure even during regional outages, providing greater predictability and resilience for mission-critical applications.

https://govscape.net/

I believe a report with timezone not using UTC is a crime.

The password `TPL075526460603` is also mentioned in CVE-2022-37255[1].

[1] https://nvd.nist.gov/vuln/detail/CVE-2022-37255

https://crt.sh/?id=20924740030

Also some related news:

* https://edition.cnn.com/2025/01/09/china/undersea-cable-taiw...

* https://www.bbc.com/news/articles/cwy3zy9jvd4o

For English translation about incidents, Google Translate for entire website might be helpful: https://smc-peering-tw.translate.goog/?_x_tr_sl=auto&_x_tr_t...

Related: https://github.com/letsencrypt/boulder/issues/4620

https://archive.ph/1Wn9v

https://archive.ph/Eaj5C

As in https://mastodon.social/@bagder/114821971646329512

Let's Encrypt issues 9M certs per day (https://letsencrypt.org/stats/), and its market share is 50%+ (https://w3techs.com/technologies/overview/ssl_certificate), so I assume there are <20M certs issued per day.

If all certs are sent to just one CT log server, and each cert generates ~10KBytes outbound traffic, it's ~200GB/day, or ~20Mbps (full & even traffic), not in the same ballpark (2-3Gbps).

So I guess there are something I don't understnad?

You Should Run a Certificate Transparency Log

And:

Bandwidth: 2 – 3 Gbps outbound.

I am not sure if this is correct, is 2-3Gbps really required for CT?

The original article seems deleted, so https://archive.ph/TTXnK this.

https://archive.ph/DYVba

The latest deployment seems using Service Worker API, which causes broken on "old" browsers because the API is not supported on these browsers.

Some people like me who block Service Worker API all the time are also affected, like https://chromewebstore.google.com/detail/no-service-worker/m... this.

https://archive.ph/tnrJN