[twitter-dev] Re: Site Streams

[Orian Marx]

Good to hear. I look forward to when I have the time / resources to
start working with it. Thanks.

On Jul 6, 7:47 pm, Mark Krieger  wrote:
> We are doing this in a VERY controlled way, where the switch from REST
> API to Site Streams (and back) is very simple as needed in our
> application. Also, the users who get Site Streams are VERY few, and
> are aware of it. So far, so good, we are doing very well with it. It
> has been up for many days, no interruptions. Happy happy.
>
> Mark
>
> On Jul 6, 1:39 am, Orian Marx  wrote:
>
>
>
>
>
>
>
> > Mark, this is a great post, thanks for taking the time to write it up.
> > What I'm curious about is that I believe Site Streams is still in beta
> > and not supposed to be used in a production environment according to
> > Twitter. Has it been stable for you?
>
> > On Jun 28, 12:24 pm, Mark Krieger  wrote:
>
> > > We've gone live with Site Streams for paying customers of our
> > > TweetRoost product. I wrote a blog with technical details which some
> > > people might find interesting. See it 
> > > athttp://www.mediaroost.com/2011/06/tweetroost-goes-live-with-twitter-s...
> > > -- it is not a product blog or a pitch :) (and I am a big fan of Site
> > > Streams, it was a great project for us to implement)
>
> > > Mark Krieger
> > > President
> > > @mediaroost

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Site Streams

[Orian Marx]

Thanks for the clarification.

On Jul 6, 9:47 am, Taylor Singletary 
wrote:
> Orian,
>
> It's just that one shouldn't go to production without checking in with us
> first right now so we can make sure the capacity outlook is good. We're
> getting closer to increased capacity on Site Streams, but until then we're
> cautious with additional production consumers, especially with larger user
> bases.
>
> @episod  - Taylor
> Singletary
>
>
>
>
>
>
>
> On Tue, Jul 5, 2011 at 10:39 PM, Orian Marx  wrote:
> > Mark, this is a great post, thanks for taking the time to write it up.
> > What I'm curious about is that I believe Site Streams is still in beta
> > and not supposed to be used in a production environment according to
> > Twitter. Has it been stable for you?
>
> > On Jun 28, 12:24 pm, Mark Krieger  wrote:
> > > We've gone live with Site Streams for paying customers of our
> > > TweetRoost product. I wrote a blog with technical details which some
> > > people might find interesting. See it athttp://
> >www.mediaroost.com/2011/06/tweetroost-goes-live-with-twitter-s...
> > > -- it is not a product blog or a pitch :) (and I am a big fan of Site
> > > Streams, it was a great project for us to implement)
>
> > > Mark Krieger
> > > President
> > > @mediaroost
>
> > --
> > Twitter developer documentation and resources:https://dev.twitter.com/doc
> > API updates via Twitter:https://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >https://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Site Streams

[Mark Krieger]

Taylor,

Our user base for this is very small, only a tiny fraction selected
for the test...

Mark

On Jul 6, 9:47 am, Taylor Singletary 
wrote:
> Orian,
>
> It's just that one shouldn't go to production without checking in with us
> first right now so we can make sure the capacity outlook is good. We're
> getting closer to increased capacity on Site Streams, but until then we're
> cautious with additional production consumers, especially with larger user
> bases.
>
> @episod  - Taylor
> Singletary
>
> On Tue, Jul 5, 2011 at 10:39 PM, Orian Marx  wrote:
> > Mark, this is a great post, thanks for taking the time to write it up.
> > What I'm curious about is that I believe Site Streams is still in beta
> > and not supposed to be used in a production environment according to
> > Twitter. Has it been stable for you?
>
> > On Jun 28, 12:24 pm, Mark Krieger  wrote:
> > > We've gone live with Site Streams for paying customers of our
> > > TweetRoost product. I wrote a blog with technical details which some
> > > people might find interesting. See it athttp://
> >www.mediaroost.com/2011/06/tweetroost-goes-live-with-twitter-s...
> > > -- it is not a product blog or a pitch :) (and I am a big fan of Site
> > > Streams, it was a great project for us to implement)
>
> > > Mark Krieger
> > > President
> > > @mediaroost
>
> > --
> > Twitter developer documentation and resources:https://dev.twitter.com/doc
> > API updates via Twitter:https://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >https://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Site Streams

[Mark Krieger]

We are doing this in a VERY controlled way, where the switch from REST
API to Site Streams (and back) is very simple as needed in our
application. Also, the users who get Site Streams are VERY few, and
are aware of it. So far, so good, we are doing very well with it. It
has been up for many days, no interruptions. Happy happy.

Mark

On Jul 6, 1:39 am, Orian Marx  wrote:
> Mark, this is a great post, thanks for taking the time to write it up.
> What I'm curious about is that I believe Site Streams is still in beta
> and not supposed to be used in a production environment according to
> Twitter. Has it been stable for you?
>
> On Jun 28, 12:24 pm, Mark Krieger  wrote:
>
> > We've gone live with Site Streams for paying customers of our
> > TweetRoost product. I wrote a blog with technical details which some
> > people might find interesting. See it 
> > athttp://www.mediaroost.com/2011/06/tweetroost-goes-live-with-twitter-s...
> > -- it is not a product blog or a pitch :) (and I am a big fan of Site
> > Streams, it was a great project for us to implement)
>
> > Mark Krieger
> > President
> > @mediaroost

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Re: Site Streams

[Taylor Singletary]

Orian,

It's just that one shouldn't go to production without checking in with us
first right now so we can make sure the capacity outlook is good. We're
getting closer to increased capacity on Site Streams, but until then we're
cautious with additional production consumers, especially with larger user
bases.

@episod  - Taylor
Singletary


On Tue, Jul 5, 2011 at 10:39 PM, Orian Marx  wrote:

