martin@rootjazz wrote: ↑Tue Sep 27, 2022 2:54 pm
SC completely changed the commenting protection, working on it. It's not easy. It's more complicated than it was
True that.
I used static IPs from different companys
price range 1-4$ each, the first days it was working fine,
after a few days more and more IPs faild to drop comments
Old accounts/new accounts no difference
swapped my IPs and it was working for a few comments per account again.
but it just kept getting worse and worse day by day
out of 100 comments maybe 5 will made.
I did a longer break 3-4 months and tried it again few weeks ago with Residential proxies from
div companys 150$ per 15GB - IP pool over 8million
and it was working perfect for a few days 100/100 but even with this big pool of different IPs
after these good working days it was the same as i got with static IPs
worse and worse day by day maybe 5/100 after a week
I guess it doesn't matter which type of proxies you use for comments, expensive resential
or cheaper static/ even your home IP seems to fail with SCM after some time.
Soundcloud has a way to detect SCM and will temporarily block your account/IP for comments,
tried also to log in manually with the faild accounts (IP) and it was also not possible to comment with a real home IP
in my browser after using SCM for comments. These are only temporary blocks, mostly 24-48 hours
So there are two problems,
Soundcloud has the ability to recognize SCM if using for comments
this means that the account plus IP can no longer be used for comments in SCM
changing the IP can help 50/50 if not, problem number two will
temporary block your account, even if using the account manually in your browser
on your home IP.
Seems SCM is not 100% simulating a request like you do manually in your browser and soundscloud can detect it
and will block the IP/Account.
Currently most of my accounts/IPs are blocked if using SCM for comments, manually in my browser working fine.
Maybe & hopefully soon you can help us Martin
