create account

Sorry for the mess... by jpphotography

View this thread on
· @jpphotography · (edited)
Sorry for the mess...
Tl;dr: Yesterday, my post scheduler went crazy. I am sorry for the ~~double~~  septuple posts, my script has been fired.

Some days I am working 12-14 hours on TravelFeed while on others I am travelling and don't even touch my laptop, this is why post scheduling is awesome for me in order to share my photos regularly. As a developer, I am not using Steempeak or Steemauto to schedule my posts though, but my own script that has some cool features: It enables me to write my post from Lightroom, the software I use for managing and editing my photos, and to schedule not just posts, but also comments to participate in the awesome travel photo contests by @czechglobalhosts. 

Unfortunately, the recent hardfork caused some unwanted behaviour. At the time when I developed the post scheduler, I naively believed that an immutable blockchain would mean reliable data, so instead of recording my posts locally, my script checked the contest posts by @czechglobalhosts for any existing comments by me to avoid double posting, which had the added advantage that it would detect any manual participation by me as well. Since the hard fork, the function `get_replies` in beem, the Python library I use, that is responsible for getting the comments of a post was having issues. I am currently using the pre-release version of beem and when testing everything worked fine, but it seems that I ended up with another node yesterday that was returning empty data. Lesson learned: The blockchain may be immutable, but Steem nodes are a mess and should not be relied on.

On top of that, I did not follow the changelogs of beem closely enough to notice that the behaviour for existing posts must have changed recently. Before, when posting with an existing title/permlink, beem would update the old post, preventing accidental double posts but causing an often unwanted behaviour. Now, beem posts are using a new permlink instead, resulting in a new post being created each time. I did not realise that this failsafe was no longer working.

To make it worse, my automations do not only post on Steem, but also share my photo and Steem(it) post to several other social networks. I want to thank everyone who did not unfollow me immediately but alerted me of my account posting like crazy and will now start answering messages and removing the double posts.

I have downvoted my double posts, feel free to do the same to remove rewards.
👍  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
properties (23)
json_metadata"{"EXIF":{"ISO":"100","ExposureTime":"1\/320s","FocalLength":"24mm","LensModel":"Sigma ART 18-35 mm f\/1.8","FNumber":"f\/8.0","CameraModel":"Nikon D5500"},"app":"steempeak\/1.15.5","community":"busy","users":["czechglobalhosts.","czechglobalhosts"],"coordinates":"None,None","tags":["photography"],"format":"markdown","hidden":true,"links":["\/@czechglobalhosts","\/@czechglobalhosts"]}"
created2019-09-05 13:04:18
last_update2019-09-06 07:05:33
last_payout2019-09-12 13:04:18
cashout_time1969-12-31 23:59:59
total_payout_value0.207 SBD
curator_payout_value0.200 SBD
pending_payout_value0.000 SBD
promoted0.000 SBD
root_title"Sorry for the mess..."
max_accepted_payout1,000,000.000 SBD
vote details (37)
@steemcleaners ·
Copying and pasting previous posts could be seen as spam when:

- Frequently reposting the same content without additional information or changes
- Reposting content within the same payout window

If you believe this comment is in error, please contact us in [#disputes on Discord](
👍  , , , , , , , , ,
properties (23)
created2019-09-05 22:28:57
last_update2019-09-05 22:28:57
last_payout2019-09-12 22:28:57
cashout_time1969-12-31 23:59:59
total_payout_value0.181 SBD
curator_payout_value0.180 SBD
pending_payout_value0.000 SBD
promoted0.000 SBD
root_title"Sorry for the mess..."
max_accepted_payout1,000,000.000 SBD
vote details (10)