How does my phone farm framework look?

[fone007]

My idea here is to have 10 phones (motherboard phone box not full phones). Each motherboard is equipped with sim slots. Automatically posting and interacting on instagram, and potentially branching out to other social platforms. The purpose being to push OF models through pages that look like meme pages, clip pages, model pages, ect. My initial framework was,

Docker containers hosting independent appium servers for each device, to view the phones I would use STF and have an "orchistrator.py" file directing scripts from a folder to each appium server then to selected phone, these scripts of course will heavily simulate human behavior and randomize imputs. After speaking with some people on the forums I've realized somethings I didnt before that will make me stick out like a sore thumb...

1. Mother board phone farms are lacking esential hardware componates like camera, sensor flex cable, mic/speaker
2. Appium leaves fingerprints that no regular user would have
3. USB debugging staying enabled since i cant just turn it off due to each motherboard missing a screen
4. Developer mode staying enabled since i cant just turn it off due to each motherboard missing a screen
5. Identical device fingerprints across devices like, device model, android build, screen resolution, timezone, constant charging, ect.

My thoughts now are

1. Buy cameras, sensor cables, ect to and add them to the motherboards
2. Use ADB and scrcpy instead of Appium and STF


Clearly instagram isnt super strict considering the ammount of p0rn bots that DM me on a daily basis but id like to limit as much fingerprinting as possible to allow me to expand to other socials that may not treat fingerprinting the same. Does my idea with scrcpy and ADB sound reasonable or am setting my self up for failure here? Any and all feed back is appreciated,

Cheers.

 

[Daniel081]

My idea here is to have 10 phones (motherboard phone box not full phones). Each motherboard is equipped with sim slots. Automatically posting and interacting on instagram, and potentially branching out to other social platforms. The purpose being to push OF models through pages that look like meme pages, clip pages, model pages, ect. My initial framework was,

Docker containers hosting independent appium servers for each device, to view the phones I would use STF and have an "orchistrator.py" file directing scripts from a folder to each appium server then to selected phone, these scripts of course will heavily simulate human behavior and randomize imputs. After speaking with some people on the forums I've realized somethings I didnt before that will make me stick out like a sore thumb...

1. Mother board phone farms are lacking esential hardware componates like camera, sensor flex cable, mic/speaker
2. Appium leaves fingerprints that no regular user would have
3. USB debugging staying enabled since i cant just turn it off due to each motherboard missing a screen
4. Developer mode staying enabled since i cant just turn it off due to each motherboard missing a screen
5. Identical device fingerprints across devices like, device model, android build, screen resolution, timezone, constant charging, ect.

My thoughts now are

1. Buy cameras, sensor cables, ect to and add them to the motherboards
2. Use ADB and scrcpy instead of Appium and STF


Clearly instagram isnt super strict considering the ammount of p0rn bots that DM me on a daily basis but id like to limit as much fingerprinting as possible to allow me to expand to other socials that may not treat fingerprinting the same. Does my idea with scrcpy and ADB sound reasonable or am setting my self up for failure here? Any and all feed back is appreciated,

Cheers.

Yo, really solid thinking here — respect for laying it all out. You’re definitely on the right path by pivoting away from Appium and thinking deeper about fingerprinting.


ADB + scrcpy is a smarter alternative for control, but it’s not completely invisible either. Platforms can still flag USB debugging/dev mode, so you’ll want to spoof or disable those once setup is done tricky without screens, but possible with some automation or custom ROM work.


Adding the missing hardware (camera, sensor flex, mic, etc.) is a must, platform's absolutely check for those. Same with unique device fingerprints, using identical builds across all boards will get you clipped fast. You’ll need to randomize the build. Prop values, Android IDs, timezone, sensor data, and ideally run mobile proxies per device.


IG might not be strict now, but if you're planning to scale or expand to stricter platforms (TikTok, X, etc.), you’ll want to get your hardware, network, and behavior looking as human as possible.


