They are new operations, but the get_content API call only returns the most recent iteration (with the overwrites).
You are viewing a single comment's thread from:
They are new operations, but the get_content API 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..