Extra database calls, running extra logic to check if you’re blocked. That sort of stuff I guess. It does make sense, compute, storage and network resources can be very expensive if you host on cloud providers like Azure or AWS.
Feed generation is already a very complex process implementing hundreds or thousands of variables to show every single user only posts that are likely to be relevant to them. Filtering out any posts by blocked accounts shouldn’t matter here. The real reason why Elon removed the feature is probably that he realized he was the most blocked person on Twitter, lol.
Extra database calls, running extra logic to check if you’re blocked. That sort of stuff I guess. It does make sense, compute, storage and network resources can be very expensive if you host on cloud providers like Azure or AWS.
Feed generation is already a very complex process implementing hundreds or thousands of variables to show every single user only posts that are likely to be relevant to them. Filtering out any posts by blocked accounts shouldn’t matter here. The real reason why Elon removed the feature is probably that he realized he was the most blocked person on Twitter, lol.
It would make it less computional, even if it adds a row of cells in the database.
When it tries to load something and sees that the person is blocked, then it doesn’t need to load anything else.
It would literally load less posts.