@christianbundy since is the offset of the last record added to the log. In different flumeviews this is a different thing. In flumelog-offset and flumelog-aligned-offset, it's the byte offset in the log file where that record starts. in flumelog-memory it's the integer index of that record, in flumelog-level it's the local timestamp when that record was added, which is used as the key.

Following that logic, deleting a record shouldn't change since.

hmm, a way simpler way than streaming deletes to the views, would be to filter out deletes from the views when querying them. views such as flumeview-level call to the log to get the message - if it's not there, drop it, done.

aggregation views like flumeview-reduce would need to be rebuilt, though.

@rabble great, I'm on board with deleting blobs, including subscription based moderation on how that happens exactly. It still has some of the same problems, but it feels like a different level since the expectation for blobs is not as high as messages.