Ok, let me read one of your posts... > Ultimately, in the pursuit of simplicity, a flag octet would be avoided, as all my thinking would leave half of it unuse

Ok, let me read one of your posts... > Ultimately, in the pursuit of simplicity, a flag octet would be avoided, as all my thinking would leave half of it unused and that I find poor, and so the final format is as follows: sixteen octets indicate the IPv4 or IPv6 address, with all zeroes indicating a system action; three octets represent the time, likely with fifteen bits representing the year as an integer and nine bits representing the day within that year; an octet has its top two bits determine if the request successfully completed and if the selector ended properly, with the latter six being used for a length of the only variable-length component, the selector itself. Holy run-on sentence, Batman. You have two problems, the presentation of the topics aren't all that engaging, and your writing style could use some improvement. As a writer myself, I have to wonder how many revisions that went through. I need at least three drafts with days between them before I publish anything substantial. Examples of real life applications might make it more interesting as well -- a lot of the drama of HN stories are where the design didn't quite work in the implementation.