A user has essentially an infinite amount of time to delete a tweet he
has sent. The sequence of events is
a. User sends a tweet.
b. Twitter forwards it to Streaming and inserts it into the Search
indexing queue if the user is not blocked.
c. User says at some point later, "Oh crap - did I really say that?"
and deletes the tweet.
d. Twitter deletes the tweet from Search and its other public-facing
facilities, and sends a "delete" message with the deleted tweet's user
and status IDs out to the *unfiltered* Streaming connections. I'm
assuming it knows enough not to send all the "firehose" deletes to
lower-frequency streams - it's none of "sample"'s business what tweets
got deleted from "firehose" or "gardenhose". ;-)
--
M. Edward (Ed) Borasky
borasky-research.net/m-edward-ed-borasky/
"A mathematician is a device for turning coffee into theorems." ~ Paul Erdos
Quoting Abraham Williams <[email protected]>:
Couldn't you add a cleaning process to statuses just before they are sent to
clients but after they have been filtered into streams? The cleaning process
could pick up delete flags and remove extraneous metadata from the status.
Abraham
On Fri, Feb 26, 2010 at 23:31, M. Edward (Ed) Borasky
<[email protected]>wrote:
--
M. Edward (Ed) Borasky
borasky-research.net/m-edward-ed-borasky/
"A mathematician is a device for turning coffee into theorems." ~ Paul
Erdos
Quoting Mark McBride <[email protected]>:
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?)
Yeah - definitely tricky. The delete messages coming from "sample" only
give the user_id and status_id, and I have to assume that the "publish"
process doesn't send me a delete for a status that it didn't send to me. ;-)
I suppose you could do the same for "filter", but that would mean keeping
track of all the tweets sent to *each* filter connection, not just one set
of tweets like "sample". That could get ugly since you can't predict /
control how many "filter" connections you're going to get or how many tweets
are going to be passed by the filter criteria.
--
Abraham Williams | Community Advocate | http://abrah.am
Project | Out Loud | http://outloud.labs.poseurtech.com
This email is: [ ] shareable [x] ask first [ ] private.
