HTTP vs SOCKS proxies for TWITTER

I heard couple of time SOCKS proxies are better than HTTP for twitter automation,
but never seen an explanation or proof to explain why.

-talking about 4G proxies

Wonder if you guys heard the same or something different?

stick to 4g..............trust me.......................

proxygo said:

stick to 4g..............trust me.......................

Click to expand...

im the process of trying a couple of 4g providers, and as of now I like the results compared to residential proxies.
if no new problems rise up with 4G proxies. I will soon have a permanent 4G provider.

you also selling 4g proxies?

proxygo said:

stick to 4g..............trust me.......................

Click to expand...

even tho I plan on switching to 4G proxies for the most part, still want to keep my options open.
One thing I learned with social media automation is:

"there is no one perfect way of doing things, it constantly changes and you have to adapt"

I suppose Socks are typically what you'd consider as more "flexible" compared to, say, HTTP. They're not nearly as fast connection speed-wise, but they do handle a far wider variety of program/ protocol and traffic without a snag. That's definitely worth considering.

proxygo said:

stick to 4g..............trust me.......................

Click to expand...

Do you have a preferred vendor? I'm looking for one.

dunzomate10 said:

Do you have a preferred vendor? I'm looking for one.

Click to expand...

yes, me too.

cant find a shared 4G provider at all, so now im looking for a fast rotating unique 4G provider for a good price, preferably not US, since the price is multiple times higher

imccafey said:

I suppose Socks are typically what you'd consider as more "flexible" compared to, say, HTTP. They're not nearly as fast connection speed-wise, but they do handle a far wider variety of program/ protocol and traffic without a snag. That's definitely worth considering.

Click to expand...

Not really. They are completely different.

SOCKS proxies work at a different level in the network stack to HTTP proxies.

HTTP proxies are APPLICATION level proxies, so an application is proxy aware and can route different requests through different proxies (so one proxy per account).

SOCKS proxies work at the OS level (basically) and the application is UNAWARE of the proxy. You can think of a VPN as a socks proxy. Everything on the OS routes through the socks proxy by default. but an application cannot choose to route one request through one proxy and another request through a different proxy. You'd need to manually reset the socks proxy (like you'd need to reset the VPN).

Personally I wouldn't call that "flexible" from the point of view of what what 99/100 people who are botting mean.

but they do handle a far wider variety of program/ protocol and traffic without a snag.

Click to expand...

This is true, but for someone botting, doesn't really apply. Although if you are browser botting it can protect you from calls that bypass the browser proxy that could reveal your true IP (same as a VPN would)