> Mark, this is a great post, thanks for taking the time to write it up.
> What I'm curious about is that I believe Site Streams is still in beta
> and not supposed to be used in a production environment according to
> Twitter. Has it been stable for you?
>
> On Jun 28, 12:24 pm, Mark Krieger  wrote:
> > We've gone live with Site Streams for paying customers of our
> > TweetRoost product. I wrote a blog with technical details which some
> > people might find interesting. See it athttp://
> www.mediaroost.com/2011/06/tweetroost-goes-live-with-twitter-s...
> > -- it is not a product blog or a pitch :) (and I am a big fan of Site
> > Streams, it was a great project for us to implement)
> >
> > Mark Krieger
> > President
> > @mediaroost
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Site Streams

[Orian Marx]

Mark, this is a great post, thanks for taking the time to write it up.
What I'm curious about is that I believe Site Streams is still in beta
and not supposed to be used in a production environment according to
Twitter. Has it been stable for you?

On Jun 28, 12:24 pm, Mark Krieger  wrote:
> We've gone live with Site Streams for paying customers of our
> TweetRoost product. I wrote a blog with technical details which some
> people might find interesting. See it 
> athttp://www.mediaroost.com/2011/06/tweetroost-goes-live-with-twitter-s...
> -- it is not a product blog or a pitch :) (and I am a big fan of Site
> Streams, it was a great project for us to implement)
>
> Mark Krieger
> President
> @mediaroost

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Site Streams beta update

[Charles]

Hi Taylor,

I wanted to ask about the possibility of finding out about the status
of our application to the Site Streams beta.  We submitted it on March
24th and have heard nothing back.  If you require more information
we're happy to provide it, but since we've heard nothing back at all
after more than a month we thought we should at least check in.  The
company is Evri and I believe our application was submitted by David
Kellum.  Please let me know, thank you.

Best,
Chuck

On Apr 19, 11:54 am, Taylor Singletary 
wrote:
> Hi Developers,
>
> We know a lot of you are excited to get started with Site Streams 
> (http://dev.twitter.com/pages/site_streams), but the API will continue to be
> in beta for at least the next few months as we continue preparing it for
> wider release. During the beta, the criteria we're looking for and
> applications we're interested in will change as needs & criteria evolve.
>
> Before applying for the Site Streams beta, we ask that you've developed your
> application far enough along with User Streams and that you've already built
> the necessary status & event consumption routines for a single-user
> scenario. This will prepare you to work with Site Streams at a faster clip
> when access is provided. Site Streams does not support any of the
> search/track features of the User Streams, so if your application requires
> these capabilities, Site Streams may not be the right fit. Some developers
> have asked for Site Streams access with the misunderstanding that it can
> provide a greater percentage of the firehose than the self-serve options
> available to them today -- this is also not the case.
>
> If you're a developer who has hoped for early access to this beta program
> but has been unable to join and are looking for alternate implementation
> options in the meantime, our team is happy to discuss alternate strategies
> on this mailing list with you.
>
> Thanks for your continued patience as we continue productionizing this new
> platform feature.
>
> Taylor Singletary

-- 
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

Re: [twitter-dev] Re: Site Streams beta update

[Taylor Singletary]

Hi Mohan,

It's unclear at this time if track/filter will become part of Site Streams
or not. Site Streams is really focused on the equivalent of home_timeline,
mentions, and associated social events for users. It's still best to use a
separate connection to the streaming API to perform long-term streamed
queries, and the Search API for servicing ad-hoc queries.

@episod  - Taylor Singletary


On Tue, Apr 19, 2011 at 8:42 PM, Mohan Arun  wrote:

> >Site Streams does not support any of the
> >search/track features of the User Streams, so if your application requires
> >these capabilities, Site Streams may not be the right fit.
>
> Are there plans for Site Streams to support search/track features
> in the future? What if you want to filter by a search query?
>
> - Mohan Arun
>
> --
> 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

[twitter-dev] Re: Site Streams beta update

[Mohan Arun]

>Site Streams does not support any of the
>search/track features of the User Streams, so if your application requires
>these capabilities, Site Streams may not be the right fit.

Are there plans for Site Streams to support search/track features
in the future? What if you want to filter by a search query?

- Mohan Arun

-- 
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-dev] Re: Site Streams follow problem

[Rich]

Oh I should add if I use this same code minus the follow parameter and
connect to UserStreams it works fine

