merieke
Registered Member
- Jun 20, 2011
- 73
- 30
Thanks for providing your expertise to help others out. I have a couple specific questions I was hoping you could help with.
1) I know the root cause of a temporary follow block can be related to several things. I am curious whether the action of changing the profile description/link is commonly known to create a block?
1a) I am using a popular bot and when a temporary block occurs it notes something like "Username - Report issue to instagram successful" in the log. Do you know what is getting reported to instagram here and should I be concerned?
2) On the topic of prelander/cloaker I built a simple page that loosely mimics a popular DDOS service. There is no captcha but instead there is a button that becomes clickable after a couple seconds and the visitor is encouraged to click the button to continue to their content. The target URL is split across 4 javascript variables, encrypted, and then decrypted and concatenated using an onclick action on the button. At no point does the full string get saved into client side javascript. My theory is that this prevents any bot from reading the source and having any idea where they are getting routed. Does this sound like a good approach? I was also thinking about using some server side code to insert a series of hidden divs that grabs rotating content from a public website to help keep the full page fingerprint from being discovered.
Thanks!
1) I know the root cause of a temporary follow block can be related to several things. I am curious whether the action of changing the profile description/link is commonly known to create a block?
1a) I am using a popular bot and when a temporary block occurs it notes something like "Username - Report issue to instagram successful" in the log. Do you know what is getting reported to instagram here and should I be concerned?
2) On the topic of prelander/cloaker I built a simple page that loosely mimics a popular DDOS service. There is no captcha but instead there is a button that becomes clickable after a couple seconds and the visitor is encouraged to click the button to continue to their content. The target URL is split across 4 javascript variables, encrypted, and then decrypted and concatenated using an onclick action on the button. At no point does the full string get saved into client side javascript. My theory is that this prevents any bot from reading the source and having any idea where they are getting routed. Does this sound like a good approach? I was also thinking about using some server side code to insert a series of hidden divs that grabs rotating content from a public website to help keep the full page fingerprint from being discovered.
Thanks!