The Elon Twitter movie will be the next Borat, I can’t wait.
Twitter Is DDOSing Itself
431–440 of 1001 posts
Re: Twitter Is DDOSing Itself
#432Matters little, but the rate limits are opening back up. 6k/600/300 -> 8k/800/400 (~noon) -> 10k/1k/500 (~3pm) https://twitter.com/elonmusk/status/1675214274627530754 and self-reply
Re: Twitter Is DDOSing Itself
#433Earlier quoted context omitted.
Well "forced to execute" is somewhat subjective. If you are convinced leadership is doing the "wrong thing," then best to either leave or accept that you're just collecting your paycheck. In the case of Twitter, the new owner has thoroughly broken the advertising business and is trying to aggressively pursue a new version of the data business Twitter once had-- E.g. Google's Caffeine, which Twitter also eventually lo…
> Well "forced to execute" is somewhat subjective. If you are convinced leadership is doing the "wrong thing," then best to either leave or accept that you're just collecting your paycheck. Я, Unless your visa is sponsored by your employer.
The OP is fundamentally wrestling with an issue of justice, but the bottom line is that in business there is no punishment for stupid. There is only reward for profit.
Re: Twitter Is DDOSing Itself
#434Re: Twitter Is DDOSing Itself
#435Central Services finally caught Archibald Tuttle, now everything is falling apart.
Re: Twitter Is DDOSing Itself
#436> 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:
As the article says, and as Bloomberg, etc have also reported. Twitter finally agreed to play nice with Google and the issue was resolved. They are probably trying to get off of GCP, but this isn't because they suddenly lost access to GCP from payment refusal.
Re: Twitter Is DDOSing Itself
#437Speaking 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…
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 the company for healthcare coverage (Thanks, America, for being the greatest country in the world) because they can't afford any other health insurance option.
Re: Twitter Is DDOSing Itself
#438Earlier quoted context omitted.
I'm sure the loads are not comparable.
Honestly. what the fuck is this response? I hear always that centralising everything is great because efficiencies of scale: but then we have something that works as good or better and the response is; “ah yeah, but the load is so high!” Why do I care? I don't honestly give a shit about how much load you have, you could be factoring Pi on every page load; it means -nothing- to me. I kindly invite you to give more of…
Re: Twitter Is DDOSing Itself
#439Re: Twitter Is DDOSing Itself
#440What I find more ironic than this bug is is that all of these Mastodon evangelists still have Twitter accounts after their Elon meltdown. So much so that they even use it after Twitter stopped public access.
But also, yes, I use it to observe the latest meltdown; why shouldn’t I?