Building a Custom Cloaker with ChatGPT

Status
Not open for further replies.

deppo

Elite Member
Jr. VIP
Joined
Oct 2, 2022
Messages
1,584
Reaction score
2,870
I like the idea of having my own cloaker doing exactly what I want it to do and customize all its parameters according to my needs. As with everything custom, if functional, it has the benefit of not being detected or targeted by major platforms. For instance, if I suspect some Residential IPs are manual reviewers from traffic sources then I add them to my cloaker having the potential to build something robust over time.

I know programming basics but I'm no expert by any stretch of the imagination and that is why I will be using AI as my assistant. No ETA for this project and it is intended to be a half journey half feedback thread to be updated on a regular basis.

So far I deployed an Ubuntu EC2 LAMP server on an AWS credit account which makes my cloaker completely free as I'm utilizing AWS credits that I make on demand.

As a first step I have edited the Apache config file with a rule to allow all x country visitors in and redirect all outside visitors to a safe related to the niche advertised blog. This is because I usually target only one country in my campaigns at a time.

Next will probably be to start building a list with VPNs, hosting, Luminati addresses etc. per country as well as suspect visits based on patterns. I will probably look into user agents a bit later.
 
Interesting journey. Will be following this. Any updates so far?
 
Interesting journey. Will be following this. Any updates so far?

It works pretty well as far as speed is concerned so far just from the basic geo-redirection, you do not even realize that there is a redirection, yes, that fast. This is one of the reasons I decided to build this from the ground up because for a lot of cloakers in the market it takes a few hundred ms for the redirection, for some even more than a sec. This is traffic aka money lost. I have not tested this in one of the major traffic sources yet but advetising on one of the lesser ones works pretty well so far with no bans and fast redirections.

one of the major things you need to work out is how to detect bots and update the IP list automatically. doing it manually won't cut it.

Good idea even though above my paygrade atm. Noted though to be researched.
 
It works pretty well as far as speed is concerned so far just from the basic geo-redirection, you do not even realize that there is a redirection, yes, that fast. This is one of the reasons I decided to build this from the ground up because for a lot of cloakers in the market it takes a few hundred ms for the redirection, for some even more than a sec. This is traffic aka money lost. I have not tested this in one of the major traffic sources yet but advetising on one of the lesser ones works pretty well so far with no bans and fast redirections.



Good idea even though above my paygrade atm. Noted though to be researched.

Are you building some kind of IP database into it? Mapping out well known server IPs like Amazon and residential IPs and so on?
 
Are you building some kind of IP database into it? Mapping out well known server IPs like Amazon and residential IPs and so on?

Not yet, but this would be the next phase of the plan, however since I get no account bans on the current traffic source I run it as is for now.
 
Status
Not open for further replies.
Back
Top