Pretty smart
I see you used the API from developer.twitter.com that's why you found it very limited. If you go through a third-party application it becomes much less restrictive.
For example, you could write 100 tweets, spin the text 10 times to have 1000 tweets, upload all of them in a WordPress database that will auto-post on a regular basis, you will see much less restrictions.
And yeah, Twitter improved a lot to detect the spams over the years. About the rate-limit...
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FJgUZWQh.png&t=663&c=okFi5oQIsk_xKQ)
But as you surely know, it's a case by case depending on the account used
I see you used the API from developer.twitter.com that's why you found it very limited. If you go through a third-party application it becomes much less restrictive.
For example, you could write 100 tweets, spin the text 10 times to have 1000 tweets, upload all of them in a WordPress database that will auto-post on a regular basis, you will see much less restrictions.
And yeah, Twitter improved a lot to detect the spams over the years. About the rate-limit...
![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2FJgUZWQh.png&t=663&c=okFi5oQIsk_xKQ)
But as you surely know, it's a case by case depending on the account used
Yes, I am currently looking at TWINT etc to get around rate limits.
Right now I'm actually using AWS for the backend. I love the scalability of using microservices for everything. The computing, databases, notification system, REST api, all handled through AWS.