On Mar 4, 10:35 am, Rich  wrote:
> Hi there
>
> I'm trying to implement site streams, I've been white listed on the
> account that my users are authenticated against and prior to this I
> recieved an error saying 'User not in role'.
>
> Well the good news is I don't get that anymore so I guess the
> whitelisting is in effect.
>
> I'm connecting using PHP and fsockopen and using oAuth.
>
> If I specify my own username in the follow parameter I get a 401
> unauthorised HTTP response.
>
> If I take out the Content-length header I get an http 400 response
> saying "45Must specify some followings to use sitestreams, e.g.
> follow=1,2,3,4"
>
> This is all over an HTTP post request.
>
> Anyone got any ideas?
>
> $postData = http_build_query($requestParams);
>
> // Oauth tokens
> $oauthHeader = $this->getOAuthHeader('POST', $url);
>
> fwrite($this->conn, "POST " . $urlParts['path'] . " HTTP/1.1\n");
> fwrite($this->conn, "Host: " . $urlParts['host'].':'.$port . "\n");
> fwrite($this->conn, "Content-type: application/x-www-form-urlencoded\r
> \n");
> fwrite($this->conn, "Content-length: " . strlen($postData) . "\r\n");
> fwrite($this->conn, $oauthHeader."\r\n");
>
> fwrite($this->conn, 'User-Agent: ' . self::USER_AGENT . "\r\n");
> fwrite($this->conn, "\r\n");
> fwrite($this->conn, $postData . "\r\n");
> fwrite($this->conn, "\r\n");

-- 
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

Re: [twitter-dev] Re: Site Streams Beta - Endpoint change to sitestream.twitter.com

[Yusuke Yamamoto]

Oops, I was pointing stream.twitter.com instead of sitestream.twitter.com.
http://sitestream.twitter.com/2b/ works fine.

Thanks,
-- 
Yusuke Yamamoto
yus...@mac.com

this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/

On Feb 23, 2011, at 13:04 , Yusuke Yamamoto wrote:

> Additionally, on HTTP I get 404 status code from both 
> http://stream.twitter.com/2/site.json and 
> http://stream.twitter.com/2b/site.json
> 
> [Wed Feb 23 12:13:11 JST 2011]POST http://stream.twitter.com/2b/site.json
> [Wed Feb 23 12:13:11 JST 2011]OAuth base string: 
> POST&http%3A%2F%2Fstream.twitter.com%2F2b%2Fsite.json&follow%3D6377362%252C6358482%26oauth_consumer_key%3DUSLG8ce1GgCOTzmxODYyg%26oauth_nonce%3D2990038945%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1298430791%26oauth_token%3D4933401-D0jHvIeQbyjrENE5TK0iSGr2VVv7ppFOQpmwPztZ1y%26oauth_version%3D1.0%26with%3Dfollowings
> [Wed Feb 23 12:13:11 JST 2011]OAuth signature: Sx7ygdXoSogNMOon9cY91Vwsslo=
> [Wed Feb 23 12:13:11 JST 2011]Authorization: 
> ***
> [Wed Feb 23 12:13:11 JST 2011]X-Twitter-Client-URL: 
> http://twitter4j.org/en/twitter4j-2.2.0-SNAPSHOT.xml
> [Wed Feb 23 12:13:11 JST 2011]X-Twitter-Client: Twitter4J
> [Wed Feb 23 12:13:11 JST 2011]Accept-Encoding: gzip
> [Wed Feb 23 12:13:11 JST 2011]User-Agent: twitter4j http://twitter4j.org/ 
> /2.2.0-SNAPSHOT
> [Wed Feb 23 12:13:11 JST 2011]X-Twitter-Client-Version: 2.2.0-SNAPSHOT
> [Wed Feb 23 12:13:11 JST 2011]Post Params: 
> with=followings&follow=6377362%2C6358482
> [Wed Feb 23 12:13:12 JST 2011]Response: 
> [Wed Feb 23 12:13:12 JST 2011]HTTP/1.1 404 Not Found
> [Wed Feb 23 12:13:12 JST 2011]Transfer-Encoding: chunked
> [Wed Feb 23 12:13:12 JST 2011]Content-Type: text/html; charset=iso-8859-1
> [Wed Feb 23 12:13:12 JST 2011]Server: Jetty(6.1.25)
> [Wed Feb 23 12:13:12 JST 2011]Unknown URL. See Twitter Streaming API 
> documentation at http://apiwiki.twitter.com/Streaming-API-Documentation
> 
> Changing the HTTP method to GET doesn't work.
> 
> What is the correct endpoint URI?
> 
> Thanks,
> -- 
> Yusuke Yamamoto
> yus...@mac.com
> 
> this email is: [x] bloggable/tweetable [ ] private
> follow me on : http://twitter.com/yusukeyamamoto
> subscribe me at : http://samuraism.jp/
> 
> On Feb 23, 2011, at 09:39 , Yusuke Yamamoto wrote:
> 
>> Hi,
>> 
>> https://stream.twitter.com/ returns self-signed certificate.
>> Any plan to fix that?
>> 
>> 
>> Thanks,
>> -- 
>> Yusuke Yamamoto
>> yus...@mac.com
>> 
>> this email is: [x] bloggable/tweetable [ ] private
>> follow me on : http://twitter.com/yusukeyamamoto
>> subscribe me at : http://samuraism.jp/
>> 
>> On Feb 23, 2011, at 07:23 , John Kalucki wrote:
>> 
>>> Note that Site Streams is still in a beta test. We're just moving endpoints 
>>> around for other projects. Sorry for any confusion.
>>> 
>>> -John
>>> 
>>> 
>>> On Tue, Feb 22, 2011 at 2:15 PM, John Kalucki  wrote:
>>> Please change your Site Streams beta clients to point to 
>>> sitestream.twitter.com and not to betastream.twitter.com. We'll continue to 
>>> support betastream.twitter.com for several weeks. This is more of a 
>>> clean-up step.
>>> 
>>> Thanks,
>>> -John Kalucki
>>> http://twitter.com/jkalucki
>>> Twitter, Inc.
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> 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
> 
> 
> -- 
> 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

Re: [twitter-dev] Re: Site Streams Beta - Endpoint change to sitestream.twitter.com

[Yusuke Yamamoto]

Hi,

Is the new endpoint https://stream.twitter.com/2b/ ? or 
https://stream.twitter.com/2/?
-- 
Yusuke Yamamoto
yus...@mac.com

this email is: [x] bloggable/tweetable [ ] private
follow me on : http://twitter.com/yusukeyamamoto
subscribe me at : http://samuraism.jp/

On Feb 23, 2011, at 07:23 , John Kalucki wrote:

> Note that Site Streams is still in a beta test. We're just moving endpoints 
> around for other projects. Sorry for any confusion.
> 
> -John
> 
> 
> On Tue, Feb 22, 2011 at 2:15 PM, John Kalucki  wrote:
> Please change your Site Streams beta clients to point to 
> sitestream.twitter.com and not to betastream.twitter.com. We'll continue to 
> support betastream.twitter.com for several weeks. This is more of a clean-up 
> step.
> 
> Thanks,
> -John Kalucki
> http://twitter.com/jkalucki
> Twitter, Inc.
> 
> 
> 
> 
> -- 
> 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

[twitter-dev] Re: Site Streams Beta - Endpoint change to sitestream.twitter.com

[John Kalucki]

Note that Site Streams is still in a beta test. We're just moving endpoints
around for other projects. Sorry for any confusion.

-John


On Tue, Feb 22, 2011 at 2:15 PM, John Kalucki  wrote:

> Please change your Site Streams beta clients to point to
> sitestream.twitter.com and not to betastream.twitter.com. We'll continue
> to support betastream.twitter.com for several weeks. This is more of a
> clean-up step.
>
> Thanks,
> -John Kalucki
> http://twitter.com/jkalucki
> Twitter, Inc.
>
>
>

-- 
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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[Tom van der Woerdt]

I just tried again (last time I tried is about 12 hours ago) and I am
getting the notifications now.

Thanks.

Tom


On 10/1/10 11:05 PM, John Kalucki wrote:
> I just verified with curl and it worked fine.
> 
> ?
> 
> -John
> 
> 
> On Fri, Oct 1, 2010 at 2:02 PM, Tom van der Woerdt  wrote:
>> I tried, but I didn't see anything. Adding a new user to one of my lists
>> didn't send anything, and removing didn't either.
>>
>> Haven't been able to test this outside my app, although I doubt that
>> it's my code (it simply outputs all incoming data to debug). Tried with
>> cURL but got an error about Basic Auth.
>>
>> Can anyone verify that there are no list events in the streams, or am I
>> simply going blind?
>>
>> Tom
>>
>>
>> On 10/1/10 10:57 PM, John Kalucki wrote:
>>> List modifications are streamed as social events. The lists themselves
>>> are not streamed.
>>>
>>> -John
>>>
>>>
>>> On Fri, Oct 1, 2010 at 11:01 AM, Tom van der Woerdt  wrote:
 Correct.

 I'd like to add an additional question to this thread: what about list
 events? The docs say that they get sent, but they don't.

 http://dev.twitter.com/pages/user_streams

 Tom


 On 10/1/10 7:46 PM, Justin wrote:
> It sounds like it's the same (NO) for both:
>
> Friendship Events
> Created - To you, from you
> Deleted - From you
>
> So, unfollow events from you not to you as the target. There doesn't
> seem to be any way to tell when someone stops following other than
> using the rest API to check followers and compare it to the list of
> following.
>
> Same with blocks:
>
> Created - From you (source)
> Deleted - From you (source)
>
>
> On Sep 30, 12:05 pm, "M. Edward (Ed) Borasky"  research.net> wrote:
>> Site Streams only or User Streams? I'm developing around User Streams.
>> --
>> M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb
>>
>> "A mathematician is a device for turning coffee into theorems." - Paul 
>> Erdos
>>
>> Quoting tsmango :
>>
>>
>>
>>
>>
>>
>>
>>> 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" >> 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

>>>
>>
>> --
>> 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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[Thomas Mango]

I'm seeing list modification events in my Site Streams. The list events 
I've seen are are list_member_added, list_member_removed and list_created.


Tom van der Woerdt wrote:

I tried, but I didn't see anything. Adding a new user to one of my lists
didn't send anything, and removing didn't either.

Haven't been able to test this outside my app, although I doubt that
it's my code (it simply outputs all incoming data to debug). Tried with
cURL but got an error about Basic Auth.

Can anyone verify that there are no list events in the streams, or am I
simply going blind?

Tom


On 10/1/10 10:57 PM, John Kalucki wrote:

List modifications are streamed as social events. The lists themselves
are not streamed.

-John


On Fri, Oct 1, 2010 at 11:01 AM, Tom van der Woerdt  wrote:

Correct.

I'd like to add an additional question to this thread: what about list
events? The docs say that they get sent, but they don't.

http://dev.twitter.com/pages/user_streams

Tom


On 10/1/10 7:46 PM, Justin wrote:

It sounds like it's the same (NO) for both:

Friendship Events
Created - To you, from you
Deleted - From you

So, unfollow events from you not to you as the target. There doesn't
seem to be any way to tell when someone stops following other than
using the rest API to check followers and compare it to the list of
following.

Same with blocks:

Created - From you (source)
Deleted - From you (source)


On Sep 30, 12:05 pm, "M. Edward (Ed) Borasky"  wrote:

Site Streams only or User Streams? I'm developing around User Streams.
--
M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb

"A mathematician is a device for turning coffee into theorems." - Paul Erdos

Quoting tsmango:








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"  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






--
Thomas Mango
tsma...@gmail.com


--
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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[John Kalucki]

I just verified with curl and it worked fine.

?

-John


On Fri, Oct 1, 2010 at 2:02 PM, Tom van der Woerdt  wrote:
> I tried, but I didn't see anything. Adding a new user to one of my lists
> didn't send anything, and removing didn't either.
>
> Haven't been able to test this outside my app, although I doubt that
> it's my code (it simply outputs all incoming data to debug). Tried with
> cURL but got an error about Basic Auth.
>
> Can anyone verify that there are no list events in the streams, or am I
> simply going blind?
>
> Tom
>
>
> On 10/1/10 10:57 PM, John Kalucki wrote:
>> List modifications are streamed as social events. The lists themselves
>> are not streamed.
>>
>> -John
>>
>>
>> On Fri, Oct 1, 2010 at 11:01 AM, Tom van der Woerdt  wrote:
>>> Correct.
>>>
>>> I'd like to add an additional question to this thread: what about list
>>> events? The docs say that they get sent, but they don't.
>>>
>>> http://dev.twitter.com/pages/user_streams
>>>
>>> Tom
>>>
>>>
>>> On 10/1/10 7:46 PM, Justin wrote:
 It sounds like it's the same (NO) for both:

 Friendship Events
 Created - To you, from you
 Deleted - From you

 So, unfollow events from you not to you as the target. There doesn't
 seem to be any way to tell when someone stops following other than
 using the rest API to check followers and compare it to the list of
 following.

 Same with blocks:

 Created - From you (source)
 Deleted - From you (source)


 On Sep 30, 12:05 pm, "M. Edward (Ed) Borasky" >>> research.net> wrote:
> Site Streams only or User Streams? I'm developing around User Streams.
> --
> M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb
>
> "A mathematician is a device for turning coffee into theorems." - Paul 
> Erdos
>
> Quoting tsmango :
>
>
>
>
>
>
>
>> 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" > 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
>>>
>>
>
> --
> 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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[Tom van der Woerdt]

I tried, but I didn't see anything. Adding a new user to one of my lists
didn't send anything, and removing didn't either.

Haven't been able to test this outside my app, although I doubt that
it's my code (it simply outputs all incoming data to debug). Tried with
cURL but got an error about Basic Auth.

Can anyone verify that there are no list events in the streams, or am I
simply going blind?

Tom


On 10/1/10 10:57 PM, John Kalucki wrote:
> List modifications are streamed as social events. The lists themselves
> are not streamed.
> 
> -John
> 
> 
> On Fri, Oct 1, 2010 at 11:01 AM, Tom van der Woerdt  wrote:
>> Correct.
>>
>> I'd like to add an additional question to this thread: what about list
>> events? The docs say that they get sent, but they don't.
>>
>> http://dev.twitter.com/pages/user_streams
>>
>> Tom
>>
>>
>> On 10/1/10 7:46 PM, Justin wrote:
>>> It sounds like it's the same (NO) for both:
>>>
>>> Friendship Events
>>> Created - To you, from you
>>> Deleted - From you
>>>
>>> So, unfollow events from you not to you as the target. There doesn't
>>> seem to be any way to tell when someone stops following other than
>>> using the rest API to check followers and compare it to the list of
>>> following.
>>>
>>> Same with blocks:
>>>
>>> Created - From you (source)
>>> Deleted - From you (source)
>>>
>>>
>>> On Sep 30, 12:05 pm, "M. Edward (Ed) Borasky" >> research.net> wrote:
 Site Streams only or User Streams? I'm developing around User Streams.
 --
 M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb

 "A mathematician is a device for turning coffee into theorems." - Paul 
 Erdos

 Quoting tsmango :







> 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"  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
>>
> 

-- 
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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[John Kalucki]

List modifications are streamed as social events. The lists themselves
are not streamed.

-John


On Fri, Oct 1, 2010 at 11:01 AM, Tom van der Woerdt  wrote:
> Correct.
>
> I'd like to add an additional question to this thread: what about list
> events? The docs say that they get sent, but they don't.
>
> http://dev.twitter.com/pages/user_streams
>
> Tom
>
>
> On 10/1/10 7:46 PM, Justin wrote:
>> It sounds like it's the same (NO) for both:
>>
>> Friendship Events
>> Created - To you, from you
>> Deleted - From you
>>
>> So, unfollow events from you not to you as the target. There doesn't
>> seem to be any way to tell when someone stops following other than
>> using the rest API to check followers and compare it to the list of
>> following.
>>
>> Same with blocks:
>>
>> Created - From you (source)
>> Deleted - From you (source)
>>
>>
>> On Sep 30, 12:05 pm, "M. Edward (Ed) Borasky" > research.net> wrote:
>>> Site Streams only or User Streams? I'm developing around User Streams.
>>> --
>>> M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb
>>>
>>> "A mathematician is a device for turning coffee into theorems." - Paul Erdos
>>>
>>> Quoting tsmango :
>>>
>>>
>>>
>>>
>>>
>>>
>>>
 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" >>> 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
>

-- 
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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[Tom van der Woerdt]

Correct.

I'd like to add an additional question to this thread: what about list
events? The docs say that they get sent, but they don't.

http://dev.twitter.com/pages/user_streams

Tom


On 10/1/10 7:46 PM, Justin wrote:
> It sounds like it's the same (NO) for both:
> 
> Friendship Events
> Created - To you, from you
> Deleted - From you
> 
> So, unfollow events from you not to you as the target. There doesn't
> seem to be any way to tell when someone stops following other than
> using the rest API to check followers and compare it to the list of
> following.
> 
> Same with blocks:
> 
> Created - From you (source)
> Deleted - From you (source)
> 
> 
> On Sep 30, 12:05 pm, "M. Edward (Ed) Borasky"  research.net> wrote:
>> Site Streams only or User Streams? I'm developing around User Streams.
>> --
>> M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb
>>
>> "A mathematician is a device for turning coffee into theorems." - Paul Erdos
>>
>> Quoting tsmango :
>>
>>
>>
>>
>>
>>
>>
>>> 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" >> 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

[twitter-dev] Re: Site Streams - Unfollow Events?

[Justin]

It sounds like it's the same (NO) for both:

Friendship Events
Created - To you, from you
Deleted - From you

So, unfollow events from you not to you as the target. There doesn't
seem to be any way to tell when someone stops following other than
using the rest API to check followers and compare it to the list of
following.

Same with blocks:

Created - From you (source)
Deleted - From you (source)


On Sep 30, 12:05 pm, "M. Edward (Ed) Borasky"  wrote:
> Site Streams only or User Streams? I'm developing around User Streams.
> --
> M. Edward (Ed) Boraskyhttp://borasky-research.nethttp://twitter.com/znmeb
>
> "A mathematician is a device for turning coffee into theorems." - Paul Erdos
>
> Quoting tsmango :
>
>
>
>
>
>
>
> > 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"  > 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

[twitter-dev] Re: Site Streams - Unfollow Events?

[tsmango]

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  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  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"  > 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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[M. Edward (Ed) Borasky]

Site Streams only or User Streams? I'm developing around User Streams.
--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

"A mathematician is a device for turning coffee into theorems." - Paul Erdos


Quoting tsmango :


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"  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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[Mark McBride]

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  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"  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

[twitter-dev] Re: Site Streams - Unfollow Events?

[tsmango]

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"  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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[M. Edward (Ed) Borasky]

As long as we're wishing, I'd like to get a notification when someone  
blocks me. ;-)

