META Text Control Byte Reconfiguration

Reconfiguring the Control Byte on META to discard the bitmap sequence and instead use a 4-bit numerical and sequential values 1-15 will allow for a much KISS friendly approach to Meta Text and also allows the expansion of Meta Text to up to 195 UTF-8 encoded characters. See discussion on the M17 Discord for more info. The current configuration uses two sets of bitmaps that don't match in a logical sense and reading them can be confusing.

See Items below, for example:

Control Len: 195; X: 211; K: 195; Meta Type: 00; Meta Text: this is a really long m17 meta text that can know hold up to 195 UTF-8 encoded characters blah blah blah xxxxxxyyyyyyyyyyyzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
 Meta Payload(01): F174686973206973206120726561
 Meta Payload(02): F26C6C79206C6F6E67206D313720
 Meta Payload(03): F36D657461207465787420746861
 Meta Payload(04): F4742063616E206B6E6F7720686F
 Meta Payload(05): F56C6420757020746F2031393520
 Meta Payload(06): F65554462D3820656E636F646564
 Meta Payload(07): F720636861726163746572732062
 Meta Payload(08): F86C616820626C616820626C6168
 Meta Payload(09): F920787878787878797979797979
 Meta Payload(10): FA79797979797A7A7A7A7A7A7A7A
 Meta Payload(11): FB7A7A7A7A7A7A7A7A7A7A7A7A7A
 Meta Payload(12): FC7A7A7A7A7A7A7A7A7A7A7A7A7A
 Meta Payload(13): FD7A7A7A7A7A7A7A7A7A7A7A7A7A
 Meta Payload(14): FE7A7A7A7A7A7A7A7A7A7A7A7A7A
 Meta Payload(15): FF7A7A7A7A7A7A7A7A7A7A7A7A7A

really_long_m17_meta_text.txt

Can't we start counting from 0? For 16 chunks, the first byte would be 0xF0, 0xF1, ..., 0xFE, 0xFF.

~Yeah, I suppose you could start counting at zero, and that would add an additional 13 UTF-8 encoded characters, bringing the total up to 208.~

No, actually, because 0x00 would be the starting byte for a singular payload, so it breaks, got to start at 0x11.

You are right, I realized that too late :)