Help me brainstorm some ideas!

I've already read a lot of "already done", "there are a bunch out there", "lots of them floating around", but I'll do it anyways:

I'm going to create a Bot platform (Not single bots) which will allow the user to load scripts in order to enable macros on the most popular social media sites. As I wrote in my Journey Thread the main scripts would be auto-posters and auto-whatevers among other things... but which other things?
I know this is the programming forum, and I already know the technology I am going to use, but I really want to know which are the current risks, limitations and other threats that the user may encounter when using macros for creating a big amount of posts in sites like Reddit, Pinterest, Tumblr etc.
It would be nice to know how people are handling OCR for Captchas too!

This bots/macros will be able to scrape data (text, images..) and post is anywhere a normal person can without blocking the Browser or locking the mouse. I may be able to do both Windows and Linux versions. I'm planning on starting development a couple of weeks form today.

I would love to hear your opinions and please avoid discouraging me, I you think I'm going to fail: at least let me try

I suppose this will be a more advanced topic as we get a little into product development.

If this is correct, then I think we will no longer be discussing how to code this function and that.

For product development, personally, for me, there are 2 major factors I would consider
- satisfy the practical objective
- extensible

Satisfy practical objective means you develop a product that user wants to use.
The problem with technical people is we are too excited in the technology and implement something only we know the "hidden" power command.
Sometime, I even hear programmer saying, "The user is not so sophisticated to understand this"
To me, no function is good, unless the user can use it.

Extensible mean you can add-on feature as you go.
You mentioned you want an "auto-posters and auto-whatevers among other things".
So, the important thing to design now is to make sure when you think of the next auto-whatevers, your platform can handle it.
I don't think you can think of an exhaustive list of auto-whatevers at this point of time.
But you will need your platform to be flexible to cater for auto-whatevers.

Something like android, you can use whatever launchers as you wish, but you can't really think of every single idea of how a launcher should work.
Even G can't make a launcher that has every imaginable function in the world, so, I don't suggest you try to. But, you should try to make a platform as flexible.

Or, if you know Tomcat, the server is started through loading of a config file, which means if you don't like a certain part of it, you can easily use your own implementation and swap it in with a config change.

This, a lot of time, means carefully thinking and defining interfaces.

Just my 2 cents.

Loved you input mypmmail, thanks! I'll check out several products available here in the forum to understand a little better how can I apply the principles you just mentioned.