Minor Structure and Cheat-sheet for response tricks v013

gistfile1.txt

// gone a little bit strange there, digging deeper of how the connection usually interacts and how services should be selled refferring to Jordan's Belford cases
[
  {
    "object": "200 RUR Service will solve a problem.",
    "object": "10 miliseconds Service per problem.",
    "object": "10 miliseconds Service will solve a problem for 200 RUR.",
    "object": "200 RUR Service will solve a problem in 10 miliseconds.",
    "object": "200 RUR Service per problem."
  },
  {
    // fair cheats in methodology
    "object": "0 RUR 100 RUR product will solve a problem.",
    "object": "Looking for 1 see 2",
    "object": 200 || "See the error bellow",
    "object": 200 followed 54ms then mirror followed to replicate bot history and loop according rate || "See the .." && "See the error" && "See the 1 2 3 4 5" && "HTMLDOMCONTENT" && etc
    "object": 200 mirror refferer's parent domain if respond > than average
    "object": 200 set header mirrorly as refferer then proceed
    "object": 200 set timeout 2000ms then proceed
    "object": 200 set timeout 2000ms then proceed minor error then reload
    "object": 200 set timeout 2000ms then referer for subcontrolled system adducate then referrer back
    "object": 275 ondemand, generate minor content then error 500 and refer for better one
    "object": 2[1-9][1-9] unique success response, min response time then normal then "formal content" then "minor objective goals referrer" then "smaller interesting referrer" if bot stopped to crawl save to story then generate further 
    "object": 2[1-9][1-9] unique success response, min response time then normal then "formal content" then referrer if it is back then according history loop to certain number of times change of headers or display content if it is trying enough
    "object": 2[1-9][1-9] unique success response, min response time then normal then "formal content" then referrer if it is back then according history loop to certain number of times change of headers or display content if it is trying then give crawler the actual job with endless list of referrers to decide best fit to crawl next
    "object": 2[1-9][1-9] unique success response, min response time then normal then "formal content" then referrer if it is back then according history loop to certain number of times change of headers or display content if it is trying then give crawler the actual job with endless list of referrers to decide best fit to crawl next through crawling or in the end of it share the crawl story to others specified 
    "object": 2[1-9][1-9] unique success response, min response time then normal then "formal content" then referrer if it is back then according history loop to certain number of times change of headers or display content if it is trying then give crawler the actual job with endless list of referrers to decide best fit to crawl next through crawling or in the end of it share the crawl story to others specified or if there are all content loaded and crawl not leaving, follow to the errors through headers
  }
]

// if crawl period is less frequent show the unique bad sides of the presence
// if crawl is annoying turn rate down