There is an issue where the post written on Steemit cannot be immediately viewed.
The most inconvenient aspect on Steemit recently is the inability to immediately see the posts right after writing them. This applies not only to the posts I've written but also to those of other users; they cannot be viewed right away.
The link below is an example of a recently posted post.
https://steemit.com/tiktok/@justlookingout/your-instantly-monetized-tiktok-account
If you click on that link, you'll see an error page like the one below.
 |
|---|
It was a temporary issue, and now there is no problem accessing the URL. However, this problem still occasionally occurs.
However, when you access the link below, which is in JSON format of the same article, the data is displayed correctly. It is in the form where only the .json extension is added to the end of the above URL.
https://steemit.com/tiktok/@justlookingout/your-instantly-monetized-tiktok-account.json
 |
|---|
After analyzing the steemit/condenser code, we found that the two links are calling different APIs.
In general, the detail page of the post we are viewing is using the bridge.get_discussion API. We tried calling it ourselves and saw that the result was empty, as shown below.
On the other hand, the json page is using the condenser_api.get_content API, and when I call it, the data is returned normally as shown below.
Finally, I tried calling the tags_api.get_discussion API from the steem developers documentation, but I got an error message like below.
This error appears to be caused by the fact that it hasn't been cached yet.
I was hoping to troubleshoot the error myself, but analyzing the cause is the best I can do at this point.
Posted through the ECblog app (https://blog.etain.club)
The permlink is wrong. This is the right one, which is also reachable:
your-instantly-monetized-tiktok-account
The condenser uses the request
bridge.get_discussionwhich responded by the hivemind node. Cou can see this in your screenshot.The
condenser_apiis responded by the full node. I think therefore you got a right response.At the moment I don't have an issue to open the article. Maybe it was just a temporary problem.
To reduce the hivemind accesses there are some cache strategies. I could imagine that there might have been settings on the cache interval or something similar.
My hivemind node works fine and give the right response. Unfortunately, it is still not possible to configure another node in the settings so that every call from the Condenster is sent to the Steemit node. Only when this is implemented can the number of accesses to the Steemit servers be effectively reduced.
There were some typos in the post I wrote. Thank you for pointing them out. Also, thank you for providing a detailed response.
I believe it might be a temporary issue. However, it seems to be occurring very frequently. So, I have tried to analyze the cause, but it appears to be a problem that I find difficult to resolve.
情報ありがとうございます。
おそらく、以下のようにNODEの違いがあるようです。
Right, but it is bridge.get_discussion.
Oh, there seems to be a difference in NODE. Thank you for letting me know.
!thumbup
Wow, thank you for the thumb-up!
Hello @anpigon! You are Remarkable!
command: !thumbup is powered by witness @justyy and his contributions are: https://steemyy.com
More commands are coming!