--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

"A mathematician is a device for turning coffee into theorems." - Paul Erdos



--
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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[John Kalucki]

Thanks both for your responses.

-John


On Thu, Sep 30, 2010 at 6:12 AM, tsmango  wrote:
> Hey, John. There are a few reasons I'm interested in unfollow events
> in Site Streams, but Tim got to the real point: "it would make it
> extremely easy to keep the relationship info up to date".
>
> * My service shows you the latest tweet, matching specific criteria,
> from each person you follow. Currently, unless I manually check the
> REST API every so often, I wouldn't know to stop showing you a tweet
> from someone you stopped following. With unfollow events in the Site
> Stream, this would be trivial and wouldn't require me to run a
> background process against the REST API.
>
> * I have a system in place to retrieve the relationship information
> between two people using my service. This currently hits the REST API
> to check whether or not you're following that requested person. I then
> cache that relationship information to my database and expire it after
> a certain amount of time. With only access to the REST API, there's
> always a chance my cache is out of date. Site Streams already deliver
> the full list of people being followed by each person the stream
> follows in addition to new follow events. Unfortunately, this isn't
> enough for me to stop using the REST API and expiring relationship
> details from my cache. I could keep the cache semi-updated based on
> new follow events, but I'd still need to expire that information and
> fallback to the REST API after some time. If Site Streams delivered
> unfollow events, there wouldn't be any need to fallback on the REST
> API because I'd have the full list of people being followed when the
> stream was opened and then each follow and unfollow event thereafter.
> My local cache would always be up to date and I wouldn't need to hit
> the REST API or expire any details locally.
>
> * Although I currently use a messaging type architecture for the main
> part of my service, there are certain features I'd like to implement
> that would require joining across a friendships table to find all
> tweets, matching specific criteria, by everyone being followed by the
> current user (I can't use my messaging tables because those only
> contain information for you after you start using the service and
> would prevent you from seeing any older tweets we already have
> matching that criteria). Manually keeping a user's full social graph
> synced up is wasteful and I've disabled the features in my site that
> currently require it. However, if Site Streams delivered unfollow
> events in addition to the list of people being followed by someone at
> the start of a stream as well as new follow events after the stream
> was open, keeping the user's social graph updated would be very
> efficient.
>
> For me, getting unfollow events delivered in the Site Stream means I
> would no longer have to hit the REST API for relationship details.
> Everything would be up to date and nothing in my cache would have to
> expire (unless a Site Stream was restarted, in which case I would
> clear the currently cached relationship details for each user being
> followed by that stream and set them up again).
>
> I hope this clarifies the different situations where I'd find unfollow
> events useful. Thanks!
>
> On Sep 29, 11:42 pm, John Kalucki  wrote:
>> Please describe your use case for unfollows on Site Streams...
>>
>> -John Kaluckihttp://twitter.com/jkalucki
>> Twitter, Inc.
>>
>>
>>
>> On Wed, Sep 29, 2010 at 5:09 PM, tsmango  wrote:
>> > Ah I wasn't able to find that. It's a shame if true. Thanks for the
>> > information.
>>
>> > On Sep 29, 6:05 pm, Tim Haines  wrote:
>> >> Seen this answered about 1 - 2 weeks ago.  Answer is no.
>>
>> >> On Thu, Sep 30, 2010 at 6:23 AM, tsmango  wrote:
>> >> > I was hoping for some clarification on the social events delivered to
>> >> > a Site Stream. The documentation (http://dev.twitter.com/pages/
>> >> > site_streams) doesn't specifically mention unfollow events and I'm not
>> >> > seeing them. I am seeing follow events, as expected. User Streams,
>> >> > however, are said to support both follow and unfollow events. Are the
>> >> > plans to add unfollow events to Site Streams?
>>
>> >> > Thanks, in advance!
>>
>> >> > - @tsmango
>>
>> >> > By the way, Home Timelines being delivered through Site Streams is
>> >> > really incredible. I can't wait to get this stuff into my production
>> >> > environment. Thanks, again!
>>
>> >> > --
>> >> > 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
>>
>> > - @tsmango
>>
>> > --
>> > Twitter developer documentation and resources:http://dev.twitter.com/doc
>> > API updates via Twitter:http://twitter.com/twitterapi
>> > Issues/Enhance

