Now that we have #9, which allows us to verify a "signature profile" by providing a local path or piping to stdin, it occurred to me that it would be great to also be able to just provide the URL of a profile hosted online:
keyoxide https://codeberg.org/keyoxide/keyoxide-cli/raw/branch/main/test/signature-profile.asc
Then I thought: why not for keys, too?
keyoxide https://yarmo.eu/9F0048AC0B23301E1F77E994909F6BD6F80F485D.asc
Implementation-wise, I guess it would be necessary to fetch the content from the URL, detect whether it is a key or a signature, and then proceed accordingly.
This would be especially useful for "signature profiles" given there is no centralised mechanism for distributing them (which can be an advantage, in terms of privacy).
Now I think of it (though this should be an issue on keyoxide-web), we could support verification of "signature profiles" on the web with a link like:
https://keyoxide.org/?profile=[profile_url]
Now that we have #9, which allows us to verify a "signature profile" by providing a local path or piping to stdin, it occurred to me that it would be great to also be able to just provide the URL of a profile hosted online:
```
keyoxide https://codeberg.org/keyoxide/keyoxide-cli/raw/branch/main/test/signature-profile.asc
```
Then I thought: why not for keys, too?
```
keyoxide https://yarmo.eu/9F0048AC0B23301E1F77E994909F6BD6F80F485D.asc
```
Implementation-wise, I guess it would be necessary to fetch the content from the URL, detect whether it is a key or a signature, and then proceed accordingly.
This would be especially useful for "signature profiles" given there is no centralised mechanism for distributing them (which can be an advantage, in terms of privacy).
---
Now I think of it (though this should be an issue on keyoxide-web), we could support verification of "signature profiles" on the web with a link like:
```
https://keyoxide.org/?profile=[profile_url]
```