Currently, BlockTogether allows lists of up to 250,000 blocks to be shared.
Some problems:
1) 250,000 blocks renders the Twitter's first-party iOS client nearly unusable. It appears that blocking checks are done client-side, and the checking is very inefficient. Twitter pauses for multiple seconds or crashes when scrolling rapidly, and the battery goes full burn. The same is likely true of Twitter's other first-party clients and some third-party clients.
2) Some Twitter clients (eg., Tweetbot) simply ignore very large numbers of blocked accounts. The additional accounts a user mutes will have no effect.
Currently, BlockTogether allows lists of up to 250,000 blocks to be shared.
Some problems:
1) 250,000 blocks renders the Twitter's first-party iOS client nearly unusable. It appears that blocking checks are done client-side, and the checking is very inefficient. Twitter pauses for multiple seconds or crashes when scrolling rapidly, and the battery goes full burn. The same is likely true of Twitter's other first-party clients and some third-party clients.
2) Some Twitter clients (eg., Tweetbot) simply ignore very large numbers of blocked accounts. The additional accounts a user mutes will have no effect.
3) If a user encounters problems such as above, cleaning up afterward is a challenge, as per https://github.com/jsha/blocktogether/issues/266