Agree with you totally and I think that it might be worth discussing this type of data-entity as its entirely own new-service. It really depends how much people use it but you're familiar with the updating issue we were discussing the other day, maybe having a different service (rather than the generic "data") service that is tailored for this use case from both a design and cost perspective would be better suited? I know this is getting into details you and I were chatting about but I wanted to share that with the community to get their thoughts.

Also the encryption piece is key- I want to increase the priority of multi-sig encryption using Syscoin keys. What this means is essentially you could encrypt the data and only you could decrypt (w/ SYS keys) - or you could use multisig encryption which still has some design nuances to be worked out but it would allow you to encrypt your data so that instead of only "you" being able to decrypt it, you, Joe, and Sue could call decrypt using SYS keys via SYS multisig encryption.

And I agree with you re: Syscore (this is a port of Bitcore to Syscoin, it is a full blockchain client built using only Javascript; We've ported the core send/receive stuff into SYS but the SYS services haven't been ported into JS yet, on our list of todos).

Interested on what people think about this (storing data using data service or should there be a new service in Syscoin specifically for social data? Also priority of encryption / community demand for multisig encryption?)