[twitter-dev] Re: Site Streams - Unfollow Events?

[tsmango]

Hey, John. There are a few reasons I'm interested in unfollow events
in Site Streams, but Tim got to the real point: "it would make it
extremely easy to keep the relationship info up to date".

* My service shows you the latest tweet, matching specific criteria,
from each person you follow. Currently, unless I manually check the
REST API every so often, I wouldn't know to stop showing you a tweet
from someone you stopped following. With unfollow events in the Site
Stream, this would be trivial and wouldn't require me to run a
background process against the REST API.

* I have a system in place to retrieve the relationship information
between two people using my service. This currently hits the REST API
to check whether or not you're following that requested person. I then
cache that relationship information to my database and expire it after
a certain amount of time. With only access to the REST API, there's
always a chance my cache is out of date. Site Streams already deliver
the full list of people being followed by each person the stream
follows in addition to new follow events. Unfortunately, this isn't
enough for me to stop using the REST API and expiring relationship
details from my cache. I could keep the cache semi-updated based on
new follow events, but I'd still need to expire that information and
fallback to the REST API after some time. If Site Streams delivered
unfollow events, there wouldn't be any need to fallback on the REST
API because I'd have the full list of people being followed when the
stream was opened and then each follow and unfollow event thereafter.
My local cache would always be up to date and I wouldn't need to hit
the REST API or expire any details locally.

