@christianbundy what about set the content to an object of a specific type, like {"type":"deleted"} and add a property to the msg object like "deleted":true. Then it should not choke up client code, but would still be distinguishable as a deleted message. What do you mean by peering errors?