Twitter was down
twitter.comIn case people are wondering what this is about: All links and images are not working on twitter right now. Seems like they accidentally included their own services in the api blocklist? Sending best of luck to the engineers. The whole twitter saga has given me a good chunk of valuable "lesson learned" over the last weeks and months.. so thanks for that.
For someone who has tried to avoid hearing as much as possible about this drama (and didn't notice this was about Twitter until looking at the comments), what are the condensed "lesson learned" takeaways if you don't mind elaborating?
Don't fire or alienate hordes of engineers with firm-specific talent. Especially for a product/service as mature as Twitter.
I honestly think the engineering/ops problems are the least of their failures. They bled revenue not because of outages, but because wild policy swings and chaotic management style alienated some of their biggest customers.
If they had frozen features and left the existing policies in tact, I suspect we would have a dramatically different narrative about the layoffs. If brief interruptions like this are the worst that happens when you cut engineering to the bone, it's a good argument that is Twitter was indeed wildly overstaffed.
Instead, though, we have a company in crisis due to its mismanagement of other areas, so we're primed to view stuff like this through the lens of that broader failure.
> If brief interruptions like this are the worst that happens when you cut engineering to the bone, it's a good argument that is Twitter was indeed wildly overstaffed.
Overstaffed in order to maintain Twitter as a static service that never ships new things, sure.
I guess they've been able to ship some things that the old Twitter had already implemented and/or a/b tested. But I'm not sure those count. Meanwhile people have been paying in advance for Twitter Blue features that were promised 3 months ago.
I mean the core issue is poor and capricious management either way.
Or else your site for logged out users will go down for an hour?
What was the reason when Twitter went down pre-Elon?
I really don't see the reason for this artificial drama. Do other "X service is down" threads go this way?
People say Elon is dramatic, but this thread is honestly ridiculous and way more dramatic than anything I've seen him post.
The frequency and types of outages and failures is significantly more frequent now than pre-Elon. This isn't a surprise to anyone, given Elon's strategy for maintaining Twitter (or not maintaining it, as the case may be).
I don't interpret a lot of "drama" as you put it, but interest. Many observers here are in this field, and follow the "chaos engineering" discipline. Some of them use tools like "chaos monkey" that simulates a metaphorical monkey running through your server room turning off random things, to see how well your resilience systems cope. It's a rare and greatly interesting sight to such practitioners to get to see what happens when the monkey "disconnecting the more sensitive server racks" is a more literal one.
Well, the fail whale was a meme way before the musk era..
The Fail Whale hasn't been used since 2013.
Yes, almost a decade ago.
is there data on this? doesn't feel like outages are more common to me.
>What was the reason when Twitter went down pre-Elon?
To use a tennis metaphor, good players minimize unforced errors and recover quickly from forced errors.
This is a very clear unforced error that could likely have been prevented by just waiting to roll out the new feature.
To extend the tennis metaphor, it would be like Serena Williams losing a set on 50 double faults. Sure, she's lost other sets before, but it would be notable for her to lose in such a unique way, even if she still went on to win the match.
That's why people are talking about this, it's a very weird way for a site to fail and it's interesting how it happened.
Alternatively -- don't take on debt for an acquisition incommensurate with an acquisition-target's capacity to service that debt.
Musk's cost-cutting may yet pan out from a business perspective, but it seems to be a pretty risky move.
The lesson is if Elon runs Twitter, an hour long downtime takes up everyone's day so we can all speculate.
Before, it was "healthy for everyone" when Twitter went down (search hn.algolia.com for pre-Elon Twitter downtime threads)
Now it's an episode of Real Housewives just like any other Elon thread on HN.
He created that drama when he tried to gaslight the entire tech industry into thinking 90% of engineering jobs were redundant, you can’t expect anything else than for him to get dunked on when the completely predictable consequences of that play out, namely that the service will get more and more unreliable over time.
It does hurt the proud IT worker in me, the knowledge that half of us can be thrown away and almost nobody notices.
Perhaps the takeaway is that we should get our shit together. The opposite of r/antiwork.
No. I think the people creating drama here should take responsibility and act like professionals.
No need to pull out terms like gaslighting to justify creating more drama.
A 1 hour downtime is nothing.
> A 1 hour downtime is nothing.
If it’s nothing, why is Musk on Twitter saying the whole codebase is brittle for no reason, and needs a complete rewrite? Sounds like a pretty big deal to me.
As far as the drama comment, you’re free to disengage from this thread at any time. No need to continually interject how against the drama you are. Just leave if you find it distasteful.
A 1 hour down time every infrequently is nothing, but at the same time a codebase can be brittle. Are you saying the two are mutually exclusive?
Brittle code means it's hard to change, and causes issues when changed, but other than that it's stable when running.
And I have every right to point out the drama here. People here do somewhat have the right to create drama, but it is distasteful and unprofessional and I will continue to call it out.
Glad for you to admit there is drama here though :)
- When you fire a lot of engineers, legal, security experts... things will still somehow keep working - Also some people still want to keep working at this place (or must, because of VISA etc); It probably happens all the time, just this time everyone was watching it in full motion. - I was sure this whole takeover was the end of twitter, but somehow with how many users twitter has, it just won't die. Goes to show the advantages of the mass.. probably the same applies to microsoft/google.. - The whole 8$ for a checkmark story.. which destroyed the whole trust in the checkmark basically immediately. The whole verification process (how that worked) - many people shared some insights on that and how much effort it was to fine-tune all of that with the scale of twitter. - The free API just being shut down with basically zero communication to devs. and somehow getting away with it. I guess this is a reoccuring theme in tech that a small company has to be open for developers until it's big enough to turn on them. - With the reduced engineering and the new management, it seems more errors slip into production (and incidents like the one now) - or maybe it just feels like it with all the focus on twitter right now - but anyways, you just see things breaking you normally would not expect to see.. - How people are communicating, or in this case not communicating.
I'm probably not the ideal person to write this down, there was so much stuff going on, some people probably made a whole blog-article series on this. This is just a few of the things that I'm able to remember right now.. and with everything on hn here it gives you some ideas and things to think about. Hope that Helps.
Maybe mister "genius" is working his magic by annoying as many people as he can and making Twitter visibly worse before it is finally great again! So people will finally be amazed at how "genius" he really is.
Seems likely that they used an allowlist rather than a blocklist for the API restriction, and left several critical services out of the allowlist.
> Sending best of luck to the engineers.
... mostly around the hope they can jump ship before the Titanic pulls them under.
Why would you stay at Twitter? Even if you believe in the platform and the mission, this has to be one of the most stressful work environments in tech right now.
The only cases I can think of for staying:
- Unfortunate H-1Bs tied to the job. (We really need to make it easier for these folks to switch jobs and keep their visa!)
- A feeling one needs the job and can't easily get work elsewhere. Perhaps living paycheck to paycheck, haven't interviewed in awhile, imposter syndrome... (If you're worried you'd not be able to get hired, instead ask why you weren't fired.)
> Why would you stay at Twitter? Even if you believe in the platform and the mission, this has to be one of the most stressful work environments in tech right now.
I worked for a different eccentric billionaire early in my career. It was stressful, demanding, and unpredictable as he tried to micromanage everything by himself in short bursts of 5 minutes before moving on to the next thing.
The hook was an idea that it was a famous company and he was a [not quite] famous billionaire and that we were sitting on a once in a lifetime opportunity to build our resumes. He was going to reward us greatly at some future date when everything was working well again, and we’d be able to work anywhere else we wanted after this.
Didn’t really pan out for us as everyone got burned out, the billionaire’s micromanagement and constant product churn diminished the company’s reputation, and he eventually laid most people off in favor of even cheaper foreign labor.
Probably the exact path Twitter is on.
But there'll be one or two people who get cozy with Elon and win the lottery and will write articles on how hard work always pays off (neglecting the other 99.9% of Twitter that gets fired when it all gets shipped to India).
> Unfortunate H-1Bs tied to the job.
Or we could reduce the hoops & cycle time for legal immigration. The US has an opportunity right now to cement itself as the leader in technology for the next 2-3 decades and stave off the impending population growth crisis if we could find a way to enable people who want to live here to live here.
Or we could force these tech companies flush with cash to pay market rate and watch salaries rise or let these companies leave the country if they can’t afford to do business here. These are the richest companies on the planet and they don’t need a labor subsidy, they just want one and are powerful enough to get their way.
> leave the country if they can’t afford to do business here
Be careful what you wish for.
I was in the industry before this greedy trend accelerated out of control - I know first hand how much better things were before. I’ve seen a colleague choose death over the abuse the average H1B gets subjected to. The sooner this lie ends, the better for all of us.
I'm not interested in government policy that allows companies to bring in cheap foreign labor to undercut my compensation. There are 330 million people in the us, so if companies need more engineers, they can pay more and train more.
Also, there is no population growth crisis. A decreasing population means less stress on the environment and lower housing costs. Yes, there will be economic effects, but it's hardly catastrophic. Japan is managing just fine.
This is a very xenophobic view on immigration, and arguably the status quo. Past performance does not equate to future results, but I think you can draw the conclusion that the immense diversity that exists in the US compared to "rest of world" is a competitive advantage. What would it mean to lean in?
I'm absolutely unqualified to say if they're correct, but there are a lot of economists predicting disaster for countries like Russia, Japan, and (not far behind them) China who will face this kind of demographic shift. The US is in the midst of this kind of shift as Boomers age through the system, but it is said that it will be less severe (thanks to younger immigrants) and less permanent than some other countries are facing.Yes, there will be economic effects, but it's hardly catastrophic. Japan is managing just fine.Of course, you can find a lot of "experts" saying anything. Economics is an area where I haven't got the chops or the hubris to tell shit from shinola.
> government policy that allows companies to bring in cheap foreign labor to undercut my compensation
They become Americans and rise to your level of comfort and compensation. By working here in the US, they increase the wealth, tax base, and culture of our country. Immigration is a good thing. Skilled immigration even more so.
The alternative is that they stay in their home country, and that country grows a tech industry that rivals the US. Those workers will work for even cheaper than in the US, putting an even wider delta on price and creating an incredible arbitrage opportunity for talent.
Much like the automotive industry, foreign competition will drive margin out of our comfortable tech industry that has enjoyed being peerless for decades.
We're only going to see more `TikTok`s and `Spotify`s arise.
At some point, talent won't want to come to the US anymore. That should scare you.
I say all of this as someone who wants everyone to enjoy wealth and prosperity regardless of where they live. I still want opportunity and the ability to capitalize on it to be accessible to any American that would take it. And for that to continue, we should keep growing our talent pool and increasing the scope of what we can achieve together.
I see foreign competition as an inevitability, but I don't think number of engineers is a decisive factor. China and India have enough engineers already, and have for a while, but other than Tiktok, no real competition yet. Whereas Sweden, home of Spotify as you pointed out, has very few.
Even if number of engineers is decisive, we will never stop it by immigration. China + India have more than 8x the population of the US. We would never be able to deprive them of enough engineers via immigration.
^ This is roughly the point I was trying to make.
Maybe folks early in their career. It's not like the cachet has totally dissolved because they did employ a lot of top notch people. Also, when they're interviewing for their next job, even if your departure was super contentious, Twitter is a great scapegoat that nobody will question.
"It says here you were terminated for breaking into a vending machine in the lobby and distributing snacks to your colleagues while dressed as Robinhood."
"Yeah it was an act of protest because management threatened to take away our lunch breaks."
"Well... it... sounds plausible I guess."
(Not at Twitter) Interviewing sucks and many people have other priorities in life, like family, etc.
Could also be that they have enough money saved up and don't actively need a job, so they're happy to ride this one out until the end and because they don't need the job they don't really get stressed or anything - if they get fired no big deal.
If they actually make it all the way to the end, maybe being the last man standing there actually does have some perks we don't yet know about?
Perhaps some people have different preferences than you.
> The only cases I can think of for staying:
You forgot the bootlickers, I'm sure not all of them have been fired yet.
> - Unfortunate H-1Bs tied to the job. (We really need to make it easier for these folks to switch jobs and keep their visa!)
They can switch jobs. H-1B doesn't force you to stay at your job.
Another reason: some people enjoy the work environment that is promised at the "New Twitter."
Clearly not for everyone given the amount of opting out and controversy.
Everything seems fine for me when I use the main website.
Are you logged in? Twitter seems to be working normally (i.e. it refreshes) where I'm logged into the browser. But where I'm not, I get the error message everybody's seeing.
Same for me, but accessing Twitter links from Google breaks it.
Seems to be related to a query param in my case (if I remove the ?lang=en, the page loads properly).
Perhaps it's region specific but I get 467 errors right now for images on both mobile android and desktop web.
Definitely region specific I think. It's working mostly fine for me. Links and images are mostly fine except for the errant occasional broken one but even then it's only when opening the full image
Doesn't work from Germany right now. (Telekom if that turned out to be important.)
I see the issue on iOS
No new links or images work for me from the main website. Cached stuff seems okay.
Worth noting Twitter’s status page claims it is “operational” and no events are listed under history section for past 180-days, which is obviously wrong:
* Not to mention the SSL certificate appears to be expired too.
———-
EDIT-01: Appears there’s a status page just for the API:
EDIT-02: Wow, Twitter is using Twitter to post status updates:
- https://twitter.com/TwitterSupport/status/163279294226274713...
> * Not to mention the SSL certificate appears to be expired too.
Love that detail. Just the icing on the top that says "everybody who was vaguely aware of this particular infrastructure is gone."
Oh man, no way. If that is the case, some people thought I was full of shit when I said, "watch it, in the mass layoffs they fired that one guy who knows all about the certs." There is always that one guy and unfortunately he always gets canned.
Also weird given that Twitter is using 3rd-party service which apparently doesn’t even automatically log and post known downtime issues; service being:
(Assuming this is more of a the site’s not down unless the CTO says it is services.)
It's not expired. That site is using the wrong cert (ERR_CERT_COMMON_NAME_INVALID).
How odd.
Browsers still look at the commonName?.. Hasn't this field been deprecated since 2000?
CN/SAN. It amounts to the same thing.
They are serving the cert for "*.twimg.com" here.
They're not expired. It looks like they're serving up the wrong one for that domain.
Twitter Support just posted:
"Some parts of Twitter may not be working as expected right now. We made an internal change that had some unintended consequences. We’re working on this now and will share an update when it’s fixed."
https://twitter.com/TwitterSupport/status/163279294226274713...
Thanks for typing out their tweet. I wouldn't have been able to have read it otherwise, seeing twitter is down.
I haven't really been able to read anything on twitter for a while now as I run noscript by default and haven't deigned to whitelist twitter.
I remain astounded by how much their product has declined (even pre-Musk acquisition) from their glory days of being so light weight that they were used to organize protests when governments would clamp down on internet access.
I try to avoid the site as much as possible but I have a redirection rule to go to a Nitter instance in case I end up clicking on a link. The Nitter UI is nicer too and works fine without JS.
Mileage varies. For me, Twitter’s user experience hasn’t changed noticeably.
Is it working for you today?
Yes. I don’t use Tweetdeck, though. I just use the website.
Also, here’s a nice way to just get the tweets from people you follow: use the realtwitter.com redirect, then click “Latest.”
Yes, just checked.
Looks like their redirect service for links was down, not twitter itself. I could go to my profile, but clicking links in my tweets gave me an API error. Ugh, not good.
Ha, that page isn't loading for me, but Nitter is: https://nitter.net/TwitterSupport/status/1632792942262747136
Maybe fetching through the API is working better?
Nitter doesn't use the official API, which seems to be what's broken, instead it talks directly to the undocumented APIs that Twitters normal web interface is built on.
I assume they do it that way to get around all the rate limiting and threat of having access revoked that the official API comes with.
We made an internal change that had some unintended consequences.
This person missed their calling at the State Department.
He came, he optimized, it died.
Thanks - we changed the URL to that from the submitted URL https://tweetdeck.twitter.com/. (Submitted title was "Tweetdeck is now broken for normal users")
It's encouraging they still have a support team, honestly.
Are they going to put "fired the people who used to enforce our change control procedures" in the post-mortem?
Followed swiftly by: "We apologize again for the fault in the service. Those responsible for sacking the people who have just been sacked, have been sacked."
When does the møøse arc begin in Twitter's storyline?
As soon as the møøse bites Eløn's sister.
Probably goes with the Llamas by Ford of Brazil
I'm gonna go ahead and say the "post mortem" will involve finger pointing and Elon firing more engineers.
Presumably those people weren't "hardcore" enough for Elon Twitter.
Hey if those people wanted to keep their jobs they should've bought sleeping bags[1]... oh, wait.
1. https://www.entrepreneur.com/business-news/twitter-lays-off-...
Unless they already left the company...
> The change in question was part of a project to shut down free access to the Twitter API, Platformer can now confirm. …
> But in a sign of just how deep Elon Musk’s cuts to the company have been, only one site reliability engineer has been staffed on the project, we’re told. On Monday, the engineer made a “bad configuration change” that “basically broke the Twitter API,” according to a current employee.
https://www.platformer.news/p/how-a-single-engineer-brought-...
This is actually funny. Just this weekend I was talking to another engineer friend of mine, and we were taking bets as to how long it would be before twitter went down for the last time.
We felt bad for the engineers that are still there, and were actually surprised it's stayed up this long, with all the knowledge that walked out the door. Basic stuff like "where are our servers actually located".
I guess the folks that left loved Twitter enough to leave behind good notes, because even the most well architected systems still need some institutional knowledge when they go down.
I would say it’s just H1B, hard to jump ship when you are on such a tight window
Just had the wild idea that Elon fires anyone who's away from their workstation long enough to be potentially interviewing elsewhere. Just crazy enough an idea to be something he'd pull.
you have chosen an interesting choice of topic for fanfiction
Harder in the current economy, when everyone else is doing layoffs.
Where did you land on the bets?
It appears that when Twitter goes down, its engineers were indispensable but when it's up, it's because the engineers foresaw this.
Given those factors, how long it stays up must be an interesting combination of how indispensable the engineers made themselves vs how much foresight they had.
I know some of the former Twitter engineers, and they were great engineers. I'm sure they built a fairly resilient system.
But at the scale and complexity, eventually you hit an unforeseen error that requires some institutional knowledge to fix, and it's doubtful they still have that, unless the ex-engineers loved the product so much they are willing to take phone calls from the people that are left and point them in the right direction.
I don't think we landed on a time frame. I'm actually surprised it stayed up this long.
Do you actually think it will go down for good?
That seems extremely unlikely to me.
No, eventually they would figure out how to rewrite it if they can't get it working again. But I could definitely see a multi-week outage.
Seems to be back up now. Both logged in and logged out states are working.
This thread is just an hour old btw, not sure when the issue started.
Seems like a huge reaction from HN for an hour long downtime given that Twitter has gone down for longer in the past.
They do this every time. Last thread I saw was Twitter had an outage for only 10k people for a short amount of time and HN was having a victory lap.
I personally don't think that 100% uptime for everyone around the globe is even a worthwhile goal for Twitter. The incremental costs for that last 0.5% aren't worth the incremental benefits.
HA is most necessary for what, journalists? (Who are already antagonized under Musk)
Everyone else can wait the hour.
It's down for me and hasn't worked for the entire weekend.
>I don't think we landed on a time frame. I'm actually surprised it stayed up this long.
How much to get in on this? Seems like free money if you thought the time frame was that early.
The problem with bets with strangers is counterparty risk. The counterparty cannot prove that they will fulfill in the loss scenario, which makes it a guaranteed loss. Bets with friends don't have that problem, since the bet is usually either cash-free or for such a small value that retaining the friendship is more important.
We always build systems hoping they never need any maintenance.
The truth is, they often do. Especially when there are changes happening. I once took a week off and we went down on day 2. Other times, I'm convinced I could've gone 6 months without anything breaking.
At Twitter's scale, I'm sure there are systems where everything is automated and self-healing. But there are probably other systems that are more fragile. And then there's the eternal race against scale; eventually a system with no maintenance will get buried under the weight of its own data or the scope of its usage. That always requires some work.
Exactly right, which is why this whole saga is so irritating to watch. The commentary is heavily biased and its exhausting to filter back to neutral. I just want to know the impact of many engineers leaving
You're not going to know that impact, because most of the technical problems that Twitter as a company can have aren't even visible to us.
Sure, images and hyperlinks breaking and not paying the Slack bill and Musk having another mental break makes the front page of hacker news, but will a spam and abuse detection pipeline being silently busted for 3 months do that? A reporting backend that was providing advertisers with incorrect data on their ad spend? Some customer-relations workflow that ruined the week of a group of TAMs, and had revenue impact?
Twitter is a big ship. There are more places things can break than anyone, inside or outside it can imagine. But as an outside observer, the only signal that we can act on is 'Has the ship sunk? Or is it floating?'
Observing that binary state answers a question, but not the question of 'Is the ship working well?'
And that's what might eventually kill it.
It seems really unlikely to die from a single spectacular failure, where a key bit of infrastructure dies and just cannot be brought back online for any amount of love or money.
A steady drip of annoying but individually minor issues will gradually chase people away: more spam and less relevant recommendations discourage users; bad spend data and fewer account reps make it a lower priority for advertisers. Twitter's main value prop is its network effect, and if a few people leave (or even engage less) every issue, that value will wither away....
You can never know the true impact because people will spin the narrative to say what they want. This hour-long outage occurred because Twitter laid off their engineers. Meanwhile, AWS had a major outage that lasted over half a day and took down Slack among other major internet infrastructure in December 2021[0], but we can't blame that on layoffs so we just ignore it, I guess.
There's really no correlation between layoffs and outages, I suspect.
There's definitely a correlation. But not having layoffs just doesn't mean no outages.
> There's definitely a correlation.
Where is the evidence of this?
What evidence do you expect? It's not like Twitter is going to show us a post morterm from their outage. Anyone who knows and uses twitter quite a bit can see that things have been wonky on the sites. Big users have mentioned tons of issues (their mentions being empty, twitter threads going broken, some tweets never reaching their audience not even a bit), etc, etc. It's all anecdotal of course, we can't build a case of evidence, this is a private company and all the shit internally is private. But things are getting worse, not better. Even those big initiatives announced are not actually happening, that paid and free API plan that was supposed to be released in 7 days? It's been a month and nothing. Things are not "normal" and clearly the lack of engineering talent is slowing a lot of things down (both new development and infrastructure resilience).
Assuming that you are correct that things are breaking more at Twitter (which I'm not sure is accurate to begin with), how do you know that is due to "lack of engineering talent" and not due to higher pressure to deliver features?
As anyone who has operated a software system knows, the #1 reason things break in production is new code, and from a third-party observer with no inside knowledge it certainly seems like more changes are happening at Twitter than ever. This is orthogonal to layoffs, though.
https://trends.google.com/trends/explore?date=today%205-y&ge...
Best source I could find. Currentlydown didn't even register yesterday's outage, and downdetector doesn't share historical data.
Their website is broken for normal users. Try visiting anyone's profile page over the web — you'll get a 467 error
[0] e.g. Elon: https://twitter.com/elonmusk
Wow. Glad I'm not putting energy into Twitter any longer.
As someone who's never sent a tweet, what did you get out of it Pre-SpaceJesus?
I quit Twitter when Elon took it over. It provided me with:
Easy access to information and articles about breaking news events.
Community.
A feed of interesting articles and discussions.
Enjoyment gained from following quickly evolving memes, discussions, and jokes.
A way to verbalize incidental thoughts, and the pleasure of crafting those thoughts into small nuggets to share with my friends.
Of course there are many negative aspects to Twitter, but those are the things I found value in.
All still present (positive and negative) on Twitter, plus the benefit to open-minded people of hearing opinions from all sides, which has improved post-Elon.
I used to run a bot that broadcasted my town's current alternate side parking rules (for snow removal operations) but after twitter got weird the town decided to make a text messaging service for it.
I still use it to follow certain artists but if that subcommunity moves I'll follow them elsewhere.
Local status updates and the occasional tidbit of interest from people whose thoughts I like to read but who twitterblog instead of using an actual blog.
Not much to be honest so it's not really a loss
Works fine on my end (considering the contents of his tweets, I almost wish it didn't, though...)
To save everyone the click his feed is equal parts misogyny [1], 3 AM shit posting [2], and tantalizing flashes of self awareness [3].
[1] https://twitter.com/elonmusk/status/1632574090216103937
That second one, poking fun at the BBC for saying that Twitter "can't protect users from trolling," was really the BBC shooting itself in the foot with a laughable headline burying the lede of the article:
> Twitter insiders: We can't protect users from trolling under Musk
> Twitter insiders have told the BBC that the company is no longer able to protect users from trolling, state-co-ordinated disinformation and child sexual exploitation, following lay-offs and changes under owner Elon Musk. [1]
For some reason, the headline decided to focus on "trolling" over an increase in child sexual assault and state-co-ordinated disinformation...
Honestly the "insider" even talking about "protecting" people from trolling and state co-ordinated misinformation(?) in the same sentence as protecting them from csam makes it very hard to believe it's something genuine.
Sounds like the people who say all the petty things they dislike about someone on the internet and then finishes with "he's a pedo" to add gravitas.(yes elon does fall into this category)
'Trolling' has basically come to mean 'misinformation' among the general public, in the same way that 'hacking' has come to mean 'cybercrime'.
Is there any information on the 467 error? Doesn't appear to be standard. Any ideas or other companies using 467?
everything is super broken. I can't load help pages. Links to 3rd party sites (that use t.co links) don't work. All kinds of fubar going on.
Twitter seems to have fixed that issue. Your link loads fine for me.
Works fine.
What is http code 467? Something Twitter made up?
What, they didn't go with something like 420, or even 69?
I guess there's still one aspect of the company that Musk hasn't "fixed" yet...
He'll probably bring this back, claim to have invented it, and ban/threaten to sue anyone who says otherwise: https://evertpot.com/http/420-enhance-your-calm
Works here
They fixed it :-)
“I would expect to start seeing significant public-facing problems with the technology within six months,” he says. “And I feel like that’s a generous estimate.”
https://www.technologyreview.com/2022/11/08/1062886/heres-ho...
A certain percentage of engineers have to keep the lights on. It's usually around 10%-40%, depending on staffing levels and engineering quality.
But there's one more gotcha, a company can't just keep 10% - 40% and expect the service to still run, because it's rotating and oncalls can always reach out to other people on the team.
Twitter not only fired indiscriminately, with perverse pattern (more capable to find another job leave first), and didn't even keep the minimum to keep the lights on.
From a software engineering perspective, it's doomed to fail, maybe it can retract to a smaller footprint (abandoning features/stacks) and still work, but that would also be pretty hard. That, and I don't think anyone not desperate will apply for a job there in the foreseeable future.
Speculation is that t.co link shortener service is broke :
https://twitter.com/emollick/status/1632788892599586816
> The Twitter outage seems to be around a critical piece of infrastructure: the Twitter link shortener.
> Every link on Twitter has been shortened to a t.co link. Only Twitter’s systems know where the link goes
> If these systems ever go down, its link rot at scale
> If these systems ever go down, its link rot at scale
Only if one's mental model is that t.co links were ever permanent.
They're privately-owned obfuscator links. Unless someone in the wild was building a mirror mapping, they were always doomed and never to be trusted; they knocked the "U" right out of the "URL."
It doesn’t matter what my mental model is if I’m trying to follow links posted by someone else.
That's what I'm saying. We must reframe our mental models so that everything on Twitter is thought of as temporary. None of it is, or really was ever, stable.
Isn’t that true of any url though? The U is for uniformly useable, it never guarantees uniform resolution.
It's even more-so true for t.co URLs though because instead of just 1 point of failure there are 2 points of failure. The original URL may work for another decade but if you don't know what the URL is behind the t.co URL and Twitter is down or whatever, then you're just out of luck.
I don’t think it necessarily changes the reliability of the URL. A server or dns change is similarly problematic.
The only issues I have with shorteners is that they obfuscate what you’re accessing (so if it changes, it’s harder to know) and they’re a privacy issue
{"errors":[{"message":"Your current API plan does not include access to this endpoint, please see https://developer.twitter.com/en/docs/twitter-api for more information","code":467}]}
Interestingly, that URL has the same message! A type of quine?
Most recent snapshot of the URL in the message gave you a recursive error: https://web.archive.org/web/20230306165738/https://developer...
wait, so did they lock themselves out of their api?
Elon's latest money making strategy: internal teams have to pay $70/mo for access to APIs managed by other teams.
They didn't pay $8.
it was working a couple of hours ago :( RIP
I can't remember a major service nosediving so monumentally in such a short period of time.
Just a steady degradation of service.
Things fail slower then faster than people expect.
Lots of people were waiting with baited breath for Twitter to fail the first week Musk bought it, but most of the failure conditions had been automated away...
Instead the reliability loss creep happened more slowly. The people that understood the edge conditions in the system were fired. Then new changes need implemented and the old, now not understood systems, were ripped out and new pieces put in. And lo and behold they have tons of failure conditions and edge cases that can knock out the system.
Even if your programming team wrote immaculate documentation on all these edge conditions, it can take an immense amount of time to both read them, and then fully understand them, and when you have a micromanager breathing down your neck for changes 10 minutes ago this is what happens.
At this rate it’ll be Reddit-tier by EOY
> At this rate it’ll be Reddit-tier by EOY
I don't spend enough time on Reddit for that to really resonate, but the badges and icons flying all over the place and talk of Twitter Gold (or whatever they're calling it) do feel very Reddit-esque these days.
Reddit is fine? Not sure what this means…
Reddit crashes almost weekly it seems. Search is completely broken. The site's UI (new, not old.reddit) is truly atrocious.
I’m in what is likely the top 1% of Reddit users by volume (I have a problem, send help), and I have absolutely no clue what you’re talking about.
Further, as a dev of 15 years, I’m not even sure what you mean by “crash” here. Are you saying that Reddit serves exclusively 500s or timeouts for a sustained period of time on a weekly basis? Or that it serves more than zero 500s at some point during a given week? Or that you, personally, encounter an issue of any kind over a week?
So many ways to describe “crashes” that yeah, by some definitions it probably does, but “can’t use the service” such as what Twitter is experiencing, I don’t think that’s accurate.
There is no way you haven't noticed reddit's servers getting overloaded. It happens fairly frequently and has for the last decade.
https://www.reddit.com/r/OutOfTheLoop/comments/2trmnk/why_is...
(See: all the people agreeing)
One of the triggers used to be that if a thread got too many comments it would bring down the website. So sports communities had to start splitting up their game threads during massive events so Reddit wouldn't break.
It definitely used to happen more often, but it was doing it for me yesterday coincidentally.
There is no need for such complex definitions. Reddit is a site that you will probably get an error on if you visit it several times a day.
That's my point; as someone who visits it many times a day, I do not get an error on the vast majority of those days.
Thats quite strange, and definitely not my expirience. Maybe you have some issues with ISP?
Search is and always has been broken on Reddit. I think it’s intentional, because nothing can be so bad for so long in accident.
Reddit's search was never unbroken, though. So business as usual.
And when it's not crashed it's slow as cold shit.
> And when it's not crashed it's slow as cold shit.
And stale. When they changed algos in ~2016(?) to try and stop certain subs I swear it got stale and feels like it updates on a cron job once a day anymore.
I hope they never remove "old" reddit.
I mean, reddit certainly has more downtime that twitter, historically over the last say 5 years.
At least once a week i'm met with the 'trippin' out snoo for a few minutes.
It's kind of funny that another thread (https://news.ycombinator.com/item?id=35043330) is in top 5 Google results for "Your current API plan does not include access to this endpoint" search term, and is flooded with newly created accounts asking for support.
Even the homepage seems to be down as of 11:15am CST. Same error message.
I think only if you are not logged in. I get the error in incognito mode.
Error randomly shows up if you’re not logged in; meaning not logged in I have seen error and error free homepage too.
I was logged in and got it too.
Alas, their login page gives the same error: https://twitter.com/login
That’s…gonna make it hard to get logged in to not see the message…
I get it both as logged in user and in incognito mode since at least 17:04 UTC. Probably different front-end servers.
I am/was logged in, still get the error.
iOS app seems to be working.
I don't think I could have predicted - even given the wanton layoffs - that the service would deteriorate so quickly across the board.
I barely use the app anymore and half the time stuff isn't loading at all or is broken in obvious, overt ways.
Just ... stunning.
> half the time stuff isn't loading at all or is broken in obvious, overt ways
I use the app for a couple hours a day (according to my iPhone weekly reports), and have barely noticed any degradation since "the takeover". (Notwithstanding the obvious outage happening currently).
There's been a few minor glitches for sure, but then what large service is immune? Facebook, Exchange, AWS, etc. have all had notable outages this past year, and the Apple Services I regularly use (Apple Music, Siri, etc.) "fail" more often for me in daily use.
Maybe you're trying to do something more advanced than me, or are using a less reliable platform somehow, but generally I find all the "Twitter is so dead" talk being confirmation bias from folks that really want it to fail in light of recent changes.
I've never seen a large company whose entire existence is a single app perform so poorly. It was down for me a whole day a week or so ago. Bugs are pretty rampant, they're small, but didn't happen to me previously. It's just been gradual degradation for months now. Idk how you aren't noticing.
> Maybe you're trying to do something more advanced than me, or are using a less reliable platform somehow, but generally I find all the "Twitter is so dead" talk being confirmation bias from folks that really want it to fail in light of recent changes.
In my ideal world, Twitter - or something similar - succeeds. I don't care much about the politics of the ownership because that's generally going to be an iffy subject with anything coming from the valley.
But to regularly use it and not see things breaking here and there every day (not even including the times when the API is borked or it's only recommending Elon Tweets in your feed or a person's timeline won't load no matter what, not being able to send a tweet, etc.) ... I have to imagine you're very lucky. There was about 11 hours when people had exceeded their daily tweet quota by trying to send a single tweet. You don't remember stuff like that? It happens multiple times a week in the last few months.
I'm certainly not doing anything advanced. I'm mostly a casual user.
I can corroborate. Videos struggle to load, timeline doesn't refresh unless you pull down multiple times, my current position gets lost multiple times forcing me to scroll down and then scroll back up, tweets showing up multiple times, many more ads than before and so on
It's really been kind of miserable to use the app and I only open it once or twice a day. It had issues before but never all at once like this
Elon's own account is that he's "experimenting" with taking production services offline to cut cost and simplify their code base. Essentially a literal Chaos Monkey. With this in mind, service degradations aren't surprising.
It not just the layoffs it is also the major changes Elon is forcing through at high speed .
Hiring for twitter is going to be quite expensive, nobody is taking this up without huge payoff and probably upfront given Elon pre disposition not to honor severance etc
He seems to be of the belief that Twitter's issues are bottom line not top line. Hiring would require a major shift in belief.
There is so only firing you can do and attrition you can handle before you have to start replacing staff .
Either he shuts it down at the point or he has to spend a lot of money .
IMO More likely he shuts down and blame any range of external factors were conspiring to take him down rather than accept he decisions were wrong
As someone that I think the previous twit sphere would accuse of being right wing adjacent, I’m shocked at the dumpster fire that twitter has become from a content standpoint.
Like.. wokeness was annoying but the trash heap of craziness it is today is 5 steps backward. My feed is nothing but conspiratorial nonsense.
If twitter was “tilted left” before, today it seems to have capsized rightward.
Right, it turns out that bringing back a bunch of previously banned trolls will chase more centrist people away, leaving only the trolls and those who like to argue with them. Not sure if there have been algorithm tweaks as well (aside from the obnoxious removal of the sort by latest button Elon swore he'd keep), my feed is the same. Combined with the stupid "Trending" tweaks and it's a worse version of Reddit.
I honestly can't believe that not only did he welcome back actual Nazis that were previously banned, but he sold them checkmarks that let them have outsized influence.
The Twitter suicide is the most crazy thing I’ve seen in my career. Rich and bored billionaire bought a “socially valuable service” just to drop its revenue by half and destroy it completely
The fun part is that the CEO is on Twitter as this happens, arguing about COVID.
When I checked this morning, he was busy posting borderline sexist dad jokes: (https://twitter.com/elonmusk/status/1632574090216103937)
I still don't understand why every fifth post in my feed is an Elon tweet, I don't even follow him. I could block him but I find it interesting to see how much of his content is pushed toward me who hasn't asked for it.
He intentionally demanded the site be jury-rigged to force-feed everyone his posts regardless
It's unintentionally becoming a symbol of its downturn.
Maybe better to block him. I did so because I was a bit sick of seeing his tweets - some of them are borderline offensive, some are him cosying up with far-right but the majority are just a bit try-hard, unfunny and ultimately sad.
I'm not a delicate flower when it comes to offense so I'd just roll my eyes when the first two kinds of tweets popped up. But seeing a grown man repeatedly trying and failing so hard at being a poster is a bit much to take.
Shameless plug: I created a browser extension to help transition to Mastodon[0]. If you don't yet feel like you can leave twitter.com, but want to explore alternatives it's a great way to get started. Essentially it injects Mastodon posts into your Twitter timeline, so you can retain your existing Twitter following while getting exposed to Mastodon.
For context, most of Twitter appears to be having issues (t.co links and images are also broken)
Given all the random things Elon has cut from Twitter, it wouldn't surprise me if that included a staging environment.
One of the criticisms against the old twitter engineering team was that they failed to set up proper dev and testing environments. A leaker exposed all of this and it was later confirmed by Musk in a Twitter Spaces call.
Not just Tweetdeck, all images and videos on the website too, and even the homepage doesn't load.
If you like graphs, I've been watching this outage from OnlineOrNot (https://twitter.onlineornot.com/)
On the positive side website response time has seen a dramatic improvement…
Looks like it's back up, was down for 56 minutes.
please see https://developer.twitter.com/en/docs/twitter-api for more information
So cool! I've never seen a self-referential error!
On an unrelated point, Californian employees in the main layoff were employed till January 4 for legal reasons. Many of them were demanding their contracted 2 months' severance to follow that. Now that 2 months have just passed, does anyone know if they received this pay?
No... he got the class action thrown out because of an arbitration clause... so each individual case must go through arbitration, and those are all still pending (when I checked a week or two ago).
That could cost him a lot more in the long run... arbitration ain't cheap and these employees are probably quite motivated to pursue it.
https://status.twitterstat.us/ says everything is operational
they laid off the people whose job it was to update that site, it hasn't updated for any of the other recent outages either
There were many different hypotheses on the outcome of Elon firing 80%+ of Twitter employees:
1. The site would crash and burn the next day.
2. Nothing would change. All those engineers were anyways just sitting around.
3. There would be no immediate impact (servers can run by themselves after all), but the site would slowly degrade over time as institutional knowledge around maintenance, upkeep and all the various system quirks was gone.
We are now seeing #3 play out in front of us.
#1 is what non-tech people said.
#2 is what hardcore Elon fans said.
#3 was always the most likely prediction and is what any actual tech engineer should have said.
certainly not all of them https://news.ycombinator.com/item?id=33498116
I'd assume that person is group 2.
The problem is that a lot of the "actual tech engineers" are in groups 1 & 2.
Should have.
#4 Massive cuts don't just mean people but include nonessential features of your product.
Let’s not pretend like Twitter has never had downtime, they literally popularized the “Fail Whale” meme way before Elon was around:
- https://www.theatlantic.com/technology/archive/2015/01/the-s...
Since the 2010 nadir of fail whales, Twitter invested a lot into improving their engineering quality.
There's a great 2015 essay by Peter Seibel who was tech lead on their Engineering Effectiveness team:
https://gigamonkeys.com/flowers
I'd guess almost nobody from that era remains at Musk-Twitter.
As reminder, from 2011 to 2014, Twitter also 10x their headcount:
https://www.statista.com/statistics/272140/employees-of-twit...
Yes, but my recollection is that the whale fail was usually due to huge growth or unprecedented traffic peaks. I don't think Twitter is growing at a fast rate any longer.
> my recollection is that the whale fail was usually due to huge growth or unprecedented traffic peaks
My recollection is that around ~2011 a day without a fail whale was the odd one out.
12 years ago
It also comes from it's history as a Ruby on rails site and disappeared once the the servers moved to scala on the JVM.
Rails was never meant to be run on such a massive load. It was the perfect framework to get twitter take over the market but once that goal was reached a rewrite was unavoidable with a tech stack that can sustain such a load.
Maybe now there are issues because of decreasing traffic?
Musk claims often that Twitter engagement numbers are at record highs. I don't believe these are lies.
"Record high" in an established business like Twitter isn't quite the same thing as a traffic spike in the growth phase of a startup (i.e. Twitter in 2011).
Record engagement these days is most likely measured in single digit percentage points over average engagement (at most maybe 10-20%), where when you're early and your traffic is spiking, it can be an order of magnitude more traffic than what you're used to seeing. The absolute numbers are larger yes, but from the perspective of "what can my infrastructure / architecture handle", relative changes are far more relevant.
> Musk claims often that Twitter engagement numbers are at record highs. I don't believe these are lies.
You're talking about a man who has more than once been fined by the SEC for making false statements about public securities. What makes you think that he'd be a more reliable narrator for a private company for which he has no external accountability and a large personal financial interest?
At the very least per tweet it’s possible to see really view patterns, which to my knowledge what’s possible before.
> At the very least per tweet it’s possible to see really view patterns, which to my knowledge what’s possible before.
Those numbers have been proven to be incorrect, by people who are posting from locked accounts with 0 followers racking up large nonzero view counts within a few minutes.
Some part of my brain immediately replied to this with the theory "what if those view counts are real and Twitter's just kind of ignoring whether an account is locked now" and damn that is a hell of a possibility to ponder.
There's another plausible theory that the just implemented it by counting database reads. So of course a locked test account will have more reads every time you look.
> There's another plausible theory that the just implemented it by counting database reads. So of course a locked test account will have more reads every time you look.
It'll have one, maybe two more reads every time you look. Not dozens. One person posted an example that had literally over a hundred alleged "views" within a minute, despite not refreshing their timeline after posting the tweet.
Source?
Many users have reported weird view counts on locked accounts with few or zero followers: https://twitter.com/search?q=Locked%20followers%20views&src=...
The fail whale was very common during a time of sustained growth when Twitter did not have the infrastructure it has today, but it all but disappeared in recent time.
The fact that things start to fail after that infrastructure has been put on place and running find for a while is noteworthy.
The fail whale was also a very specific case - I have no idea what was going on in the backend, but from a user perspective it was all "twitter's not available". Now we have inconsistent behaviour and countless small bugs that detract from the overall experience.
I feel like I'm living in an alternate reality. People seem to be acting as if Twitter was good prior to 2022 until Musk ruined it, but my experience has always been that Twitter is awful, both from an engineering and content viewpoint.
Maybe it's because I use an Android, but I've always found the experience terrible. I get notifications, but when I click them and they don't take me anywhere; the back button is completely broken; mentions randomly don't produce any alerts; it resets me to the algorithmic timeline every few days; replies often fail to load; the spam problem is completely out of control and most adverts are irrelevant crypto-spam; search never finds what I wanted; it's constantly putting tweets on my timeline from people I don't follow; and the whole app seems optimised to produce as much hatred and outrage as possible. Nowhere on the planet is as toxic as a Twitter thread, and yet the media and political sphere collectively decided that reporting on and catering to Twitter spats is the most important aspect of their career.
Frankly, if Musk destroys Twitter, it might be the best thing he could do for society. I may be misremembering, but I thought that prior to Musk buying Twitter, everyone was decrying it as toxic and lots of people were suggesting the government should step in to reduce its influence. Now it seems to be imploding by itself, yet everyone's upset.
It's telling that it all but requires a visit to the Wayback Machine to find reporting on that era.
That was many years ago when Twitter had fewer employees.
twitter had 5 'major' outages in 2022. Twitter had 5 'major' outages in March 2023. (citations needed)
4. Something in between? In short term we'll see some issues but overall nothing important will change and these downtimes and small issues are a justifiable cost for letting such massive cut in the payroll.
lol, I guess every tech company that has major KPIs for availability is wrong and people are totally fine with apps being down constantly, and new users will totally come back after trying to signup and failing. It's a tech company, a few thousand employees supporting perhaps hundreds of millions of users is pretty standard economies of scale.
What keeps Twitter up as a major social network is not %99.99 uptime. It's strong network effects in play.
What will sink Twitter is not %99.8 uptime. It's those network effects fading away.
For example, if people stopped using MySpace, Facebook, etc it was not because of their availability.
Again, I'm not saying this is cool. Im just saying if that extra %0.2 downtime (in short term) costs you 80% of your work force costs, a business manager may consider that acceptable.
>these downtimes and small issues are a justifiable cost for letting such massive cut in the payroll.
Well we're not even a year in and these "small issues" seem to be repeatedly occurring. Let's get a little further out with some more stability before we call them justifiable lol
I think 3 is happening but the thing is that can this HC-twitter build knowledge and code back so that site functions stay about same before users leave is the real battle.
Also #4 they are shipping features much more than before. Shipping more always will likely lead to more errors happening. IMO it's a combo of #3 and #4
3 was the most likely, third party changes slowly breaking stuff
Option 4., Twitter was always bad and had strange bugs and outages, but now it's political and people care.
All services have downtime. Look at AWS last year.
4. The institutional knowledge is not gone, in the event of any massive catastrophe employees who previously worked at Twitter can return as “consultants” and charge very high rates to fix issues as they occur. It’s pay as you go.
> 4. The institutional knowledge is not gone, in the event of any massive catastrophe employees who previously worked at Twitter can return as “consultants” and charge very high rates to fix issues as they occur. It’s pay as you go.
What you're describing is the loss of institutional knowledge with a fantasy tacked on the side.
1) There's no reason to expect those employees would come back, even at rates far higher than Musk is likely willing to pay. Everything indicates Musk has destroyed a lot of goodwill with his shambolic layoffs, and getting people to come back is one of the situations where you need goodwill.
You're basically talking about gig-work on a shitty boss's terms. Only desperate people would play that game, and the people Musk would need probably aren't the desperate ones.
2) Any employees that come back are going to be rusty and lack the institutional of what happened after they left, so their effectiveness at immediate fire-fighting will be greatly reduced.
3) If there's a "massive catastrophe" at Twitter, do you think they even know who to call back? I wouldn't be surprised if they've lost a lot of the institutional knowledge about who knew what, at this point.
> return as “consultants” and charge very high rates to fix issues as they occur.
I'm sure there are some people who would do that, but those opportunities become very expensive-to-impossible when you burn bridges the way certain new management has. People hold personal value on things like respect and principle that can make them behave "irrationally" in naive analyses like this.
Massive catastrophes are averted by people with institutional knowledge correctly adding to the hardware/codebase over time, with new features that integrate well with old one, knowing how to scale hardware correctly, patches being applied, etc.
Not by bringing people in during a fire and pointing into the smoke and saying "fix that!"
Most of those people will presumably have other jobs now, which would tend to preclude this. You do _not_ want to be in the position of begging employees you fired to come back as consultants; it's not at all as easy as you seem to think.
>return as “consultants” and charge very high rates to fix issues as they occur.
Elon Musk has a rock-solid reputation of paying his bills, after all.
Interesting to me that when Twitter was ascendant the same predictions of doom were not made so frequently when the fail whale was a regular occurrence.
It's possible Twitter didn't need to be spending all the money they were to be maintaining five nines or whatever, given the shift in product focus (humans and not a general/universal message bus - bots can't @-mention anymore, etc).
Given that they are unprofitable, if I were a shareholder I would be upset if I did not see experiments being run to see how much cost can be cut and where. I doubt people will abandon the platform en masse over a few minutes of downtime here and there. They will lose 100% of users and be down forever if they don't stop the bleeding, however.
> Given that they are unprofitable, if I were a shareholder I would be upset if I did not see experiments being run to see how much cost can be cut and where.
Twitter will never get to $44bn market cap again (much less a valuation with a decent IRR) by cutting costs alone. They need to grow way more than they need to cut costs.
If any of those experiments lead to less growth (which I’d argue is true of a broken Tweetdeck), then they are wholly not worth it.
If I were a former Twitter shareholder, I'd be extremely grateful to the board for selling the whole thing for 44 Bn. No way tje company would have reached this evaluation without Musk. And Musk knew it, he just signed himself a contract he couldn't het out of.
As a nit, Twitter traded well above $44bn for good portions of 2021.
It was arguably even a fair price when he offered it (acquisition always have premiums), the market just turned.
So, shareholders got paid the pre-downturn price after the downturn? At a time big tech went down double 10+%? Sounds like an incredibly good deal to me.
Yeah it was.
But now $44bn is the cost basis for all the current shareholders, so Elon has to make returns against that.
If pre-acquisition shareholders choose to stick around after that windfall, well, that there problem. And Elon's.
> Interesting to me that when Twitter was ascendant the same predictions of doom were not made so frequently
... wait, they absolutely were, though? I remember at the time people saying that Twitter was doomed for this very reason, by analogy to Friendster, an early MySpace-ish/Facebook-ish thing which was never able to stay up.
It was a pretty common belief at the time that unreliable Twitter would be replaced by Pownce/Google Buzz/something entirely different.
> Interesting to me that when Twitter was ascendant the same predictions of doom were not made so frequently
It could be because Twitter was ascendant at the time as you described.
A simple and short lived glitch does not a #3 make. Twitter is better than ever now. Elon did good.
We're just pretending it doesn't now take the better part of 10 seconds for twitter.com to load now? That response times have gotten perceivably, measurably worse over the last few months? Or that these glitches aren't now a weekly occurrence?
I don't use it anymore but the odd time a friend will send me a link to it, and it is horrifically slow. I wonder if anyone will write about this time at twitter in a few years. Would be a case study in how to decimate a websites popularity and what not to do to avoid that.
Apparently there is literally a 5 second pause on load in the javascript.
"Meet the new Boss, same as the old Boss" -- and that's a slam on Elon who promised a ton of things like open sourcing the algorithm, etc. All I get now is a bunch of right-wing weirdo crap in my feed that I didn't subscribe to or ask for.
And this thing he was complaining about back in May, he completely f'd it up post-purchase:
https://www.makeuseof.com/how-to-fix-twitter-feed-elon-musk/
This is one of several different glitches and downtime seen this year.
A revenue collapse of 40% with a surge in fake verified profiles does not make Twitter better than ever. It is crazy to see a sudden sharp 40% revenue decline being described as better than ever.
While I've no trouble believing revenue dropped, where are we getting this 40 percent number and surge in fake verified profiles data from? With Twitter now in private ownership, Musk doesn't need to disclose real data and to best of my knowledge hasn't really.
Why?
Twitter in the age of Elon continues to lurch from one embarrassment to the next.
Twitter is broken for all users. Dang or someone else should merge this with the other twitter post on the front-page.
PSA: Mastodon, Misskey, Nostr, Bluesky exists now.
Just top 3 Mastodon instances(mastodon.social, pawoo.net, mstdn.jp) collectively has > 2mil users, same level as Twitter in 2008. Misskey, an ActivityPub/Mastodon compatible server software, now has >10K users. Nostr isn't much, Bluesky is still invite only and had just went past 2k registered, but those are all available options for direct substitutes to Twitter in case anyone still in need of a legacy twitterform social media.
Just chiming in to say not to visit pawoo at work.
> Just top 3 Mastodon instances(mastodon.social, pawoo.net, mstdn.jp) collectively has > 2mil users, same level as Twitter in 2008.
You really think 'pawoo.net' and 'mstdn.jp' are fabulous advertisements for Mastodon of over 2M users on those instances, unless you think CP and loli culture there is a great thing since it is totally illegal in hundreds of countries?
Secondly, both pawoo.net and mstdn.jp instances are owned by a single company called Mask Network [0], which essentially means it is not community owned and is under central control of a company that can do whatever it pleases, even if the users on the platform dislike it.
Finally you missed out another large Mastodon instance after mastodon.social which is braag.et which promotes CP and illegal content. So it seems that the instances with the larger amount of users also allows CP and illegal garbage on it.
It's quite hilarious to believe that Mastodon with these examples remotely has a chance against Twitter as an alternative.
[0] https://masknetwork.medium.com/mask-network-acquires-pawoo-n...
> You really think 'pawoo.net' and 'mstdn.jp' are fabulous advertisements for Mastodon of over 2M users on those instances
Yes.
My understanding at this point is that, firstly, instances that do not federate with these, and those cheap “CP” accusations, has no relevance in this discussion, because nothing comes out of those.
Secondly, it seems completely plausible to me at this time, that a central Mastodon instance will become the core of a Western European social media landscape, in the way this wartime Russian Federation maintains VKontakte, or that Communist China maintains Sina Weibo. And Misskey could be another such for another region, each contributing to slow segregation of the Internet at religious-social-political interfaces.
Such violent responses that you have expressed against the names of .jp and Pawoo is plausibly an indication of those developments.
> My understanding at this point is that, firstly, instances that do not federate with these, and those cheap “CP” accusations, has no relevance in this discussion, because nothing comes out of those.
It is totally relevant since not only you just mentioned both of those instances, but they also have over a million users there which CP and loli culture is pervasive on those instances and hiding the problem under the rug only makes Mastodon a far worse place, given that the majority of those instances is full of that CP content which is completely illegal in lots of countries and is hardly appealing to normal users.
> Secondly, it seems completely plausible to me at this time, that a central Mastodon instance will become the core of a Western European social media landscape...
Right, eventually defeating the whole point of federation with more re-centralization and co-ordinated instance-level banning and you advocating a centralized government controlled social networks being much better. What could possibly go wrong? /s
> Such violent responses that you have expressed against the names of .jp and Pawoo is plausibly an indication of those developments.
What "violent responses"? The basic facts about Mastodon may indeed hurt, but you advertising those two instances that have over a million users using it for loli and illegal CP content doesn't put Mastodon in a good light and makes it completely unsuitable as a 'direct substitute' to Twitter.
> given that the majority of those instances is full of that CP content which is completely illegal in lots of countries and is hardly appealing to normal users.
I say they can totally beep beep beep about that. I don't advocate violence and/or harm, but that's the Internet. If that isn't appealing to normal users, the Web 2.5.x and social media in their entirety are not for normal users, which it probably is a correct observation given recent reports of mental health issues skyrocketing. But I doubt Web3 or later will be any "better".
>> Such violent responses > What "violent responses"?
.jp, Pawoo, Misskey at this moment are kids running around. I would think something very similar can be said about *chan, though personally they creep me out. Either way, it's not a horde of groomers conspiring over Tor. When a bunch of smart people actively tries to reframe and crush kids running around as "dark web illegal CP sharing activities left unsolved in un-enlightened countries" that's a violent response.
With the continuous growth of streaming and video social medias and looking at what are trending there, I doubt the adoption of so-called "completely illegal in lots of countries and is hardly appealing to normal users" content will even slow down. It will completely normalize, and if it did not in the EU, the EU is going to isolate itself leading to further fragmentation of the 'net scape.
> and you advocating a centralized government controlled social networks being much better. What could possibly go wrong? /s
Oh, forgot this part. I think it's within possibility that more municipal level governments start hosting ActivityPub servers, irrelevant to whether it's idealistically ideal, in case there will be significant numbers of entities that can't migrate to Insta but actually needed non-Twitter-Twitter.
> If that isn't appealing to normal users, the Web 2.5.x and social media in their entirety are not for normal users, which it probably is a correct observation given recent reports of mental health issues skyrocketing. But I doubt Web3 or later will be any "better".
Who mentioned or is talking about Web3 here?
> .jp, Pawoo, Misskey at this moment are kids running around. I would think something very similar can be said about *chan, though personally they creep me out. Either way, it's not a horde of groomers conspiring over Tor. When a bunch of smart people actively tries to reframe and crush kids running around as "dark web illegal CP sharing activities left unsolved in un-enlightened countries" that's a violent response.
It takes me ONE second to link to open evidence of CP and loli content on the TWO original instances YOU promoted. If you're going to mention another instance; I might as well mention 'baarag.net' again. Since that is an equally large Mastodon instance in the millions and is one that you know that is not 'kid' friendly which the content hosted there is unsuitable and even illegal in the majority parts of the world and you know that.
> With the continuous growth of streaming and video social medias and looking at what are trending there, I doubt the adoption of so-called "completely illegal in lots of countries and is hardly appealing to normal users" content will even slow down. It will completely normalize, and if it did not in the EU, the EU is going to isolate itself leading to further fragmentation of the 'net scape.
By allowing loli and CP content for all normal users? You do know that there is a reason why the majority of countries that have CP laws have made it illegal?
> Oh, forgot this part. I think it's within possibility that more municipal level governments start hosting ActivityPub servers, irrelevant to whether it's idealistically ideal, in case there will be significant numbers of entities that can't migrate to Insta but actually needed non-Twitter-Twitter.
Governments go where the majority of normal user voter base is and that is on centralized social networks like Facebook, Twitter, Instagram and TikTok. They don't follow where techies, furries or loli and CP fans are hiding.
It does appear that the undocumented api that nitter uses still works and is unblocked by this change as I've been able to access twitter through nitter.
is it cached? have you tried viewing new tweets
No, it was also working with the self-hosted nitter instance I was using which should have almost nothing cached. Double checked with a new tweet posted in this thread.
If you like Tweetdeck and Reddit, checkout rdddeck [0].
The headline may overstate whatever happened.
I'd never used tweetdeck prior to now. Yet, it just now loaded fine for me. Once it loaded, I clicked a button that said something like, "setup some fields", and then tweets were displayed. What's not working? I'm just a free user of twitter.
> The headline may overstate whatever happened.
Or... it was broken for normal users and is now fixed.
The newspaper said there was a fire at this building? Yet, it looks fine to me now?
It is an overstatement to say something is broken, when it comes online 10-20 minutes later.
At Twitter's scale? It is not.
Hardcore engineering at work.
Muskops!
"This one API user has more calls than all the others combined."
"Disable them and see what happens."
It feels like we're being deliberately herded into Mastodon.
Obviously, that's paranoid thinking. But the results are the same in many cases.
A market for lemons developing. A reinforcement of the strategy for others. And more stressful things in our lives.
If people are resentful, I understand. I hope they can find peaceful communities and safety wherever they go. I'm sure there will be political or technical reforms to accomplish that.
I hope people remember in the end that there were beautiful and good people in different spaces on the Internet, including Twitter.
I hope I can choose my own story.
I was literally adding a 2FA authenticator app to my Twitter accounts that aren't Twitter Blue accounts when this happened. I thought it was something I did.
Good to know that I can rely on H/N to tell me what's really going on... and it's not "just me".
Twitter went down constantly in its early years and did fine; as long as errors get fixed, I don't see why that dynamic would spell doom for Twitter now. There are a lot of people for whom the idea that Twitter can get along without most of its former headcount is a bitter pill to swallow, but that doesn't make it untrue.
One reason the site was stable pre-Musk is that no one made any changes to it. For better or worse, it's now owned by someone who actually uses the product and has ideas for how to develop it.
Yeap. Most people commenting here are just bitter and are looking for any excuse to confirm their biases.
From a business perspective does it matter that Twitter is down for a moment? It's not a plane or medical machine. It's not blocking anyone from doing anything useful. Everyone are just going to check & post when it is up again.
It also doesn't mean that Twitter employees have a bad work experience like most here assume. Maybe they've got a permission to iterate fast, even if it risks bringing things down, and everyone are having a jolly good time, skipping on the boring chores ensuring everything will go smoothly usually takes.
Their status page once again shows no issues. https://api.twitterstat.us/
One can only assume the system that updates the status page is down.
Seems to be affecting web view but not mobile clients. Wonder if this has anything to do with them not paying their AWS bill as reported the other day.
I'm also getting the same error for the homepage.
Recursive error message, best error message.
This is all links. Not just tweetdeck.
It's not just tweetdeck. Any clickable t.co URLs (i.e. all URLs embedded in tweets) are broken.
On seeing these errors, for a minute I seriously wondered whether their hosting provider had started turning things off due to those unpaid bills.
Is down too, at this moment.
Wow, I have never seen the Twitter front-page before.
What a colossal piece of shit. Everything there is information-free and radicalized. The only maybe useful thing is the result of some game, that I assume it's soccer. (But British soccer, why would I care about British soccer? The rest of the page is localized into Brazil.)
It's up for me, maybe a geographically limited outage?
Working for me.
https://downdetector.com/status/twitter/
Looks like it's already being/has been fixed. Still, pretty impressive level of brokenness for a short time.
Most Twitter subdomains are down with the same error.
help.twitter.com, api.twitter.com, developer.twitter.com etc.
They definitely need chaos engineering team. Maybe, they had one, but they were fired?
Even before the current downtime a string was data-mined from the TweetDeck beta which referred to itself as "a feature of Twitter Blue" so the days of being able to use TD for free are probably numbered anyway.
Does anyone know of time-series data with Twitter incidents/up/downtime? Would be interesting to do an analysis of the service level and change point analysis wrt the firing.
Yeah, they stopped paying for API access because it got insanely expensive.
This happened right as I was using Selenium to log in to Twitter for a project. Was wondering what the hell I was doing wrong until I saw this and realized it wasn't just me.
Not that I particularly like Elon but people are now making a big deal out of every twitter outage as if twitter didn't spend down half of the time before Elon bought it.
I dont remember Twitter being down so often before the takeover. I actually distinctly using Twitter to check if OTHER websites or services were down
Twitter had issues early on, but before Musk bought them they definitely did not have outages half the time.
No, definitely not half the time... a third tops.
I've become accustomed to the fact that it's beyond clear that pre-Musk engineers pushed changes to the servers live without testing them first, and didn't even bother doing an incremental roll-out either. Either they had no engineering culture, or that culture was gutted long before he arrived, because Twitter had problems with frightening regularity.
Every speed bump and hiccup of Twitter's outages since the acquisition is now magnified by the new standard expectation of 1000% uptime by the schadenfreude brigade.
Before it is all '#hugops' and 'best wishes to the engineers at Twitter' when it had downtime before the acquisition. But as you can see, they all love to hate it because a person called Elon R. Musk owns the blue bird site.
Just like when everyone here thought that Facebook, Instagram, WhatsApp all collapsed and went down for hours it was declared as the 'end of times' the 'death of Meta', etc, with it's network effect still unaffected by that.
The same thing is happening for Twitter as even when it goes down, it's network effect of 220M+ users is still sitting there waiting for it to get back up.
Surely this will be the end of twitter forever!
for reference: I see absolutely none of the things anybody is saying they are seeing as errors. Twitter works exactly as it ever has for me.
The former you said is in no way implied within this post or its link.
The latter is a kind of anecdotal evidence that does have no value in discussions like this. The linked post is from the official Twitter account stating that things are broken and it is for many people. If you don't see it this could be due to many conditions on why it might seem working on your device/client/account. This does not lead to any logical conclusion that these information might be wrong.
Tweetdeck provides access to cherry pick from a goldmine of fresh search data by 'likes' and retweets. The latest tweetdeck is tough slogging to use.
Twitter devs don't have Slack right now to even discuss this. They are all in one crowded conference call, panicking, and with Elon screaming.
Maybe we could GoFundMe a couple of Slack accounts to the Twitter devs?
Yep, something has gone very wrong. New images are also returning the same error. I assume the person that used to fix such things has been fired.
Twitter should not use a redirection service for links in the first place. Let a link be link. Ideally it should also not track click-throughs.
Incredible that MuskBird lacks the alien technology of checking the log to see which customers are still using the API before turning it off.
Normally, this solution works great.
At Twitter's scale with the number of API users they had, I can't imagine how they'd filter the signal out of the noise.
This is very much a "someone would have had to know we're using our own API to avoid this disaster" scenario, which is an institutional knowledge problem. The kind of problem that gets hard to solve when XX% of your workforce suddenly left to seek new opportunities.
Sorry no. It is not an oral history problem. You simply group the stats by caller. “At Twitter scale” implies they already have this dashboard.
Ah, good point. Twitter should have been the largest caller.
That 467 error code suggests to me something else is going on and Twitter is emitting the wrong error message (467 isn't a standard HTTP, so I'm wondering if something lower-level emitted a 467 error, it was misinterpreted as an HTTP status, and the error string chooser logic is giving that API access error message due to fall-through).
What's up with that 467 error code? That's not a standard HTTP status code; I wonder what it means?
2 full time bodyguards to protect Elon from employees when he goes go to bathroom
0 engineers to prevent this from happening
I am not able to access twitter in any way from my macbook's browser.
I can access it from my mobile browser.
I get random random errors and can't really browse (logged in)
Farewell?
The "weird nerds defending Elon Musk" meme gets more true as time goes on.
https://twitter.com/CaseyExplosion/status/101855884867059302...
This isn't "you can't run Twitter with half of its 2021 headcount".
This is "Elon Musk is deliberately mandating bad software engineering practices". I will decline to speculate whether that is out of malice or incompetence.
@elon, what have you done?
No bio links work for me
It's back
Y'all are silly and insufferable. Twitter had a temporary outage that was quickly rectified and you act like it’s some massive catastrophe directly caused by his highness Elon. Like you’ve never pushed a breaking change before…
Time to burn my imaginary internet credits again.
I won't argue that firing all the engineers so swiftly wasn't a mistake (I mean I _could_, but don't want to dig myself any deeper than necessary in a single post). What I will say though, is that this gives me hints as to the quality of engineering that went on at Twitter.
I feel like some stellar Rube Goldberging went into solving problems that could have used simpler, if not _less CV boosting_, solutions. I've been at places like this. The engineers have fun building convoluted "solutions" for the sake of saying they worked on cool-tech-x. And surprise, it needs endless maintenance.