@mamba_cbk7210 Thanks! It's a bit tricky because Android apps cannot be extended like browsers (Android Firefox supports extensions though).
Or, I could add a bot, which works on all devices, but possibly in response to certain events; it would be different behavior.
Will think about it 🤔
@Lurils There is nothing special about 29; maybe rate limit (too many request in short time, will resolve on its own after a while) or try reload the tab, in case it is memory related. I am assuming the match rules did not change.
@UnusedArmor @TonyBamaga @ZLOK Who knows, it is their internal server rate limit: https://t.co/jWN5dBvKrW
That means any mass block does either not mass block like they claim, or builds a queue to get around this restriction, and blocks over a very long period of time.
@kingdomfantasy6 I am open to suggestions of how to handle it better! Maybe make the prompt configurable by keyword instead of all or nothing? let me know.
@Tadness121 Twitter does not allow mass blocking over short period of time, will need to queue and do it over a long period of time. I think current max is 50 blocks/15 min time period. Extensions cannot bypass this limit since it is enforced by twitter.
@ChaKatKimber @sigmamayo @e_sequin Megablock makes promises they can't keep; there is a rate limit on blocks over time. But I can and actually will block based on keywords.