mesb1

For now it is working again, from this point, so let's see how it goes for the next day.

If possible there is a sense to add a bit more debug via --debug key as it is not clear on which side it was broken, between app and 3rd...

Looks like i have run into problem again. It happens about 3 hours ago, app stops working again: `./x -t "testing2"` `Failed to unmarshal response` Also it looks like this...

And now working again, tried 7 times before with no luck.

And same happens again. Do we have some limitations somewhere?

Oh, sounds sad. Did i get it right, this is whole limit across allthe users? I mean for example my limit was ended, and you also will be limited even...

Well, i assume there is a sense to add some limitation to the xcli then for local or server side. We can share 50 tweets across 10 users for 5...

If you ever decide to move for some paid options for this api we can try to continue streamer data posting.

By the way, is it possible to create xcli2 xcli3 xcliN app for twitterconnection for making it about 50 requests each?

> I will stop my autoposter for tracks and will use this for some specific things like just random posts sometimes from server. FYI: I have reordered my automation scripts...