Ah, I apologize. I missed that. I saw block/unblock events come in during my tests, I didn't realize they were directed at the source rather than the target.
On Sep 30, 12:59 pm, Mark McBride <mmcbr...@twitter.com> wrote: > Note that block/unblock events are delivered to the person creating or > destroying the block (the source of the action), *not* the target of > the action. > > ---Mark > > http://twitter.com/mccv > > > > On Thu, Sep 30, 2010 at 9:31 AM, tsmango <tsma...@gmail.com> wrote: > > Hi, Ed. Block and unblock events are already being delivered in the > > Site Stream. Very useful! > > > On Sep 30, 12:30 pm, "M. Edward (Ed) Borasky" <zn...@borasky- > > research.net> wrote: > >> As long as we're wishing, I'd like to get a notification when someone > >> blocks me. ;-) > >> -- > >> M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb > > >> "A mathematician is a device for turning coffee into theorems." - Paul > >> Erdos > > > - > > Thomas Mango > > @tsmango > > > -- > > Twitter developer documentation and resources:http://dev.twitter.com/doc > > API updates via Twitter:http://twitter.com/twitterapi > > Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list > > Change your membership to this > > group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
