Currently the main keys endpoint returns keys in a format that is suitable for use in an authorized_keys file without any parsing or modification.
This is a key features of the keys project and should be kept as the default behaviour.
However if the caller requests content-type: html they should instead receive the content in html. This will be a lot easier to view in the browser and can later support features like automatically copying keys to clipboard and clicking on tags to filter by them etc.
Attention should be given to still keeping the container as light as possible.
This issue can be completed in the following parts to help keep PRs small:
Currently the main keys endpoint returns keys in a format that is suitable for use in an authorized_keys file without any parsing or modification.
This is a key features of the keys project and should be kept as the default behaviour.
However if the caller requests content-type: html they should instead receive the content in html. This will be a lot easier to view in the browser and can later support features like automatically copying keys to clipboard and clicking on tags to filter by them etc.
Attention should be given to still keeping the container as light as possible.
This issue can be completed in the following parts to help keep PRs small: