Dear Jacob
Firstly great to see a response on the error code 226 from one of you guys. I am sure that it had many developers ripping their hair out since October 2013.
Whilst I am sure many of the developer community accept that spam was becoming an issue on twitter. After all we probably all got spammed with the latest Viagra offers or phishing dm saying have you see. his post about you etc.
However these new spam filters seem to be killing off real developers which is shame as the few seem to have spoiled it for the many.
I did file a ticket as instructed and one of your team kindly fixed the issue but after attempting to send a dm containing a link to my app. it quickly reverted back to the error code 226 after a few min (70 dm from 10 users keys which contained links to my app) which seems to have be blocked to my api key for good there after.
Having an app with 10s of thousands of users you can imagine we do need to process quite a high volume of dm each day and these spam filters seem to make that job just impossible. Of course we can remove an link to our website and the dm seems to work just great so for now that seems the way ahead.
However would be good to know if one day we could use our brands URL in without them being blocked all the time. Maybe the idea of whitelisting certain apps or dm texts that pass a means test in the future could be considered?
If you could shed any light on how I could get this to work it would be much appreciated. My ticket ref that was resolved originally was 01139377, but the issue soon returned and I was back to square one.
Best regards