[OTR-dev] OTR version 4 Draft #2

[Sofia]

Hey!

> In either case, designing the current API to anticipate one of these
> compromises would almost certainly be a mistake for these reasons and
> also the aforementioned complexity issue. Getting OTRv4 out the door
> and into users' hands soon is far more important.

Yes, completely agree. We are absolutely not doing this. It was just an
idea of something to would be nice to have on the future.

Thanks!

-- 
Sofía Celi (aka cherenkov)
@claucece / @cherenkov_d
EF74 1A5F 5692 E56F 14F6  243C 3992 6144 F89D 996F