Hello steemians
So, I've noticed many people with various duplicated contents on steemit lately. This is an issue I have observed lately while posting on the main site steemitdotcom. You get a transaction broadcast error when your post in actual sense has been published.
Perhaps the most frustrating of this occurrence is the case wherein your post is not published and all your text varnishes (with no draft copy as you would have expected). This had happened to me twice before and it wasn't any funny as I had to start the work all over again.I was only lucky I had an earlier draft which I could then build my post from again.
For me personally, I hate to see those duplicated contents but what do we have to do when we have to do while we hope this issue is fixed by the devs? Okay, so I have these points below I feel everyone should take note of while making a post.
After you have finished the composition of your post,
Ensure you copy the whole of the post before submitting
After publishing your post and getting a transaction broadcast error, check your blog to be sure if the post was published or not.
If your post was not published, you can then paste your copied draft for a repost.
I hope this guide was useful while hoping a solution comes soon for the bug.
I will take a screenshot of what I am talking about if it comes up while publishing this post.
img credz: pixabay.com
Nice, you got a 4.0% @minnowbooster upgoat, thanks to @dorth
Want a boost? Minnowbooster's got your back!
The @OriginalWorks bot has determined this post by @dorth to be original material and upvoted(2%) it!
To call @OriginalWorks, simply reply to any post with @originalworks or !originalworks in your message!
That is what i always do @dorth
Nice @tfame3865. I hate to see those duplicated posts really.
It usually gets published in the first try. Copy, cancel and refresh. It will be updated!!
Yeah... But there was an instance when instead of being published, everything just went away... That's the worst of the case.
Umm 😐 I never had that. It wasn’t just updating!
I had it. Although I'm forced to think it's browser dependent cos the two times it happened, it was while I was using Mozilla on my system. I was surprised too..