Abi

I think it might be a performance feature, when building the timeline for user A, we pull content from various public accounts + accounts the user follows, but we have to query each tweet in the generated timeline for their authors, then check to see whether the author has blocked user A or not. Because authors who blocked user A don’t want A to see their content. That query is expensive, because you are pulling the block list of every single author of every tweet that comes to your timeline.. by removing that extra check I bet gettimeline should run faster. I think they removed that because blocking users from a public account can be easily mitigated, just open incognito window and you can see everything. Mute however is cheaper, we get a timeline and we filter it against the current user mute list which is tiny. Now you still can’t interact with the tweet, if the author blocked you which is fine, that is a cheaper check on interaction. Of course this won’t stop someone from screenshot and engage. which is what i think the goal here is (sigh) im just interested in the engineering.