- Dec 16, 2020
- Reaction score
What's the best way to manage hundreds of Twitter accounts without them being suspended?
Not always the best way, yet people seem to preach "custom bot" is the best, but I doubt they have actually gone that route.Use good custom made bot which masks all footprints and connect accounts with fresh 4G proxies.
Not always the best way, yet people seem to preach "custom bot" is the best, but I doubt they have actually gone that route.
Yes there can be benefits to a custom bot, but also drawbacks.
1) The dev needs to know the domain they are writing a bot for. the tricks the site pulls to detect bots. These are not apparent straight away, but you get to know them with time. A custom bot dev is never going to find these
2) Testing. You will be the tester, sure the dev will find the main bugs, but the little edge cases, you will be finding these (or worse you won't). With a public program, there are many more users finding these things out
3) Sites change, you will always be reacting to changes breaking the code. Similar to (2) more users can find the changes quicker and updates put out before 99% of people realise there was a breaking change
4) Want a new feature, try and contact the dev and hope they are not busy they start discussing cost
5) found a bug, try and contact the dev and discuss who is going to pay for it
6) The idea that a custom bot has less footprints assumes that a developer who is not working on the domain, will write a cleaner bot, with less footprints than a developer who is working on automating that domain all day every day is false. Not all, more in more cases than not custom bots have more glaring footprints than any public bot
7) cost, you are paying for every line of code. Every update, every new feature, this can get very expensive. A public bot is paid for by all users.
8) as some one requesting a bot, probably you don't know what you want, you have no experience managing a software project, you underestimate the cost and time and this will lead to issues with the dev
Of course it is not all negative. For instance, a custom bot will work EXACTLY as you want, with your flow. If you want to run high numbers of accounts 10000+ then a custom bot will be designed for that. Most public bots are designed for the average user, who has between 1-100 accounts, that is 99% of users. So things are not as smooth in public bots for 10k accounts. Perhaps you have have specific needs that you MUST have, again a public bot is the only way. Maybe you do find a skilled domain developer who is always available, charges a fair price, will fix anything quickly without issue, will make updates and new features cheaply and without issue. But, lets be honest, that is not usually the case.
In my experience of custom work, customers wildly under estiamte the cost, thinking a custom bot can be developed for about the same price of x2 of a similar public bot, it just cannot, without cutting all corners. Equally, I've yet to meet a dev who can estimate how long a green project will take.
All the above can be ignored if the dev already has work in the domain, perhaps got a bot codebase ready, but then the benefits of a "no footprint" bot (if that was true anyway) is nullified because they are just building the same codebase and selling it to you
You can use any Antidetect browser for this as well, don't forget about proxiesI have managed 30+ Twitter account at a time. I have created 30 Google Chrome browsers and login each account in each browser. So all accounts are okay now and easy to use for me. This way is the only safest way. You can try if you want.