Spotify Streamfarms - Experience

Synaptic

Newbie
Joined
Nov 15, 2020
Messages
3
Reaction score
3
Hello guys,

my name is Tom and I just got into spotify streaming farm business. First of all please excuse my horrible english skills since im not that expierenced in using the english language for communication purposes.

Im a c#/c++/php hobbyist since about 20 years and i started to build my own tools to farm streams on spotify.

The main reason for starting this thread is to exchange knowledge that people were able to gather while they worked on botting streams.

As for now the expected payout value on my distributors backend panel increases from day to day but I'm not sure if they pay the revenue out at the end of the month, or if spotify already detected me and denie the payout even after increasing the values in their forecast.

Account Creation

I wrote my own little c# programm to mass create spotify accounts but no matter what I do, they got flagged as suspicous and their password is getting changed after 2-3 days.

When i create those accounts i use a fixed proxy ip per account and also a fixed user agent. My account list looks like: username:password:proxy:agent and for sure im using the desired proxy/agent while streaming.

Ive started a little project called "legalizer" - lol - which should make those accounts less suspicous but it failed. One dedicated Server was running those accounts all day long just to perform random actions like following top Charts Artists/Songs/Playlist. I did not addet the feature to listen to acual songs yet but i guess that wont change the outcome.

Also "legalized" accounts password got changed after a few days.

Streaming Workflow

I currently wonder whats the best way to stream my songs while being on a save side. At this point i really do it suspicous. I create 5000 Accounts and each account is playing a album from the first to the last track and then i simply switch to the next account. While doing so the "monthly listeners" value also increase in a nice way but as soon as a spotify anti fraud employee checks it manually im pretty sure they will suspend the artist.

How do you handle this? Do you guys reuse one account or maybe play differend songs to make it less suspicous?

Software Used

I currently use selenium to perform those actions. I attached all tactics ive found on google to hide the webdriver. ( removed navigation.webdriver, cdc_, permissions undefined, .. ) Meanwhile Im also able to run the bot multitabbed and headless and it works but headless did not gave me the performance boost i though it will give and when using the tabbed mode i can not change the proxy so it is kind of pointless.

How big should I get?

in my imagination the spotify fraud team wont check every artist but for sure those, who hit the big numbers.
Does any of you guys knows something about the numbers which are kind of save to stay under spotifys radar?

I currently have like 40 songs with about 10k to 15k streams. I could set up a new Artist with new songs and repeat in order to stay low on the numbers or continue up to lets say 100k streams per song.

Maybe it don't even matter and spotify checks every case which get flagged as suspicous sooner or later. Let me know what you know :D



Well anyways - you can share your knowledge in all terms here and we can try to exchange more findings over time. You can also pm me if you wont share infos to public.

Thanks for reading.
 
Good initiative. Try to keep the numbers low not to trigger any flags initially and instead spread over multiple artists as some will always get flagged for sure.
 
What type of proxies are you using? 5000 accounts using different data center proxies will definitely be a red flag.

I'd look at using a mix of residential and 4G.

Definetly keep the numbers per track, per artist as low as you can. Spread out among a lot of artist's that look super real with their own social media profiles.
 
puppeteer>selenium in many cases.
 
How long is the duration of every track you had? 1-minute each track?
 
What type of proxies are you using?
..
Spread out among a lot of artist's that look super real with their own social media profiles.

Im not sure what you guys mean with residential/datacenter ips. I don't think spotify is able to take a look behind those ip addresses. I order 1000 private ips geolocated in germany every month ( im able to refresh them once every 10 days if i wish to). Im not sure if they come from datacenters or residential areas.

puppeteer>selenium in many cases.

I read alot about puppeteer in my research but did not tryed it out yet - could you explain why?

How long is the duration of every track you had? 1-minute each track?

1-2 minutes


Keeping numbers low was my first though also but its a lot of work and pretty hard to get:

a) own song material
b) distribute it
c) wait 1-3 weeks per release until its online
 
Im not sure what you guys mean with residential/datacenter ips. I don't think spotify is able to take a look behind those ip addresses. I order 1000 private ips geolocated in germany every month ( im able to refresh them once every 10 days if i wish to). Im not sure if they come from datacenters or residential areas.

They most definitely will look at where the IP is coming from as a normal user would not have an IP that is detected as a proxy from a datacenter so it make it painfully obvious to them that you are a bot.

This is the first check any website will do and it is known as IP quality.

Datacenter proxies are private/shared proxies from a server in a warehouse. Residential proxies look identical to a proxy a normal user would be using. 4G proxies are the best because they are harder to obtain for spamming/botting.

High quality proxies should be your first plan of attack.
 
4G proxies are the best because they are harder to obtain for spamming/botting
Its not working like this. Overall residential = mobile IP in therms of quality but this depends on actual case.

For example same operator can offer dsl line and mobile internet. IP range assigned for mobile users can be really smal compared to residential IP ranges. Back in time when residential IP ranges were assigned to big guys it was very easy to get huge IP range for cheap or no cost.

In theory guy can also get bunch of 4g modems and sim cards and create huge proxy pool. At same time its not doable/hardly doable with residential line.

I don't think spotify is able to take a look behind those ip addresses.
Im sure they look at IP addresses.

I read alot about puppeteer in my research but did not tryed it out yet - could you explain why?
Just take a look at puppeteer extra and puppeteer stealth ;)
 
Its not working like this. Overall residential = mobile IP in therms of quality but this depends on actual case.

For example same operator can offer dsl line and mobile internet. IP range assigned for mobile users can be really smal compared to residential IP ranges. Back in time when residential IP ranges were assigned to big guys it was very easy to get huge IP range for cheap or no cost.

In theory guy can also get bunch of 4g modems and sim cards and create huge proxy pool. At same time its not doable/hardly doable with residential line.


Im sure they look at IP addresses.


Just take a look at puppeteer extra and puppeteer stealth ;)


Well i checked puppeteer stealth out and i assume i reworked all ideas in c# already according to this simple test:

https://intoli.com/blog/not-possible-to-block-chrome-headless/chrome-headless-test.html

im hiding cdc with a patched chromedriver and i override useragents, webdriver, plugins, permissions and all that stuff.
 
Back
Top