@pub_cel

The problem with 0, null, {}, etc., is that all of our code expects a well-formed message, and tends to throw errors when you don't have one. We can use a fake or modified message, which is what I'm doing now, but I've seen an abundance of peering errors that may suggest that the gossip code is viewing it anyway.

@moid

The way you've done it in filter_log() works, and that's how I'm currently doing feed deletion. The problem is that it's incredibly slow, especially on mobile devices, and so the next step is to do deletion without rebuilding the log or indexes when possible. Anything built on leveldb can do quick and easy deletes with db.del(key), so as long as our log supports deletion then it's simple to say "if deletion is supported, delete, otherwise rebuild".