I hate to sound like a broken record, but this is going on to its fullest extent last night and into today.
Either via the web interface or API calls, I am destroying direct messages. (On the web interface, they are removed from the list, and the API returns that it has destroyed them.) However, they're still there. I'm totally unable to delete DMs the last 24 hours. I will open an issue on the tracker, but I wanted this information saved in this thread as well to reflect the problem of the API and web interface both promising to have deleted an object, but that object (in this case a DM) still existing. Thanks, Blair On Mar 11, 5:22 pm, Alex Payne <[email protected]> wrote: > If it's any consolation, we were just talking about the completely > unacceptable inconsistencies of this sort in our daily meeting of the > people responsible for Twitter's infrastructure. I've sent along your > email to that group as a perfect illustration of those > inconsistencies, and why fixing them needs to be a priority. I hope > we'll have solutions in hand soon. > > > > On Wed, Mar 11, 2009 at 14:35, blairblends <[email protected]> wrote: > > > I realize this may not be the most exacting place to bring up this > > topic, but the other avenues for Twitter support have all proven, at > > least for me, to be black holes. > > > Since at least September, whether referenced from the web interface or > > the API calls, the number of direct messages in my account is not > > consistent from one call to the next. For example, right now there > > are actually 10 messages in my inbox. However, when I load the web > > interface, it says 7. I immediately reload, and it says 9. I reload > > again and it says 7. A fourth reload and I finally get 10, the > > correct number. And this just continues over and over. > > > And, for example, when the web interface or API reports 7 messages, > > that's all I can actually see. The three recent messages ahead of it > > are not listed to me. However, if I reload a few seconds later, and > > I'm shown the count 10, I can see them all. > > > It's very frustrating, since it can sometimes take me an hour to be > > able to see a DM someone sends me. > > > (ASIDE: It's maddening on an entirely different level because SMS > > hasn't worked for me for almost 6 weeks. I used to at least get DM > > notifications, but even those have stopped. I have all the settings > > correct on the Twitter site, but now I just get NO direct messages. > > That's an entirely issue entirely, but I point it out only to > > emphasize that my attempts to get support on that matter have also > > been totally black holed. The only thing I ever hear back from the > > Twitter support site is a form response which, itself, is a COPY of > > that page. It's utterly Sisyphean.) > > > So, I raise the issue of the DM fracture here, where it has great > > chance of getting some attention. I'm not in the least angry, just > > pointing out a 5-month old issue I have tried to raise over and over, > > when on your status page, it appears as if direct messages are problem > > free...when myself and many others are noticing this same problem. > > -- > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
