Earlier quoted context omitted.
A union vote is the only way to save that platform. Either unionize or let the company die.
Unions are for the people, not the company
a company is made of: _____
Twitter Is DDOSing Itself
591–600 of 1001 posts
Re: Twitter Is DDOSing Itself
#592Earlier quoted context omitted.
Some of the remaining engineers may be stuck due to H1B
Canada just changed their immigration program such that they'll accept all H1B holders (working or not) into Canada with a similar visa, but without the requirement to find a job immediately. Something to look into for any Twitter (or other) engineers who are bound to a company due to lack of options. https://www.forbes.com/sites/andyjsemotiuk/2023/06/28/us-h1-...
Sure, but if you've built your life in the United States that still means moving country
Re: Twitter Is DDOSing Itself
#593Earlier quoted context omitted.
> The people at Twitter who understood the system and could predict the side effects were all fired or left. This is like a case study in what happens when you fire everyone except the sycophants and yes-men. I only feel sorry for remaining non-yes-men twitter employees who might still be there because for whatever personal reasons they're in a precarious economic situation where they can't quit (H1B?) or are tied to…
> This is like a case study in what happens when you fire everyone except the sycophants and yes-men. The initial and biggest waves of layoffs last year were of people who hadn’t yet had a chance to demonstrate whether they were or were not sycophants. They were essentially random.
You're correct that they could have also fired some sycophants. But that doesn't mean the current proportion of sycophants is any lower.
I should also add that Musk's management methods are likely to turn any remaining people in to yes men. E.g., his "demon mode" routine: https://fortune.com/2023/06/29/elon-musk-demon-mode-rip-peop...
Re: Twitter Is DDOSing Itself
#594> If you missed the initial news of the impending showdown, Platformer reported on June 10th that Twitter had been refusing to pay Google for its cloud services ahead of their contract’s June 30th renewal date. > Twitter’s Google Cloud contract dates back to 2018. https://www.engadget.com/twitter-has-supposedly-started-payi... Oh... this explains all this fiasco :facepalm:
Twitter does not use google cloud as the main backend service. All of its self hosted.
Gcloud only supports batch jobs and data analysis.
Re: Twitter Is DDOSing Itself
#595Earlier quoted context omitted.
In this job market, it's hard. And many engineers are on H1B visas so it's even harder to jump ship.
If they truly cannot get another job despite trying hard for 15 months then really they should be thanking Musk for giving them a steady paycheck when no one else in the industry will.
If I understand correctly, the U.S. doesn’t allow them to get another job without getting a new H-1B and there are dramatically more applicants than visas each year. They are unlikely to get a new one so their options are to either stay at Twitter or leave the U.S.
Re: Twitter Is DDOSing Itself
#596Earlier quoted context omitted.
Ok, but the only people left are either hostages or sycophants. Doubt either care at this point.
Or they're just people trying to earn their pay. Why must everything be a political divide these days...
You say that in a tone of contradiction, but sycophants are absolutely trying to earn their pay. They've just decided that their true job is what their context rewards.
Re: Twitter Is DDOSing Itself
#597Re: Twitter Is DDOSing Itself
#598This bug is very unlikely to be the reason. The rate limiter on the server side is cheap and the frontend bug only gets triggered with the rate limit active. I have seen similar bugs in the systems I oversee because network libraries love to retry requests without sane limitations by default. But I never saw them make our rate limiters sweat. It's slightly more annoying when they hit an API which actually does some e…
I don’t think it’s necessarily saying the self-inflicted DDoS has caused a technical issue that’s forced them to shut down access. I think it’s possible that shutting down anonymous access caused the DDoS, which led to giant spikes in some metric , which led them (Elon) to conclude that there was an uptick in scraping, so they imposed the 600/tweet/day limit to punish scrapers. Seems like either my quota reset or the…
This. I'd bet substantial amounts of money that the evil scraper idea is the result of a) another issue + b) paranoia + c) Musk thinking he understands better than anybody else.
Re: Twitter Is DDOSing Itself
#599Earlier 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. Are you saying the engineers who are now at Twitter don’t have the right skills?
All the best people I know left.
Re: Twitter Is DDOSing Itself
#600Speaking 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…
[flagged]
Ooh, good idea. People can go build something against the Twitter API! Oh wait!
I'm absolutely going to keep enjoying Musk's comeuppance. In this, consider me a traditionalist. As the Greek tragedies show, people have been enjoying the just punishment of hubris for thousands of years.