SorteKanin
Jokes on you, I love the clumps of chocolate in milk with cocoa powder.
Yes. Describe it as best as you can and let the developer reach out to you if you want. A good maintainer will ask follow up questions for more specific stuff that you may not have provided at the start.
a bit of text you can send to them by whatever secure side channel you want down to handing them a flash drive
Normal non-technical people are never going to do this. It needs to be easy as clicking a button, otherwise it will never happen for them. Again, this is a neat technical solution but it completely forgets the human.
Yea in theory you wouldn’t need the password if you have the private key but here the key is only used for signing, maybe not for login. If it also needs to be backwards compatible. In any case, I don’t think user-held private keys is viable.
Sharing with trusted parties… I dunno, I think again it’s too technical and complicated to do it. And you’d need people on the platform you trust to already be there.
The only time I’ve ever needed a Mutex<()> so far with Rust is when I had to interop with a C library which itself was not thread safe (unprotected use of global variables), so I needed to lock the placeholder mutex each time I called one of the C functions.
Actually I think in this case you’re still better off using a Mutex with “data” inside. I’ve done this before. The idea is that you make a unit struct MyCFuncs
or whatever and then you only call the C functions from methods of that unit struct. Then you can only access those methods once you lock the Mutex and get the instance of the unit struct. It feel elegant to me.