pibara-utopian / asyncsteem Goto Github PK

In order to field test the 0.5 version and see if everything runs stable and reliably, a port of the @pibarabot Watching The Watchers scripts should provide a good opportunity to do just that.

This port won't do any posting yet, due to signing being unimplemented.

The bot should be enhanced in the way that:

• The current MVVP metric is replaced by an rshares based metric
• It distinguished between flagging and attenuation of upvotes.

Either implement a separate Python3 version of asyncsteem or write one version that is cross python-version compatible

Need to implement a setup.py for installation and make sure it gets the dependencies right.

• Completely port *Watching The Watchers to asyncsteem
• Completely port @croupierbot to asyncsteem
• Completely port the steempersist bot collection to asyncsteem

One of the goals of asyncsteem is the possibility to use it for away-bots that aim to contribute to the platform by using excess voting strength for good.

A few examples:

• Countering accidental upvotes to comments of known comment bots by post authors.
• Attenuating reputation destroying downvotes.
• Countering false downvotes.

Given that other accounts may be running similar bots, and given the fact that there are no mutexes to avoid two bots (or more) from thinking they are doing measured attenuation when together they do not, other measures are needed to avoid overshooting targets.

For this, we need to implement a network technology known as Carrier Sense Multiple Access Colission Detect. Before we vote, we check if other bots didn't attenuate already After making an attenuative up or down-vote we check again. If a bot voted in the same direction we did, just before we did, we retract our vote, re-calculate, and if needed start over at lower strength.

All public classes and methods should be well documented.

@dhimmel: " It was a bit hard to search the figure to find my username. Have you considered exporting the detailed image as a PDF so we could search the text or even better using an interactive network layout?"

https://steemit.com/stats/@pibarabot/flag-war-stats-for-posts-made-on-2018-06-13

In order to perform signed operations, such as votes, down-votes, posts and comments, the asyncsteem library should implement an operation signing facility.

When running the test code for asyncsteem/jsonrpc.py, ocassionaly an 'Unhandled error in Deferred' without a stacktrace is logged to the twisted logger.

Need to figure out what these unhandled errors are and implement proper error handling.

The code base currently is commented rather minimally. Need to add a lot more comments to explain the code logic.

tls_process_server_certificate', 'certificate verify failed')]>]". 'api.steemit.com'
2019-05-02T22:50:14-1000 [asyncsteem#error] Error on HTTPS POST : 'ResponseNeverReceived' : "[<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]>]". 'api.steemit.com'
2019-05-02T22:50:14-1000 [asyncsteem#error] Error on HTTPS POST : 'ResponseNeverReceived' : "[<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]>]". 'api.steemit.com'
2019-05-02T22:50:15-1000 [asyncsteem#error] Error on HTTPS POST : 'ResponseNeverReceived' : "[<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]>]". 'api.steemit.com'
2019-05-02T22:50:15-1000 [asyncsteem#error] Error on HTTPS POST : 'ResponseNeverReceived' : "[<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]>]". 'api.steemit.com'
2019-05-02T22:50:15-1000 [asyncsteem#error] Error on HTTPS POST : 'ResponseNeverReceived' : "[<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]>]". 'api.steemit.com'
2019-05-02T22:50:15-1000 [asyncsteem#error] Error on HTTPS POST : 'ResponseNeverReceived' : "[<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]>]". 'api.steemit.com'
2019-05-02T22:50:16-1000 [asyncsteem#error] Error on HTTPS POST : 'ResponseNeverReceived' : "[<twisted.python.failure.Failure OpenSSL.SSL.Error: [('SSL routines', 'tls_process_server_certificate', 'certificate verify failed')]>]". 'api.steemit.com'
2019-05-02T22:50:16-1000 [asyncsteem#error] Error on HTTPS POST : 'ResponseNeverReceived' : '[<twisted.python.failure.Failure twisted.internet.error.ConnectionLost: Connection to the other side was lost in a non-clean fashion: Connection lost.>]'. 'api.steemit.com'

I been trying to get this to work, here is my log. What is easiest way to deal with this twisted certificate tls_process_server_certificate I have ssl, not sure must be some little step I need to investigate from here. If anyone knows please let me know. I will post answer if/when I figure out.
I think I just need to add the code! of course!)

Python 2.7.16 (default, Mar 4 2019, 09:02:22)
[GCC 4.2.1 Compatible Apple LLVM 10.0.0 (clang-1000.11.45.5)] on darwin
Type "help", "copyright", "credits" or "license" for more information.

from OpenSSL import SSL
from OpenSSL import SSL
from twisted.internet import ssl, reactor

https://steemit.com/utopian-io/@coininstant/re-mattockfs-re-mattockfs-writing-an-asynchronous-steem-web-app-in-python-with-asyncsteem-20190503t040807000z

It should be possible to stop a bot, then start it up again later, making it pick up where it left off when it was stopped. To do this, we should implement a steempersist style persistance, but one that takes into account the asynchonous and paralel nature of asyncsteem.

Improve tests and terst code coverage of tests in order to maximize code coverage for tests.

We need to determine if we want the Python3 version to be Twisted or AsyncIO based.

Implement a simple gUI demo for a simple away-bot with a user interface in PyQt or CEFPython.

When creating a post, the option exists to set beneficiaries for the revenues from the post. This possibility seems to be a somewhat more complex version of the signed operation, so I created a separate issue for 0.8, so 0.7 can be released without this working.

An example of use for this functionality could be the @pibarabot Watching The Watchers bot donating 20% of post revenues to @freezepeach.