Detailed technical specification

[vitkabele]

I found this cli and your library recently. I want to use it to keep some secret keys for possibly a long time and it is convenient for me to keep the secrets written on paper.

This library seems to be good choice for my needs, however due to my expectation of possibly long term archivation of such a keys, I'd like to see some detailed technical description of the shares format, so that it would be possible to construct different program to combine the shares, even if the original one (this one) disappear from the internet and/or will not be maintained and it will be impossible to use in the future versions of rust/c etc...

[Huge]

Hi, I'm also interested in SSS future compatibility.
I started an experiment for a testing suite to compare this tool, http://point-at-infinity.org/ssss/ and Python's Cryptodome.Protocol.SecretSharing.Shamir , so far I only get results from the last one, where seems to be a limit of 16 bytes for the split message. From my study of the ssss mentioned, which is an older C implementation currently living in https://github.com/MrJoy/ssss I found it support upto "128 ASCII characters".
I'd like to make a proper evaluation, but currently I'm struggling financially, would you consider supporting the effort via https://www.bountysource.com/issues/89196848-detailed-technical-specification , @vitkabele ?