* Although I currently use a messaging type architecture for the main
part of my service, there are certain features I'd like to implement
that would require joining across a friendships table to find all
tweets, matching specific criteria, by everyone being followed by the
current user (I can't use my messaging tables because those only
contain information for you after you start using the service and
would prevent you from seeing any older tweets we already have
matching that criteria). Manually keeping a user's full social graph
synced up is wasteful and I've disabled the features in my site that
currently require it. However, if Site Streams delivered unfollow
events in addition to the list of people being followed by someone at
the start of a stream as well as new follow events after the stream
was open, keeping the user's social graph updated would be very
efficient.

For me, getting unfollow events delivered in the Site Stream means I
would no longer have to hit the REST API for relationship details.
Everything would be up to date and nothing in my cache would have to
expire (unless a Site Stream was restarted, in which case I would
clear the currently cached relationship details for each user being
followed by that stream and set them up again).

I hope this clarifies the different situations where I'd find unfollow
events useful. Thanks!

On Sep 29, 11:42 pm, John Kalucki  wrote:
> Please describe your use case for unfollows on Site Streams...
>
> -John Kaluckihttp://twitter.com/jkalucki
> Twitter, Inc.
>
>
>
> On Wed, Sep 29, 2010 at 5:09 PM, tsmango  wrote:
> > Ah I wasn't able to find that. It's a shame if true. Thanks for the
> > information.
>
> > On Sep 29, 6:05 pm, Tim Haines  wrote:
> >> Seen this answered about 1 - 2 weeks ago.  Answer is no.
>
> >> On Thu, Sep 30, 2010 at 6:23 AM, tsmango  wrote:
> >> > I was hoping for some clarification on the social events delivered to
> >> > a Site Stream. The documentation (http://dev.twitter.com/pages/
> >> > site_streams) doesn't specifically mention unfollow events and I'm not
> >> > seeing them. I am seeing follow events, as expected. User Streams,
> >> > however, are said to support both follow and unfollow events. Are the
> >> > plans to add unfollow events to Site Streams?
>
> >> > Thanks, in advance!
>
> >> > - @tsmango
>
> >> > By the way, Home Timelines being delivered through Site Streams is
> >> > really incredible. I can't wait to get this stuff into my production
> >> > environment. Thanks, again!
>
> >> > --
> >> > 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
>
> > - @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

