Consider # of items you'd have to blacklist vs. whitelist. Consider negative consequences of delaying adding something to a blacklist or whitelist. (Assume there will be delay between identifying something should be listed -> it being listed, and what does that cost.)
-
-
-
Good criteria. A variation of the delay criterion is: the consequences of a mistaken addition or omission (some kind of 2X2 is hatching in
@vgr subconscious right about now) If # of items are not very different, the difference in ease of compiling - 1 more reply
New conversation -
-
-
Whitelist for high quality at low volume. Blacklist for acceptable quality at high volume.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
borrowed from another domain (sysadmin/devops/webshit) if a failure in the node could cascade to other nodes it should use a whitelist (with expiring credentials maybe). if a failure in the node can only bring down that node a blacklist is probably ok.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Centralized vs decentralized decision making.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I wish there were a way to follow tweets.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Whitelists, always.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.