Hey there, I have a script that syncs my statuses from Twitter to a local database, before converting them to e-mail and pushing them into an e- mail folder. Using the local database, it enumerates any older than 7 days before making /statuses/destroy requests to delete them.
This is where the fun begins. The first thing I noticed was that most/ all the statuses I tried to delete are still present in the web interface (note: not search.twitter, actually on the main site on my profile page). On resetting the deleted flag in the local database and rerunning the script, I see that /statuses/destroy throws errors for about 50% of the previously deleted IDs – in other words, not only did it tell me previously that the statuses were deleted when they weren't, it's happy to delete them all over again. If you look at my profile (davidbelfast) you'll see that I apparently have 0 statuses, and yet if you look at my history, you can see there are statuses going back well over 7 days. I've re-run the deletion portion of the script repeatedly, and finally the API is reporting "status doesn't exist" errors for every ID, but if you look at the web interface, they're all still there. W..t..f?? Another oddity is the status count reported by the web interface is different to that reported by the API. /users/show/davidbelfast reports 42 statuses. Cheers, David
