Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twitter was down

twitter.com

Post reply on HN
Print view View original

171–180 of 493 posts

Re: Twitter was down

#171

Post by tsimionescu »

secondcoming wrote: post #13
roboyoshi wrote: post #10

In 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.

Everything seems fine for me when I use the main website.

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).

Re: Twitter was down

#172

Post by mandeepj »

papito wrote: post #30
roboyoshi wrote: post #10

In 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.

[flagged]

> Honestly, I'd just quit right now and pour myself an extra-large drink. It would feel amazing after this much abuse.

Unfortunately, there are his blind followers trying to emulate him. Not sure what havoc they are planning to unleash on their employees.

https://www.businessinsider.com/marc-benioff-elon-musk-ceos-...

paywall-less link - https://archive.ph/HbC3k

Re: Twitter was down

#173

Post by tashoecraft »

billti wrote: post #56
nkozyra wrote: post #25

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…

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.

Re: Twitter was down

#174

Post by ffreire »

kibwen wrote: post #165
photon12 wrote: post #111

Earlier quoted context omitted.

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?

Re: Twitter was down

#175

Post by MrOwnPut »

rgbrenner wrote: post #163
JumpCrisscross wrote: post #119

Earlier quoted context omitted.

> Did you see the photo of the employee sleeping on the floor? I’ve done this. I had lots of fun—everyone, from the CEO down, was crunching—and became financially independent after it. It’s usually a sign of under-resourcing. But almost every start-up experiencing unexpected growth should be ready for it. It’s unusual at Twitter’s scale, but closed to mismanagement than abuse.

That's great that it worked out for you.. That twitter employee wasn't so lucky... she was fired last week: https://thehill.com/policy/technology/3876505-twitter-employ...

A picture of someone sleeping on the ground is not really a good indicator of their work performance one way or the other.

Only the company would really have insight into that.

Pulling a late night and sleeping on the ground does not make you immune to a layoff.

Re: Twitter was down

#176

Post by top_sigrid »

thepasswordis wrote: post #156

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.

Re: Twitter was down

#177

Post by SauciestGNU »

doomleika wrote: post #90
jedberg wrote: post #44

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 t…

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.

Re: Twitter was down

#179

Post by brucethemoose2 »

mikebonnell wrote: post #97

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...

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?

Post reply on HN