A prosperous 2021 to all. Let's dive into some Keyoxide news.
## Signature profiles
The Keyoxide web client just got updated to [2.4.0](https://codeberg.org/keyoxide/web/releases/tag/2.4.0) which
introduced a few minor bug fixes as well as a robots.txt and noindex meta tags.
The most exciting new feature in this release is the support for "signature profiles", a new way of creating
decentralized profiles that is both simpler to generate and solves a few drawbacks that come with the traditional
method of storing identity claims as notations in cryptographic keys.
From the newly added [signature profiles guide](https://keyoxide.org/guides/signature-profiles):
> Storing claims inside the key as notations is a powerful method. Wherever the public key goes, so go the identity claims. This allows one to use the existing vast network of key sharing tools to also share these identity claims.
> There are drawbacks to this: you lose granularity. You cannot pick and choose the claims you want to send to certain people or use for certain purposes. There is also the possibility that notations in keys could be scraped as the keys are publicly available.
> Putting (certain) claims in a signature profile solves both drawbacks. You can choose which claims to be associated with each other and you can choose which persons can see this by only sending it to them. You can even encrypt the signature profile! Since the signature profile is not publicly available (unless you make it so), there is no possibility to scrape the contents of it.
> Note that there is one catch: the person you send it to could publish it. Only send claims you wish to keep secret to people you trust!
### What does a signature profile look like?
Here's an example:
-----BEGIN PGP SIGNED MESSAGE-----
Hey there! Here's a signature profile with proofs related to the DOIP project (https://doip.rocks).