Also I think the printable shares, besides the QR, would be nice to have the HEX representation of the share’s code. So it is up to the final users if they want to rely on the cam or just type manually the shares’ codes.
During a recovery process I would be forced to use HyperBacked/SuperBacked again?
or I could use any standard QR-scanner + any standard SSS tool?
In other words, is HyperBacked/SuperBacked somehow just a wrapper of standard tools? or are they very opinionated?
People winging something out over the WE should also be taken with a grain of salt tho.
Usually, the hard parts are not the 80% that can be done with an LLM but more of the rest.
Doing something quick and fast doesn’t guarantee it’s done right.
True that maybe having that closed-source is maybe not the best but it’s not like a drop-in replacement either.
Be careful with quickly released software (that are heavily marketed on socials) from now on.
If we do not need the encryption passphrase, I think it is better to use directly the archaic: ssss-split and sss-combine, and if we want the qr code enhancement, we can use standard: qrencode and zbarcam(but they are an addition, we should have also the code shares in the share PDF).
I think hyperbacked/superbacked is a cool tool but it could complicate the recovery process, because they are not standard tools and prob they are a bit opinionated. Maybe after 20 years I need to recover from these shares, but I can’t find them, also their generated shares’ codes do not work directly with ssss-combine.
All credits to Sun Knudsen, I heard for first time about SSS many years ago, but he was the first to attempt to build a easy-to-use tool.