introduce the ATOM type instead BOOLNULL as for https://github.com/ssbc/bipf-spec/pull/3 but with 64bit uint and "trimmed" encoding of int introduced by tinySSB. This does not require current implementation to be modified if they do not want to benefit from this extension of meaning.
This proposal contains 2 changes:
introduce the ATOM type instead BOOLNULL as for https://github.com/ssbc/bipf-spec/pull/3 but with 64bit uint and "trimmed" encoding of int introduced by tinySSB. This does not require current implementation to be modified if they do not want to benefit from this extension of meaning.
specify that INT val is a 64 bits signed integer . Note that today implementations of tinySSB are using 32 bits int. This change do not require them to be modified immediately. And modification if straightforward. Meanwhile I think it is important to make the format more future proof. As it is used in SSB for the timestamp encoding, we are subject to the 2038 Problem https://en.wikipedia.org/wiki/Year_2038_problem#:~:text=Consequently%2C%20if%20a%20signed%2032,on%20Tuesday%2C%2019%20January%202038.