No, the error i get is for the url `https://api.twitter.com/1.1/onboarding/sso_init.json` and the error is "Over capacity" code 130. The client keeps looping on this call too so idk if the load will ever dissipate lol.
It doesn't seem to include any backoff, so any browser tab left open on that screen will keep tightlooping on it. Almost certainly exacerbating the problem.
What should my mental model be for "where" the code that causes those repetitive API requests is coming from? JS logic deployed to a CDN somewhere?
If so, seems it may be an interesting question of whether or not it's possible to ship a hotfix (add exponential backoff) to JS asset in time to be helpful in fighting an outage like this.
> Honestly pretty shocked that something at their scale could be depending on Fastly for core assets.
Why would that be surprising? Fastly has many customers of similar scale. Amazon.com has fastly as one of the options to serve as their CDN (as was publicized when a fastly outage took down amazon briefly last year).
Probably reductive but in my head Cloudlfare and Cloudfront are the only 2 "mega large" CDNs and, to your point, I've only ever heard about Fastly in the context of outages.
Just right now logged in, and Twitter proposes next pop-up:[img]
Boost your account security
Protect your account with two-factor authentication. Once enrolled, you won’t be prompted to confirm your identity again. Learn more about #https://help.twitter.com/managing-your-account/two-factor-authentication.
On this floating pop-up URL to help docs inserted with prefaced `#`, turning link into tweet search query:[0]
Its weird.
UPDATE: Twitter again logged me out and continuously flickering with "Error" popup:
Error
Something went wrong, but don’t fret — it’s not your fault. Let’s try again.
UPDATE2: Now (0223 UTC), one minute after previous update, after refresh Twitter works again and keeps me logged in.
UPDATE3: Twitter just logged me out again (0255 UTC). Since previous update I was able to tweet about issue with URL on "Boost your account security" pop-up.[1,2]
UPDATE4: Twitter still flickering (0310 UTC) logging me in and out, but I was able to reply to ex-CEO on their "Works for me" claim with pop-up issue screen.[3]
I do not recommend logging out as I believe it's broken now.
I was trying to add 2FA to my account when I was asked to log out and could not log in back. Either it was fortuitous or I was the one who inadvertently broke it. :|
edit (12-29T00:49Z): Inspecting dev console logs, it seems to be trying to load resources from `ton.local.twitter.com` which is unresolvable.
It logged me out an hour ago and locked two empty accounts that I was in, then it randomly asked me to add 2fa, logged in again and was logged out shortly after. Console is saying "over capacity". Mobile is moving shaky as well but seems fine there for now.
More bitterly amused at how awful all social media platforms are than angry. I don't have a Twitter account and don't care about it at all. Though I do have a Mastodon account and am struck by how much it recapitulates most of Twitter's socially damaging affordances.
I've not given M** or Twitter, neither of which I have any form of relationship with at all, a moment's thought. I have a Mastodon account, and am pretty sure my assessment of its denizens reactions are about right.
