You are viewing a single comment's thread from:
RE: Bookmarks for Steemit – Step 1: Hivemind Update
That's a good thing.
To avoid reinventing the wheel, it would be a good idea to document the custom_json we create.
That's a good thing.
To avoid reinventing the wheel, it would be a good idea to document the custom_json we create.
What do you mean with "we"? Do you mean a documentation about all custom_json operations?
We've discussed this before. Usually, the developer creates a special operation for their app to store data on the chain. Such special operations cannot usually be reused for other apps.
Documentation would be useful for cross-app operations (like the bookmark ops). I don't know of any overview of this either. You can find a few hints here:
Thank you so much for the good information. I will take note. I agree that custom_json is generally difficult to reuse. However, my ideal idea is, ‘If we make the usage of custom_json into a protocol, wouldn’t it be possible to share it with other developers?’ I will personally proceed with the project with custom_json and then share the results.
And 'we' are the people who use custom_json, and documenting and sharing it is just an idea for now.
That's right, I see it the same way. That's why I shared and documented my operation. I also want others to be able to use this and integrate it into their apps.
I think that's good. Have you made anything public about this yet? That would interest me.
Thank you very much for your comments !finanzbot 5 %.
Maybe you can also support me as a witness with your vote.