Live data from Hacker News

Twitter Is DDOSing Itself

sfba.social

831–840 of 1001 posts

Re: Twitter Is DDOSing Itself

#831

Earlier quoted context omitted.

> goals of my organization What do you think they are?

The organization’s stated mission, inherent not just to it but to all places of its sort, is , even though, unfortunately, we often end up chasing instead. It’s a difficult balance: is in fact necessary to continually achieve but there are times where decisions focus exclusively, or at least too much, on . But we live in the real world, and sometimes that’s necessary. ( is not money though it has an impact on our fin…

> but I value my privacy

I guess the way you abstracted will probably reduce your privacy (a tiny bit). At least I have not seen anybody write "" instead of just X in this usecase.

So either this is very specific to you, or is very common in your circles so you do it too. Both of which reduce the number of potential candidate if somebody tries to doxx you.

Additional you (or your editor) uses “” over " which also reduces the number of candidates.

(Not trying to attack you here, just thought it was notable)

Re: Twitter Is DDOSing Itself

#832

Earlier quoted context omitted.

The people at Twitter who understood the system and could predict the side effects were all fired or left. My guess is Elon said "the site's too slow!" Engineers noticed that the home feed request was slow. They didn't understand how it worked, had no tools to profile it, and were given an unrealistic deadline to fix it. So about the only thing they could do was issue multiple, parallel requests and hope that at leas…

>The people at Twitter who understood the system and could predict the side effects were all fired or left Not necessarily. I’ve predicted bad outcomes for decisions in a few cases and been ignored but stuck around regardless. Mostly because I like my job and the goals of my organization even if it makes bad decisions. Of course to remain productive and improve my influence in future decision making it is absolutely…

Tell me you're in your 4th year at a BigCo without telling me you're in your 4th year at a BigCo.

The goals of the organization are mostly a facade. The people running the organization, and their actions, are what the goals of the organization actually are.

Re: Twitter Is DDOSing Itself

#833
post #126

Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement. Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof. I can of…

I'm curious about this: When you were experiencing this, why didn't you quit? I truly feel bummed for the people remaining at Twitter who are miserable but for whatever reason feel they can't just quit.

That is a good question, but on the two specific occasions when something of this sort did not make me leave instantly, there were very specific factors at play. I cannot comment on the first situation as that would require an extensive post with an obscene amount of context on my background, politics in my country, the people involved, weighing up the public good, etc. Simply, would go beyond a HN comment and I feel I couldn't do the situation justice anyway for someone who wasn't following local news at the time these things happened.

The second instance, I feel I can comment on, though allow me to leave out details to spare the people involved public embarrassment.

There, the changes, whilst annoying and born out of a complete misunderstanding of a core part of their alleged competency (Imagine a Botanist telling you leaves are always blue because that is the color of the sky), were not going to break anything, just look silly and create unnecessary, but compensated, work.

In that case, I also viewed the specific project finally launching as vitally important to our user base and wanted the results to go public for their benefit, so the decision was made to document and execute on their requests, so we could go live.

Of course, two weeks before our go live date, they changed their requests again ("leaves are not blue, they are violet because of the wave length of light") and had a hard time understanding that changes can have a knock on effect and some things are a bit more complex than Find and Replace. If I had been forced to make those changes at that point, I'd have packed my bags.

Simply said, when my work has the potential to benefit users and I know that arguing, even though I am correct, will lead to massive delays, I'd rather just put that silly request in writing and deal with these things after the users have received what has been worked on. Try to explain when someone is wrong, but if that doesn't work, finish the project, argue later.

Of course, if after the fact responsibility isn't taken, that finished project gets mentioned in my CV for the next employer.

Re: Twitter Is DDOSing Itself

#834
post #572

Earlier quoted context omitted.

Twitter Engineers have had over a year to get out and find another job. At this point the terms of their employment and the expectations from their boss are all crystal clear. Hard to sympathize with those who continue to stick around for whatever reason.

Someone pointed out that it looks like most of the workers that stayed at Twitter appear to be foreign born and are probably reliant on Twitter's sponsorship of their H1-B visa. https://www.vice.com/en/article/n7z5px/twitter-employees-on-...

Can sponsored H1-B visa holders look for another sponsorship to try to switch jobs, or would they get deported after resigning from "hardcore Twitter"?

Re: Twitter Is DDOSing Itself

#835

Earlier quoted context omitted.

It seems more plausible than the alternative. Let's say that Twitter availability issues were really caused by disabling anonymous access and that Elon wants to back out of his decision due to public backlash, wouldn't he just reverse the decision? That would fix both of his issues at once. He could even claim to have solved the scraping issues through a clever trick that doesn't require disabling anonymous access. T…

The theory is more that Elon wants to prevent public access to Twitter in hopes of making it more profitable, but he doesn't like the backlash to such cash grabs and has invented this story which makes the Auth requirement and non-paying account view quotas more palatable. It's important to note that Twitter's desires are fundamentally at odds with the desires of the content creators on Twitter on this point. Twitter…

My initial contention was directed towards the claim that Twitter was accidentally DDoSing itself. However, it seems you are proposing another theory - that there is no DDoS at all and Twitter is "faking" its availability issues to introduce quotas and a login requirement. While I personally perceive this as veering into conspiracy theory territory, I concede that it isn't entirely beyond the realm of possibility.

Re: Twitter Is DDOSing Itself

#838
post #676

Earlier quoted context omitted.

You might be right; the person you're replying to might have zero idea. Now me... I know someone personally who was a senior exec for Twitter's software team, who left after Elon's purge. He left because all the people who understood the system and could predict the side effects were fired or left. He'd been with companies going through death spirals before, and had no interest in being involved with another one. So,…

I don't know you or your friend, but thinking how dreadful some hiring process can be, I would defer changing my job as much as possible..

Arguably, most of the ex-Twitter employees had zero say if they wanted to defer a job search or not.

They were just summarily fired.

Re: Twitter Is DDOSing Itself

#839
post #126

Speaking from very painful, personal experience, few things are more agitating than being forced to execute on something you fully know is a horrible idea, especially when you tried and failed to communicate this fact to the individual pushing you to go against your best judgement. Even more so when that person later loudly proclaims that they never made such a request, even when provided with written proof. I can of…

The people at Twitter who understood the system and could predict the side effects were all fired or left. My guess is Elon said "the site's too slow!" Engineers noticed that the home feed request was slow. They didn't understand how it worked, had no tools to profile it, and were given an unrealistic deadline to fix it. So about the only thing they could do was issue multiple, parallel requests and hope that at leas…

It is very possible that they did not predict this specific down stream effect, for one of many reasons. I do not want to discount that, though, as I am not at Twitter and am not on a first name basis with anyone there. Maybe there are some who did see this.

What I maintain though is that most anyone still working on code at Twitter, regardless of their experience or overview of the code base, would strongly argue for testing and staging, which appear to go against current leadership's mode of operation, likely because of the time pressure you mentioned.

Not pushing such changes straight to production is a concept I feel anyone working at Twitter would subscribe to, yet has to painfully go against, lest they be led go.

Re: Twitter Is DDOSing Itself

#840

Earlier quoted context omitted.

People didn’t leave because of the bad decisions. They left because Musk said he wanted “hardcore” people who’d work 80 hour weeks. Turns out masochism isn’t correlated with great engineering.

yeah its correlated with getting deported from the US if you lose your employer

I bet that most, if not all, H1B visa holders working for Twitter, would be able to land a job pretty quickly if they wanted to.
Post reply on HN