In short, ADB/Scrcpo is a better tool, but without full spoofing + randomness, the setup's still noisy. You’re close though. Keep pushing.


Cheers.

 

[zammy669]

My idea here is to have 10 phones (motherboard phone box not full phones). Each motherboard is equipped with sim slots. Automatically posting and interacting on instagram, and potentially branching out to other social platforms. The purpose being to push OF models through pages that look like meme pages, clip pages, model pages, ect. My initial framework was,

Docker containers hosting independent appium servers for each device, to view the phones I would use STF and have an "orchistrator.py" file directing scripts from a folder to each appium server then to selected phone, these scripts of course will heavily simulate human behavior and randomize imputs. After speaking with some people on the forums I've realized somethings I didnt before that will make me stick out like a sore thumb...

1. Mother board phone farms are lacking esential hardware componates like camera, sensor flex cable, mic/speaker
2. Appium leaves fingerprints that no regular user would have
3. USB debugging staying enabled since i cant just turn it off due to each motherboard missing a screen
4. Developer mode staying enabled since i cant just turn it off due to each motherboard missing a screen
5. Identical device fingerprints across devices like, device model, android build, screen resolution, timezone, constant charging, ect.

My thoughts now are

1. Buy cameras, sensor cables, ect to and add them to the motherboards
2. Use ADB and scrcpy instead of Appium and STF


Clearly instagram isnt super strict considering the ammount of p0rn bots that DM me on a daily basis but id like to limit as much fingerprinting as possible to allow me to expand to other socials that may not treat fingerprinting the same. Does my idea with scrcpy and ADB sound reasonable or am setting my self up for failure here? Any and all feed back is appreciated,

Cheers.

Your phone farm framework for pushing OF models via Instagram (and potentially other platforms) is creative but has risks.

Switching to ADB and scrcpy is a step in the right direction to reduce detection, but there are still challenges.

 

[Ralphoton]

Just one suggestions for you, You can use real phones with screens and randomize each device’s settings and IDs to hide fingerprints.

 

[fone007]

Just one suggestions for you, You can use real phones with screens and randomize each device’s settings and IDs to hide fingerprints.

unfortunately its starting to feel like that might be the best route. that or waste serious time trying to make the motherboard farm useful for high level tasks...

 

[WindSpace Agency]

Switching from Appium to ADB + scrcpy is a smart move - fewer obvious flags. Just remember it’s not fully invisible, so spoof or turn off USB debugging after setup. Make each device unique (build.prop tweaks, new Android IDs, different timezones, sensor data) and run mobile proxies.

 

[DropVS]

What is the best phones to IG?

 

[befiveanati]

Yo, really solid thinking here — respect for laying it all out. You’re definitely on the right path by pivoting away from Appium and thinking deeper about fingerprinting.


ADB + scrcpy is a smarter alternative for control, but it’s not completely invisible either. Platforms can still flag USB debugging/dev mode, so you’ll want to spoof or disable those once setup is done tricky without screens, but possible with some automation or custom ROM work.


Adding the missing hardware (camera, sensor flex, mic, etc.) is a must, platform's absolutely check for those. Same with unique device fingerprints, using identical builds across all boards will get you clipped fast. You’ll need to randomize the build. Prop values, Android IDs, timezone, sensor data, and ideally run mobile proxies per device.


IG might not be strict now, but if you're planning to scale or expand to stricter platforms (TikTok, X, etc.), you’ll want to get your hardware, network, and behavior looking as human as possible.


In short, ADB/Scrcpo is a better tool, but without full spoofing + randomness, the setup's still noisy. You’re close though. Keep pushing.


Cheers.

this response is Ai btw

 

[ToyBox Marketing]

If you plan to use scrapy, look into a second monitor where you can have the screens open. We know a couple agencies that have 2 monitors that have multiple screens for scrapy open on each page.