421–430 of 1001 posts
Matters 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
Twitter links are now poisoned, and basically useless.
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…
The only difference between then and now is that there is a big personality at the top who now personifies everything Twitter does, especially if things go wrong, whereas before it was mainly just a faceless bureaucracy whose Trust and Safety lead at times had more visibility than the CEO.
The subtext is that Twitter changing hands also involved trimming a lot of the dead weight, particularly hitting the softer managerial/diversity/HR side. Now a lot of people are rooting for the site to fail because it has gotten too "bro-ey", as the era of trust-and-safety and $15k backchannel bluecheck deals has made way for free-speech and monthly subscriptions.
Earlier quoted context omitted.
At least once have I done a CC blast as a form of insurance when being asked to do something absolutely boneheaded.
You gotta get executives in writing sometimes or they'll throw you under the bus later.
Earlier quoted context omitted.
I am not disagreeing with you but self-ddos is not entirely uncommon. When I worked at Amazon this would happen a few times a year. Not on the main amazon.com website but on supporting services often initiated by but not limited to kindle devices. Having something like this slip through the cracks of even experienced engineers isn't uncommon.
But in such cases surely there's some kind of rate limiter in place? I mean, if I'm reading that screenshot correctly this is 700+ requests a minute. I've tripped the rate limiter with less on other sites.
Not really, our team maintained a reverse-proxy that fronted all requests that came into amazon. And whenever we would have a self-ddos event, we'd get a request from the backend team whose service was getting self-ddos'd to shed traffic before it reached their service hosts to prevent it from browning out. In many case ddos's were coming from kindle devices which were not even easy to update so deploying a "fix" wasn't even always an option.
Earlier quoted context omitted.
Speaking from a US perspective... Unions are the reason we have a minimum wage, limited work week, paid holidays, equal pay for equal work, unemployment benefits, workers' comp, the family medical leave act, and many more things. If not for unions we would all still be doing sixty hour weeks getting paid in company scrip. "Socialism" brought us Social Security, Medicare, child labor laws and agriculture subsidies, he…
To be fair, social security and Medicare are causing the USA budget deficit
Earlier quoted context omitted.
Clearly there is something wrong with the site. So I don't doubt there is a bug. But the OP gives no helpful information that could be used to reproduce the issue and fails to describe it in any helpful detail really. They seem content to just effectively say "Twitter is dumb." Which, again, is fine but not all that technical and interesting.
There’s information in the post that very probably points at the underlying cause. The scrollbar jumping is a dead giveaway: Twitter loads more content based on scroll position. If your viewport is sized such that displaying the error message triggers another load event by its corresponding change in scroll position, it will try again indefinitely absent some additional logic to bail out. Edit: this of course depends…
Maybe that theory is correct. But I feel like pretending this post is getting to the top of HN because it's a technically interesting diagnostic analysis is sort of silly.
Earlier quoted context omitted.
Employment is not the choice in the USA because health care is tied to it. The second reason is H1B.
> Employment is not the choice If you’re a software engineer anywhere in the US (with exception of H1B/TN/etc), where you work is 100% your choice. There isn’t a shortage of open engineering roles in this country. Nearly 100% of full time positions include fully paid healthcare.