zlacker

>>ZacnyL+(OP)
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 course not say whether the people currently working at Twitter did warn that the recent measures could have such major side effects, but I would not be surprised in the slightest, considering their leadership's mode of operation.

Even as someone who very much detests what Twitter has become over the last few months and in fact did not like Twitter before the acquisition, partly due to short format making nuance impossible, but mostly for the effect Tweets easy embeddability had on reporting (3 Tweets from random people should not serve as the main basis for an article in my opinion), I must say, I feel very sorry for the people forced to work at that company under that management.

>>Topfi+Ew
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 least one of them was fast.

I worked in the games industry for a while, and came to understand how they could spend so much money and so much time, and yet release a game where even basic functionality was broken. It's exactly this sort of extreme schedule pressure that, ironically, makes a huge morass where changing one thing breaks 10 other things, so progress grinds to a halt.

>>martin+oN
> The people at Twitter who understood the system and could predict the side effects were all fired or left.

You have zero idea if that is true or not.

>>sigzer+O51
About 80% of Twitter was laid off or quit. I think it's a reasonable supposition that a good number of those were critical personnel who felt they could get a better deal somewhere else.

>>lolind+i61
This rhetoric is well past its peak. When the firings happened, people said twitter would crash in a week. It's been a long time since then, and twitter, for my very generic uses and purposes, has just gotten better.

Demonizing past hard decisions at every unrelated point of difficulty has to be the worst kind of toxicity there is.

>>maxlin+VG1
> for my very generic uses and purposes, has just gotten better.

Interesting. My "generic uses and purposes" was to occasionally scroll around through tweets somebody linked me to.

That's entirely impossible now since I don't have an account (and don't plan to create one).

Roughly speak, it has become infinitely worse for me.

>>correl+CT1
It's a big holiday weekend in America, and having an outage seems like a minimal inconvenience, especially for those of us without an account.

There are entire communities of people who relied on the ability to simply read Twitter without an account, took the time to write code of their own, and now are reacting with much more maturity than HN seems to be. The petty personal attacks are simply astonishing.

"RIP Nitter" https://github.com/zedeus/nitter/issues/919