punkinhead
Regular Member
- Feb 19, 2015
- 450
- 37
Requirements:
1) Lots of tiny virtual machies (each with own IP) that need proxies
2) Need full anonymity AND stealth, so something like Tor is out as it leaves it's own fingerprint
3) Each needs only 1 proxy at a time as it is being used for a particular social media profile
4) I'm assuming proxy should not switch during session as this would not be usual behavior for a given social media user.
5) Some profiles are one-offs with sessions lasting from several minutes to half a day. Others are persistent and will log in again as same profile over a period of several months, and will need access to the same IP to do so.
6) I'm assuming this may require two systems: One for shorter sessions that allows per-session switching (cannot switch on timer mid-session), and another for the longer term use where I have reserved private proxy that I switch as needed every few months.
7) Use involves media streaming, so I'm guessing all the residential backconnect systems that charge by bandwidth are out.
So... am I on the right track? Do I need one residential back-connect system with session control for the shorter sessions, and reserved private proxy list for the longer term ones?
Is there any way to do residential IP's for the longer term uses?
Am I making too much of a big deal about the switching mid-session? I'm assuming this is a dead giveaway that something is out of the ordinary with that user. Is this correct?
Is three some other type of solution I should be looking at? Would I be better off retooling my system to have a single outgoing IP so I could use a solution that allows only 1 IP access, but a different proxy per port, etc? Looking to do this on a reasonable budget.
1) Lots of tiny virtual machies (each with own IP) that need proxies
2) Need full anonymity AND stealth, so something like Tor is out as it leaves it's own fingerprint
3) Each needs only 1 proxy at a time as it is being used for a particular social media profile
4) I'm assuming proxy should not switch during session as this would not be usual behavior for a given social media user.
5) Some profiles are one-offs with sessions lasting from several minutes to half a day. Others are persistent and will log in again as same profile over a period of several months, and will need access to the same IP to do so.
6) I'm assuming this may require two systems: One for shorter sessions that allows per-session switching (cannot switch on timer mid-session), and another for the longer term use where I have reserved private proxy that I switch as needed every few months.
7) Use involves media streaming, so I'm guessing all the residential backconnect systems that charge by bandwidth are out.
So... am I on the right track? Do I need one residential back-connect system with session control for the shorter sessions, and reserved private proxy list for the longer term ones?
Is there any way to do residential IP's for the longer term uses?
Am I making too much of a big deal about the switching mid-session? I'm assuming this is a dead giveaway that something is out of the ordinary with that user. Is this correct?
Is three some other type of solution I should be looking at? Would I be better off retooling my system to have a single outgoing IP so I could use a solution that allows only 1 IP access, but a different proxy per port, etc? Looking to do this on a reasonable budget.
