The task of interpreting profile.json as your personal information is handled by the Onename application, not by Blockstack. To Blockstack, profile.json is just an opaque JSON blob (and need not be a profile). Information that the profile.json file links is outside of Blockstack, and managed by Onename.
Nevertheless, we’re adding a generic data storage system to Blockstack in 0.14.1. You will be able to use it to store arbitrary data in a filesystem-like structure. However, applications will need to be designed to use it for backing up application-specific data (like avatar pictures).
Yeah, I know the difference (I guess :D). I mainly meant whether I can add for an avatar https://website.tld/some-avatar a backup https://another-website.tld//backup-location-for-avatar and specify this in my profile.json.
Is there a specification that would allow that? (Has to be somewhere in schema.org or something own, I guess)
Okay, cool! I definitely agree that it’s a good idea to have multiple copies of avatars, just as long as Onename knows how to use them. When we refactor Onename to run as a local application, we’ll add support for this.
Great idea @vsund! Would we also want to have optional hashes of the avatar data stored in the profile so apps can verify the integrity of the data the user intended to point to?