{"type":"rich","version":"1.0","title":"William Casarin [ARCHIVE] wrote","author_name":"William Casarin [ARCHIVE] (npub1d7…93exj)","author_url":"https://yabu.me/npub1d7e068ud72v0au6xf53qvek44eccfhlgnhzuclf6za6hnxrvx89sc93exj","provider_name":"njump","provider_url":"https://yabu.me","html":"📅 Original date posted:2018-06-27\n📝 Original message:Hey Andrew,\n\nIf I'm reading the spec right: the way it is designed right now, you\ncould create hundreds of thousands of zero bytes in the input or output\nkey-value arrays. As far as I can tell this would be considered valid,\nas it is simply a large array of empty dictionaries. Is this right? I'm\nworried about buffer overflows in cases where someone sends a large blob\nof zeros to an unsuspecting implementation.\n\n\nAlso, the extensibility section reads:\n\n\u003e Additional key-value maps with different types for the key-value pairs\n\u003e can be added on to the end of the format.\n\n\"different types for the key-value pairs\", is this referring to new\ntypes beyond the current global, input and output types?\n\n\u003e The number of each map that follows must be specified in the globals\n\u003e section\n\nIs this out of date? Since there is only one type in the global section\nnow (tx).\n\n\u003e so that parsers will know when to use different definitions of the\n\u003e data types\n\nI'm not sure what this means.\n\n\nThanks!\n\nWill\n\n\n--\nhttps://jb55.com"}