jordan
The way it normally works is: you encrypt a message with my public key _and then_ sign it, which gives the receiver proof of the person who sent it too....
I suppose it wouldn't be _too_ hard to tell if it was encrypted or signed first, although signed first sort of makes more sense now I come to think of...
Hi @j0hax, thanks for the suggestion. It would definitely be nice to add a derivation to Nixpkgs. I’ll certainly do that at some point in the near future. For now,...
Hi @j0hax, MR is open at https://github.com/NixOS/nixpkgs/pull/165488 - hopefully it'll be merged soon
Thanks for the report, I think this is related to the move to React Router v6. I'll try to reproduce and push up a fix today
Seems to be the other way round, I can reproduce this on v0.1.0 but not master. Can you confirm this is the case? If so, I'll release v0.1.1 today
Ah, makes sense. Good to know there's (likely) not broken code released. Fwiw, during development I usually run the frontend using `yarn start` under `chartered-frontend` with the `git` and `web`...
Don't think there's any cheap/elegant way of doing this at the moment, the way cargo informs us that a crate is from the same registry is passing `registry` as `null`...
Ah interesting, will do thanks
This is updated now, thanks @jszwedko