>>> Can we propose a patch to document them? Don't want to get bitten by this
>>> suddenly changing...
>>
>> I can certainly propose something on their mailinglist, but I unfortunately
>> wouldn't get my hopes up too high as NSS and documentation aren't exactly
>> best
>> friends (the in-tree docs doesn't cover the API and Mozilla recently removed
>> most of the online docs in their neverending developer site reorg).
>
> Kinda makes me question the wisdom of starting to depend on NSS. When openssl
> docs are vastly outshining a library's, that library really should start to
> ask itself some hard questions.
Sadly, there is that. While this is not a new problem, Mozilla has been making
some very weird decisions around NSS governance as of late. Another data point
is the below thread from libcurl:
https://curl.se/mail/lib-2022-01/0120.html
--
Daniel Gustafsson https://vmware.com/
