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.
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.
Are you saying the engineers who are now at Twitter don’t have the right skills?
It's very easy to get caught in assumptions like, "Nobody would ever do things THIS way, so they must have built it THAT way," only to find out that, once upon a time, THIS way was the right way to do things, only for it to over time become less and less optimal, but the costs of changing things were too high to fix it. Once your system is old enough and large enough, you'll have several thousand things just like that.