-
Thomas Mango
@tsmango

-- 
Twitter developer documentation and resourc

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[Tim Haines]

Favstar offers a different UI based on whether you're following someone or
not, and different services based on whether you're following @favstar or
not.  If site streams provided unfollow data it would make it extremely easy
to keep the relationship info up to date.  OneForty.com was also interested
in it..

Tim.

On Thu, Sep 30, 2010 at 12:42 PM, John Kalucki  wrote:

> Please describe your use case for unfollows on Site Streams...
>
> -John Kalucki
> http://twitter.com/jkalucki
> Twitter, Inc.
>
>
> On Wed, Sep 29, 2010 at 5:09 PM, tsmango  wrote:
> > Ah I wasn't able to find that. It's a shame if true. Thanks for the
> > information.
> >
> > On Sep 29, 6:05 pm, Tim Haines  wrote:
> >> Seen this answered about 1 - 2 weeks ago.  Answer is no.
> >>
> >>
> >>
> >> On Thu, Sep 30, 2010 at 6:23 AM, tsmango  wrote:
> >> > I was hoping for some clarification on the social events delivered to
> >> > a Site Stream. The documentation (http://dev.twitter.com/pages/
> >> > site_streams) doesn't specifically mention unfollow events and I'm not
> >> > seeing them. I am seeing follow events, as expected. User Streams,
> >> > however, are said to support both follow and unfollow events. Are the
> >> > plans to add unfollow events to Site Streams?
> >>
> >> > Thanks, in advance!
> >>
> >> > - @tsmango
> >>
> >> > By the way, Home Timelines being delivered through Site Streams is
> >> > really incredible. I can't wait to get this stuff into my production
> >> > environment. Thanks, again!
> >>
> >> > --
> >> > 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
> >
> > - @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
>

-- 
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

Re: [twitter-dev] Re: Site Streams - Unfollow Events?

[John Kalucki]

Please describe your use case for unfollows on Site Streams...

-John Kalucki
http://twitter.com/jkalucki
Twitter, Inc.


On Wed, Sep 29, 2010 at 5:09 PM, tsmango  wrote:
> Ah I wasn't able to find that. It's a shame if true. Thanks for the
> information.
>
> On Sep 29, 6:05 pm, Tim Haines  wrote:
>> Seen this answered about 1 - 2 weeks ago.  Answer is no.
>>
>>
>>
>> On Thu, Sep 30, 2010 at 6:23 AM, tsmango  wrote:
>> > I was hoping for some clarification on the social events delivered to
>> > a Site Stream. The documentation (http://dev.twitter.com/pages/
>> > site_streams) doesn't specifically mention unfollow events and I'm not
>> > seeing them. I am seeing follow events, as expected. User Streams,
>> > however, are said to support both follow and unfollow events. Are the
>> > plans to add unfollow events to Site Streams?
>>
>> > Thanks, in advance!
>>
>> > - @tsmango
>>
>> > By the way, Home Timelines being delivered through Site Streams is
>> > really incredible. I can't wait to get this stuff into my production
>> > environment. Thanks, again!
>>
>> > --
>> > 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
>
> - @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

[twitter-dev] Re: Site Streams - Unfollow Events?

[tsmango]

