I have bot that I clone and modified but spoaridically failling Oauth

[ChannelsSmall]

I just spent the last 6 hours testing and modifing this twitter bot to maintain my feed on the channel and I was hit with Application cannot perform write actions. Contact Twitter Platform Operations through https://support.twitter.com/forms/platform. I am not sure if that’s a response to OAuth failures? I would get 5 post and 3 authentication failures. I’ve tried to diagnose and compare and contrast my Authorization headers from what is displayed on the portal. The only differences is, some of the oauth_* headers might be out of order? I can’t tell why it’s failing? Now I am left without a way to update my feed without using a third party?

EDIT:

Subject:Case# 89452569: Muzzled application - channelsmall-retweetbot - 15670023 - ChannelsSmall [ref:00DA0000000K0A8.5004A00001S9eRK:ref]
Hello @ChannelsSmall,
 

Thank you for reaching out. We have reviewed your request and have reactivated your API key. Going forward, carefully ensure that your application adheres to Twitter’s policies:
 

    Developer Agreement and Policy

    Automation Rules

    Twitter Rules

 

Please note, applications found to be violating policy again may be subject to permanent suspension.
 

Regards,
Twitter Platform Operations

I don’t know what Muzzled application mean? I’ve tested my OAuth credentials via third party and come back clean?

[LeBraat]

It looks like your app has been flagged as having broken our spam policies judging by the information that you have provided.

Muzzled application means that we have automatically changed your app’s permissions to prevent you from continuing to abuse our spam policies. I strongly encourage you to comb through the rules that our team has provided you and make sure to adjust your app’s activity to not abuse our rules. If you do not comply with these rules, we will permanently suspend your account.

Developer terms

[ChannelsSmall]

Hello,

Thanks for elaborating what Muzzled mean, as the E-Mail didn’t not explain what occurred at all. Failing every 2-3 authentication failures with 2 successes is considered spam? None my other 3 twitter bots, with the same functionality, experience these issues? Now I know that failing authentication is considered spam. When the E-Mails are vague and complied with Twitter polices. You left with no idea what to do about it?

EDIT: I will be rewriting or developing a new bot in PHP. Unlike other API vendors, what is recommended by Twitter developers on reddit, is to mass create twitter accounts with throwaway mobile numbers as Twitter doesn’t offer any Test API’s to debug issues. According to this response, might have to resort to doing.

[LeBraat]

You can read more about our restricted use cases here:
https://developer.twitter.com/en/developer-terms/more-on-restricted-use-cases

What you outlined in your Edit: section is against our policy and will result in the suspension of your apps, accounts, and potentially your IP address.

[LeBraat]