Jonathan Schleifer
Jonathan Schleifer
I think MUC and regular chat are a different story. I think it makes sense to enable it by default for regular chats, but not MUC. And maybe also adding...
A notification would not need to be permanent - I think it would be enough to show it when starting a new unencrypted chat or when switching from OMEMO to...
I think it would make sense to have a type like this in one of the reserved ext types.
From #128: > I think it's possible use a single type to display it though. I'm not sure about this. I think these might even be 3 different types in...
@ugorji Where did you edit it? In the first post? A diff would be nice, to see what changed. Or any kind of versioning. I think having a dst bit...
@ugorji This looks good. One question though: ``` 4 bytes: secs32 6 bytes: secs32 tz 8 bytes: secs32 nsecs 10 bytes: secs32 nsecs tz . 9 bytes: secs 0 11...
@ugorji Ah, I understand. Maybe it would make sense to have 3 types? time, time + nsec and time + nsec + tz.
@ugorji Well, I see a problem with appending a 0 that is basically just a wasted byte in a format that wants to be compact. If you want to be...
@ugorji Well, I don't see a reason to not have 3 different types for it, especially considering that in C those _are_ 3 completely different types.
Why can I only specify extra bytes for nanoseconds? What if I want 0 byte? Why is seconds optional? What about a way to denote it's not a date but...