That’s not really a solid argument. Blocking is likely implemented as a very tiny piece of what is already very likely a massive table join operation. Computationally, it’s likely to have as much an impact on their compute costs as the floor mats in your car have on fuel efficiency.

Everyone already sees different content. It’s an inherent part of Twitter. It’s not a static site where everyone sees the same thing. You see the tweets of who you’re following, and don’t see tweets of those you’ve muted. All that filtering is happening at the server level. Any new tweets or edited tweets or deleted tweets change that content too, which is happening potentially hundreds of times a second for some users.

Anyway, caching would be implemented after a query for what tweets the user sees is performed to reduce network traffic between a browser and the Twitter servers. There’s some memoization that can be done at the server level, but the blocking feature is likely to have almost no impact on that given the fundamental functionality of Twitter.

But you can upvote and comment. OP didn’t specifically say posts, just increases in upvotes and socialization

I had the Samsung Note 2 back in the day. I installed a custom bootloader and OS that worked fantastically. I had GPS issues, and all the guides I read said I have to reinstall Samsung’s OS, get a GPS fix, then reinstall my custom OS.

I made the mistake of installing a newer version of the Samsung OS which installed Knox and locked down my bootloader. I was now locked into an old, insecure Android version with no possibility of ever upgrading because Samsung abandoned it.

From that day on, I vowed never to buy another Samsung product again. Screw them and their anti-choice bullshit.