or as I said earlier, to make sure that there is a standard and testing a message that comes in if it's supported by the running instance of ssb. if not skip. I think this message object shouldn't be stopped from being saved in the database (as I could just have an outdated version of ssb), but it should be filtered out of any front-end as early in the stack as possible.