Ah I wasn't able to find that. It's a shame if true. Thanks for the
information.

On Sep 29, 6:05 pm, Tim Haines  wrote:
> Seen this answered about 1 - 2 weeks ago.  Answer is no.
>
>
>
> On Thu, Sep 30, 2010 at 6:23 AM, tsmango  wrote:
> > I was hoping for some clarification on the social events delivered to
> > a Site Stream. The documentation (http://dev.twitter.com/pages/
> > site_streams) doesn't specifically mention unfollow events and I'm not
> > seeing them. I am seeing follow events, as expected. User Streams,
> > however, are said to support both follow and unfollow events. Are the
> > plans to add unfollow events to Site Streams?
>
> > Thanks, in advance!
>
> > - @tsmango
>
> > By the way, Home Timelines being delivered through Site Streams is
> > really incredible. I can't wait to get this stuff into my production
> > environment. Thanks, again!
>
> > --
> > 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

- @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

Re: [twitter-dev] Re: Site streams and privacy

[M. Edward (Ed) Borasky]

Quoting jmathai :


On Aug 30, 12:59 pm, "M. Edward (Ed) Borasky"  wrote:

That's part of an application developer's responsibility - to make it  
clear what your application *does* "on behalf of a user" and how users  
can detect when it does something it *shouldn't* do. And yes, very few  
applications fully document that during the oAuth dialog, but it  
*does* need to be done somewhere.


That's more my point and I'm not arguing that the Stream API shouldn't
exist.  I want to use it myself.  I just don't believe users are
really agreeing to this regardless if it's in the fine print or not.
There's a fine line and it's being approached - that's all.

I think it's a bigger issue with OAuth as a whole.  Users don't really
know what they're handing over since it's not their username and
password.  They continue under a false pretense that their information
is still "secure" (citation needed).  I don't think more words on the
OAuth flow pages addresses this and the only way to solve this is to
educate users (not an easy task).  I hope in time users have a true
understanding of what it means to "allow this app" because right now I
don't believe they do.


Ayup - and it's only going to get worse as Twitter grows towards its  
500M user goal. For better or worse, Facebook's size and complexity is  
blazing these trails and, assuming "good will" of the power elite,  
something approaching "best practices" will emerge.


Twitter is currently both smaller and less complex than Facebook. My  
futurist lens is very cloudy on how Twitter and its user base will  
co-evolve, but I have to assume that a future 500M-user Twitter will  
be different from today's 500M-user Facebook. And I am even less  
certain how much bigger Facebook can get. ;-)


--
M. Edward (Ed) Borasky
http://borasky-research.net http://twitter.com/znmeb

"A mathematician is a device for turning coffee into theorems." - Paul Erdos


--
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?hl=en

[twitter-dev] Re: Site streams and privacy

[jmathai]

On Aug 30, 12:59 pm, "M. Edward (Ed) Borasky"  wrote:
> That's part of an application developer's responsibility - to make it  
> clear what your application *does* "on behalf of a user" and how users  
> can detect when it does something it *shouldn't* do. And yes, very few  
> applications fully document that during the oAuth dialog, but it  
> *does* need to be done somewhere.

That's more my point and I'm not arguing that the Stream API shouldn't
exist.  I want to use it myself.  I just don't believe users are
really agreeing to this regardless if it's in the fine print or not.
There's a fine line and it's being approached - that's all.

I think it's a bigger issue with OAuth as a whole.  Users don't really
know what they're handing over since it's not their username and
password.  They continue under a false pretense that their information
is still "secure" (citation needed).  I don't think more words on the
OAuth flow pages addresses this and the only way to solve this is to
educate users (not an easy task).  I hope in time users have a true
understanding of what it means to "allow this app" because right now I
don't believe they do.

-- 
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?hl=en

[twitter-dev] Re: Site streams and privacy

[jmathai]

John,

I know it doesn't introduce anything new (per my original post).

I had a hard time coming up with an example but here's the best I
could do.

When I authorize application FOO to access my account I am giving them
permission to poll for my direct messages. [Agreed]
I am also giving them permission to listen to a stream which contains
my direct messages. [Agreed]
I am also giving Twitter permission to mail them a CD every month with
all my direct messages. [Agreed]

My point is...it's not about a violation of the existing terms.  But
there is a line - which I'm sure you'd draw before mailing out CDs -
which I think the Site Stream is approaching.

I'm not opposed to the Site stream - in fact I hope to use it.  But I
also don't have much personal information on Twitter (it's generally
public - incl. DMs).  But it could be for others.

I'm sure you guys thought about it more than I have but it's worth
bringing up.

On Aug 30, 12:07 pm, John Kalucki  wrote:
> Site Streams do not change anything in the Twitter privacy model. OAuth'ed
> applications have always been able to pull your direct messages via the REST
> API.
>
> -John Kaluckihttp://twitter.com/jkalucki
> Twitter, Inc.
>
> On Mon, Aug 30, 2010 at 12:05 PM, jmathai  wrote:
> > I haven't kept up on the streaming API but read about the new Site
> > Steam and it raised some privacy concerns.  Specifically the fact that
> > direct messages would be streamed from anyone that added your
> > application.  I understand this was always possible but the stream API
> > makes it fairly trivial to collect all that data.
>
> > It's also a privacy concern because of user intent.  When someone adds
> > an application my guess is that they're not intending on saying "yes,
> > gain access to my direct messages" much less "sign up to receive all
> > my direct messages via a stream".
>
> > Anyways, the stream API is awesome...but it's important to understand
> > how users interact with applications and what their intentions are
> > when they add (regardless of what they are in fact signing up for).  I
> > also realize all of this was previously possible but by making it
> > easier it increases the chances that apps are accessing this data.
>
> > Just thought I'd bring it up for discussion :)
>
> > --
> > 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?hl=en
>
>

-- 
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?hl=en