Thanks for the review.

> do you think yours is/will be more reliable than e.g. the stream function used in steem-python?

I have a couple workarounds to stream blocks on my old steem-python scripts. I didn't wanted to implement these into lightsteem blindly.

Currently, I can not say lightsteem is more robust than their competitors, but it will be. I switched some of my scripts and waiting for them to crash. I will apply the workarounds after that. 

One thing I remember that the get_dynamic_global_properties sometimes returns null. There are a couple of cases like that. I will decide the best way when I encounter them, and apply it. :)

Regarding docstrings, I am not a believer. Not because the docstrings are bad, it's a good thing but it needs to be used perfectly.

Example: 

```
def hello(person):
	```
	@param person string
	```
   print("hello", person)
```

This is our initial function. Then requirements change, and we change the function.

```
def hello(people):
	```
	@param person string
	```
	for person in people:
		print("hello", person)
```


We have quickly updated the code since we face with deadlines but forgot to update the docstring.

That makes the docstring and documentation unreliable. And once the docstring is unreliable (even %99 is up to date), it's worthless. (There is no "person" argument anymore and it's not a string.)

And I can say, this happens a lot. Even in large codebases with well-established projects.

*thanks for catching the typo. Fixing asap. :)*

Thank you for your review, @amosbastian!

So far this week you've reviewed 1 contributions. Keep up the good work!