736
Elon Musk Says Twitter Is Going To Get Rid Of The Block Feature, Enabling Greater Harassment
(www.techdirt.com)
this post was submitted on 11 Jun 2023
736 points (100.0% liked)
Technology
37736 readers
393 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's interesting to me that they made the argument that blocking is increasing server costs.
I mean, it's plainly clear that Musk has no idea what is going on at any of his companies and the narrative of him being a genius of some kind was simply that: a narrative.
In a way, I could imagine it increasing server costs by like 0.001%, if even that, because if the algorithm finds a post to recommend but then realises it's from a blocked account, it would have to search again (ofc it's probably optimised so that it realises that at an earlier stage).
But we're talking about such small details it literally doesn't matter and is outweighed by the functionality lost one hundredfold.
I expect it's accurate to say; their architecture is not like a database where you can add an index on a blocked state and then join against it. You have to get a list of potential posts that the user might want to see and then eliminate any in the block list. There will be a few edge case users who have thousands of block entries and a multithreading strategy is likely required to swiftly filter it in a reasonable timeframe.
However, an architecture I've seen that works around this is to build this timeline in the background and present it to the user from a cache, I don't know if this is what Twitter does as I never worked on that. However, if you want to not have a block feature but have some kind of mute feature anyway I don't see how there is a meaningful difference.
Yeah, sounds like that's the case. Funny how flaws in system architecture gets exposed to the public through vapid excuses these days.
My guess is muting would likely result in a decrease of overall visibility. Every account gets a mute score.
As I understand it it's because of block lists making large queries as soon as someone subscribes to it. I don't condone the removal of the block feature, just trying to answer your question to the best of my knowledge.