I made a bootable live USB image that has the Inkan Management Utility pre-installed. This is meant to provide an airgapped environment for signing delegations and revocations of signing authority between key pairs, and for identity creation.
The OS is expected to be amnesic across reboots and networking is disabled. I added QR codes to conveniently transfer keys and signed declarations to an online system. You can also configure persistent storage to keep the keys that secure your identity right on that USB.
I still look at NIPs for ideas, but I'm not overly concerned about conforming to them when it's not convenient. If I did I wouldn't get much work done. I do try to engage in protocol discussions but the experts are mostly not very responsive, which leaves one without proof that there is actual expertise there. If one community moves too slowly, I guess it may be better to divide one's time and talk to a different one, or just to focus on the product.
Thanks, that's what I figured. I'm currently just using a non-networked version of Tails to generate the master key, and then put an encrypted version of it on a USB. The master key most likely will have to be used only once, so it's easy to store copies in, say, a safe deposit box. There are probably better ways to do the airgapped operations that my method requires. I'll look out for updates on what you're doing.
What makes vicious characters interesting is maybe the virtuous characteristics they need to have to be effective in the pursuit of their vices. Or maybe it's considering why their vicious goals seem good and worthy of pursuit to them.