RE: STEEMIT ATE THIS POST TWICE - Why Is Steemit Still Eating Votes, Comments And Posts? 50% Of My Submissions Are Deleting With No Draft Saved (Foul Language Ahead)
It has been no fun for me for about a week. Started posting again yesterday; it hasn't eaten one of my posts yet, but I use a "work log" (a LibreOffice document) to compose in, as a general rule.
It is constantly spinning while trying to upvote.
I think I found something:
It seems that the spinning behavior is worse when you're looking at a feed and left-click a link, which causes it to appear "above" the feed, and you can click outside of the white background to dismiss it and go back to the feed.
When I had done that, I upvoted two people who I see regularly, as well as your post, and it kept showing the "can only upvote every 3 seconds" (which was behind the post, grayed out in bottom left -- another UI issue). I clicked outside the white to go back to the feed, then I did a middle-click of your post to open it in a new tab.
Then I switched to the tab and saw that two of those upvotes had been recorded. I made the third, and then started writing this comment. Which I'll Ctrl+A Ctrl+C before I hit Tab Space, just in case.
I agree with you, having to take so many extra steps is madness. And is causing me to walk away -- just as I made a significant investment! :(
Good news though is I learned more about MinnowBooster delegating in the meantime.
"but I use a "work log" (a LibreOffice document) to compose in, as a general rule."
That's a good rule to follow.
"It seems that the spinning behavior is worse when you're looking at a feed and left-click a link, which causes it to appear "above" the feed"
I have noticed this as well. I've been opening comments into their own individual windows, but that is labor-intensive.
"Then I switched to the tab and saw that two of those upvotes had been recorded. I made the third, and then started writing this comment. "
Everything you describe here I've seen as well.
Agreed! "Labor-intensive" is what computers were fucking (sorry) created to solve!!1!eleven!1!!
I made a #steemgigs post about my thoughts to resolve this, earlier today:
https://steemit.com/steemgigs/@libertyteeth/steemgigs-idea-steemit-agent
"is what computers were fucking (sorry) created to solve!!1!eleven!1!!"
Haha, that's why I added the foul-language warning to the title! This type of stuff really sets me off...
Hey I found a solution to this crap today!
https://steemitstage.com/steemit/@libertyteeth/4oiiz7
Which I originally found here: https://steemitstage.com/steemitstage/@surpassinggoogle/let-s-help-steemit-devs-test-https-steemitstage-com
Any portal you use to the Steem block-chain would "fix" this issue, since the DDoS attacks target specific domains (www.steemit.com, etc.)