Yes, that's correct. We've considered adding more metadata to delete messages to make routing easier, but the privacy issues involved get tricky (if I delete something, do I *really* want the full text re-sent to a bunch of people?)
---Mark http://twitter.com/mccv On Fri, Feb 26, 2010 at 6:14 AM, John Kalucki <[email protected]> wrote: > Mark might have to comment on this too, but there's a metadata issue that > makes this currently impossible. The deletion notice does not contain all of > the Tweet metadata, just the primary key, and maybe another field or two. > So, there's nothing to match to forward on to your stream. All firehose > consumers will receive the delete, however, so your Tweet should be gone > from search.twitter.com, Bing, Google, Yahoo, etc. etc. > > -John > > > > On Fri, Feb 26, 2010 at 1:18 AM, M. Edward (Ed) Borasky > <[email protected]>wrote: > >> P.S.: A refresh of the "Search" page for my tweets shows that the deleted >> tweet has been removed from Search results, as desired. >> -- >> M. Edward (Ed) Borasky >> borasky-research.net/m-edward-ed-borasky/ >> >> "A mathematician is a device for turning coffee into theorems." ~ Paul >> Erdos >> >> >> >> >> >> Quoting "M. Edward (Ed) Borasky" <[email protected]>: >> >> I'm doing some testing with the "filter" stream using location >>> bounding boxes around PDX. I can send a geocoded tweet, and it shows >>> up in the output of "filter" not too long after that. But when I >>> deleted the tweet from the web app, I never saw a "delete" message >>> come down the filter pipe. Should I see one? How long should I have to >>> wait for it? >>> >>> >> >
