@thephd You mean, like the first description of a buffer overflow was in the "Anderson Report" around 1965? And that lead to things like hardware bounds checking (Multics), languages with bounded strings and arrays (PL/1, Pascal, Modula), and run-time range checking? And the C came along and...

@nawi @tootapp @ConnyDuck It's a self-correcting problem: if app devs block Nazis everyone wins except Nazis. If app devs block too many other things or less repugnant things then there will eventually be a larger market for new apps that still block Nazis, but not less extreme content. Would you feel the same if the app dev was blocking pedophilia? Rape apologists? Murder-for-hire solicitations? Are you saying those things should be available by default?

@nawi @tootapp @ConnyDuck You can educate people about Nazis without listening to Nazis or giving them a platform to push their ideas. Some ideas deserve no respect, no quarter and no opportunity to be debated. Trying to be "fair" only gives them some semblance of legitimacy and allows those ideas a chance to re-spread and infect those with an impaired anti-Nazi immune system.

@nawi @tootapp So, the app becomes useless for talking to Nazis? (SRSLY - I get what you're saying, but if an app owner goes overboard and starts blocking non-hate speech, then there will be a market for a different app.)