News Feed
- DrugHub has agreed to fully refund all users who lost money in the SuperMarket exit scam.
- Retro Market has gone offline. Circumstances of the closure unknown.
- SuperMarket has closed following an exit scam by one of the admins.
- The admin of Incognito Market, Pharoah, has been arrested by the FBI several months after exit scamming.
- Silk Road
- darknet markets list
- Popular P2P exchange LocalMonero has announced it is closing.
Regarding proxies, I’ve observed that socks5 proxies are more reliable for mobile use compared to residential proxies, which often have poor fraud scores or issues with geo-matching. While this alone isn’t a deal-breaker unless IP addresses are burnt (i.e., flagged for misuse), it still contributes to the overall "fraud" score.
Your points have confirmed a lot of my own findings. I’ve been "aging" my profiles in a similar way building up a history on high-intent targets before hitting the LPs. My main struggle, as you guessed, is the inconsistency that comes from the human element in my operation.
This is where your reply hit me hard. You said: I’ve integrated all of this functionality through AdsPower’s API and launched bot-master Python apps.
That's the wall I'm hitting. That's the next level.
I've built out the individual components. My Python scripts can handle the API launches, the proxy management, the on site navigation... but my architecture is clunky. It's a series of disconnected tools, not one cohesive "bot-master" app like you've described. My process still requires too much manual oversight to chain the tasks together, and the whole thing feels... fragile. It doesn't have the elegance or the robustness of a truly autonomous system that I know is possible.
I feel like I've built a collection of perfect, lethal rifle parts, but I'm struggling to assemble them into the self firing weapon you've clearly perfected.
This might be a long shot, and feel free to tell me to piss off, but seeing a master's architecture is worth more than a thousand theories. I'm not asking for your private LPs or your proxy sources. But I am wondering if you'd be willing to share a sanitized, stripped-down version of your "bot-master" app's core logic or structure? Not the whole thing, of course, but maybe just the main orchestration loop that shows how you elegantly chain the API launch, the cookie warm up, the site navigation, and the shutdown into one seamless process.
I'm at a point where I'm just spinning my wheels trying to architect it correctly, and I know I'm probably overcomplicating it. Seeing how a real pro handles the state management between those different phases would be an absolute game changer.
Cheers for the solid advice either way. It's already given me a lot to think about.Respect