INSTAINFANTRY Docs
  • Welcome Message
  • Preface
  • Who is GreyHatNik?
  • Chapter 1: Philosophy and Fundamentals
    • The GHM and InstaInfantry Philosophy
    • Botting Fundamentals
      • Trust Scores Explained
      • Age
      • Device
        • Device used to MAKE an account
        • Device used to OPERATE an account
      • Email
      • Phone Number
      • Proxies
      • Software/Scripting
      • Parameter Settings
      • Reaching Equilibrium
  • Chapter 2: Using InstaInfantry
    • Adding Accounts into INSTAINFANTRY
    • Branding Accounts
      • Manual Editing and Mass Editing
      • The Cloning / Reposting
    • Reactions Module and Driving Traffic
      • The Reactions Module
      • Story Reactions
      • Mass Actions
    • The Use of Accelerators
    • DMs, Message Customization, and Managing DMs with Chatters
      • The Reply to pending DM
      • The Welcome DM
      • The Send DM Feature
    • Custom Delays and Activity Time Settings
      • The Activity Time Settings
      • The Custom Delays
    • Target Quality Tracking and Debug Mode
      • Target Quality Tracking
      • Task Expiration
      • Debug Mode
    • The Activity Log
    • Conclusion
  • Chapter 3: Botting Strategies
    • Introduction and Terminology
      • King Account
      • Customized Infantry Account
      • Generic Infantry Account
      • Scraper/Accelerator/Low-Tier Account
    • Strategy #1: Automating your King - Follow/Unfollow
      • Strategy #1's Execution
      • Strategy #1's Pros:
      • Strategy #1's Cons:
      • Strategy #1's Verdict: 🔴
    • Strategy #2: Automating your King - Story Reactions (Small Scale InstaInfantry Customs)
      • Strategy #2's Execution
      • Strategy #2's Pros:
      • Strategy #2's Cons:
      • Strategy #2's Verdict
    • Strategy #3: InstaInfantry Customs - Story Reactions (Large Scale)
      • Strategy #3' Execution
      • Strategy #3's Pros:
      • Strategy #3's Cons:
      • Strategy #3's Verdict: 🟢
    • Strategy #4: InstaInfantry Pyramid (King/Infantry)
      • Strategy #4's Pros:
      • Strategy #4's Cons:
      • Strategy #4's Verdict: 🟢
    • Strategy #5: King/Infantry - Comments
      • Strategy #5's Pros:
      • Strategy #5's Cons:
      • Strategy #5's Verdict: 🔴
    • Strategy #6: Mass Mentions
      • Strategy #6's Pros:
      • Strategy #6's Cons:
      • Strategy #6's Verdict: 🟡
    • Strategy #7: Mass Direct Messaging (Mass DMs)
      • Strategy #7's Pros:
      • Strategy #7's Cons:
      • Strategy #7's Verdict: 🟢
    • Strategy #8: Interactive Quiz/Maze
      • Strategy #8's Pros:
      • Strategy #8's Cons:
      • Strategy #8's Verdict: 🟡
    • Strategy #9: Artificial Engagement
      • Strategy #9's Pros:
      • Strategy #9's Cons:
      • Strategy #9's Verdict: 🟡
    • Conclusion to Strategies
  • Chapter 4: Target Audience Selection
    • Introduction
    • Source Assessment
      • Source Discovery - Music
      • Source Discovery - OnlyFans
      • Sourcing for Active Users
    • Common Pitfalls When Target Scraping/Filtering
    • Conclusion
  • Chapter 5: Technical Issues/Troubleshooting
    • Introduction
    • Dealing with Relogins
      • “We Suspect Automated Behavior” Challenge
      • “Your Post Goes Against Our Community Guidelines” Challenge
      • Phone Verification
      • Email Verification:
      • Captcha
      • Selfie Verification
      • Temporary Lock / 24 Hour Review
      • Suspension
      • Permanently Disabled
  • Chapter 6: Final Words
Powered by GitBook
On this page

Was this helpful?

  1. Chapter 5: Technical Issues/Troubleshooting
  2. Dealing with Relogins

“Your Post Goes Against Our Community Guidelines” Challenge

Previous“We Suspect Automated Behavior” ChallengeNextPhone Verification

Last updated 1 year ago

Was this helpful?

This one is of a similar vein as the automated behavior checkpoint. Again, it’s very easily resolvable and doesn’t really impact the account in too significant of a way. This challenge can occur pretty regularly when you are using the discussed in the section of the docs. Generally, Instagram is able to spot content that’s being reposted by tracking its hash. This tends to occur most often if you are consistently reposting content from a singular source since it sees the same hashes appear over and over again.

To prevent this challenge from appearing in the future, try to not repost more than one piece of content from a singular source per day if you can help it. This challenge can also occur as a result of people reporting the content but that occurrence is even more rare in most instances.

Resolving this checkpoint has the same degree of ease as the previous one. Just click on the blue “OK” button in your device or emulator and everything will go back to normal. However, this challenge does have a slightly higher severity score and you generally only get about three of these before it escalates into a suspension.

Severity Level: 2.5/10

Repost module
Branding Accounts