Seems you're right. They have done this in the past though, so wouldn't exactly be a surprise.
Here is what the "free speech" platform have censored previously on GitHub:
> X Corp. employs various technical protection measures to control access to its copyrighted works, including those at issue here (API schemas and platform content): e.g., official X Corp. API key/OAuth authentication, rate-limiting mechanisms, proprietary behavioral pattern detection, TLS fingerprint validation, and x-clienttransaction-id checks. The repository referenced above appears specifically designed to circumvent these measures using browser cookies, curl_cffi TLS impersonation, fake headers, request jitter, and reverse-engineered GraphQL queries.
Here is what the "free speech" platform have censored previously on GitHub:
> X Corp. employs various technical protection measures to control access to its copyrighted works, including those at issue here (API schemas and platform content): e.g., official X Corp. API key/OAuth authentication, rate-limiting mechanisms, proprietary behavioral pattern detection, TLS fingerprint validation, and x-clienttransaction-id checks. The repository referenced above appears specifically designed to circumvent these measures using browser cookies, curl_cffi TLS impersonation, fake headers, request jitter, and reverse-engineered GraphQL queries.
https://github.com/github/dmca/blob/b2c88bad7dd771dc7d1842ff...