You are viewing a single comment's thread from:
RE: [STEEM DIP] Development Progress Report #2
I have two questions regarding the comments and the draft features.
Did you guys try to load the comments (when possible) after the content being scrolled? Maybe using lazy loading to make the user experience smoother.
Couldn’t be there a better solution for drafts? Did you guys thought about using the blockchain directly? I presume that most of users would have been happy to start a draft on phone and continue on another device.
I guess the draft can be a comment using the same permlink and be edited at each refresh. Or even in the user profile as a metadata (without erasing the existent infos obviously).
Overall it’s a good work and the templates looks pretty nice.
We appreciate your comments and feedback, and we hope to answer your questions as follows.
As shown in the image above, the development of the loading comments function was developed in a way that separates the loading of posts and loading of comments, not the lazy loading method from the beginning. It seems that it will depend on the person using it as to which method will provide a better ux. If there are more feedbacks that the lazy loading method is better, I think we can change it.
First of all, we agree with you. Steemit Team's DB was not available, so we thought about providing our DB, but this has problems in terms of the completeness or sustainability of the service. And the method of storing drafts as metadata in user profiles has problems in that user drafts are published before they are published, and the storage capacity is limited. We left many options open and thought a lot, but we had no choice but to choose the method with the least potential problems in the future.
Steem DIP is now in its first step, and I think we need to continue thinking together about how it can be improved in a better way. Thank you very much for your thoughts and thoughts on a better solution!
Hi @upvu.witness, this looks great and I'm looking forward to trying these new features.
Similar to @future.witness - One idea that could work for saving a draft on the blockchain is to save it within the json_metadata of the user's very first post (apologies if this is the same idea as future.witness). Since the 1st post will always be the first post, then it'll be easy to retrieve and you won't need to record where the drafts are saved anywhere - it'll always be within that user's profile. Since the user's logged in (or needs to be logged in), it's then portable to other devices.
I'm also curious about how the drafts are saved - You mention it's in the user's browser, is this through the use of cookies?