> Even in email, spam is still not really solved. I still get both false positives and false negatives. See my comment about Secure Scuttlebutt below. Email is

> Even in email, spam is still not really solved. I still get both false positives and false negatives. See my comment about Secure Scuttlebutt below. Email is a little different, in that complete strangers (and apps) should be able to reach you. However, that's not the case with FaceBook, Slack, Instagram etc. If you sync exclusively with people you know (or your organization) and their connections, spam won't exist by design. What you gotta do is to model online communities similar to the physical world. In meat space, you choose the people who you are accessible to. That'll work here as well. > I see your point here, but would also counter with: degraded security because we need N databases to patch every issue after the issue is public, rather than 1 database (potentially) before the issue is public. WASM-based db engine could be a good option, if the app is browser based. We could treat it as part of the app, and the standard security considerations apply.