The biggest problem right now is that all the major frontends for Steem completely overwrite the json_metadata field when you use them to edit. If you wrote a post on chainBB.com, it will set one version of the meta data, but if you go edit that post on steemit.com it'll end up overwriting all of that JSON data with stuff that steemit.com wants. The app tag within the meta is specifically what I'm concerned about for the time being.
If anyone's got thoughts - I'd love to talk about it and potentially start a new thread.
I thought an 'edit' was actually a new post. If that's the case, then the original post and metadata are still intact.
They are new operations, but the
get_contentAPI call only returns the most recent iteration (with the overwrites).Ah ok. Sounds like steem(it) need to work on a json_metadata standard.
Yeah - I'm hoping we can raise some urgency on it as well. With SMTs partially focused on adoption by other sites, we need to make Steem itself multi site friendly for that to work :)
I'm playing around with the metadata field at the moment in my current project, and it seems you can add custom metadata and it is retained after edits on another front end. So there is at least that small positive in that you can set a duplicate "app" key (call it "application", say) and write and read from that on your front end.
The minute two of us start using
applicationinstead ofappthough - it'll start getting overwritten :DI'll call mine
application69..