Makes sense.
One thing I'm noticing that now this feature is live:
If userA and userB are both in my follow id list, and then if userA
makes an explicit reply to userB, I get userA's update twice. Just
something to be aware of for everyone.
This "duplicate update" also happens if you have the same user id
listed twice (or more) in the follow id list. I found this out by
merging two follow lists which overlapped. 'sort' and 'uniq' became
my friends soon thereafter.
-Chad
On Tue, Jun 9, 2009 at 11:24 PM, John Kalucki <jkalu...@gmail.com> wrote:
>
> Unlikely.
>
> In general, we treat a status as immutable, but removable.
> Hosebird doesn't re-write statuses.
> Clients can determine this by themselves.
> Too many other things to do!
>
> -John
>
>
> On Jun 9, 8:10 pm, Chad Etzel <jazzyc...@gmail.com> wrote:
>> Neato!
>>
>> Would it be possible to add some sort of attribute to the status
>> object which indicates when this is the case? (i.e. this update is
>> being sent to you, but the user id of the sender is not explicitly in
>> the follow id list?)
>>
>> Would be handy, perhaps.
>> -Chad
>>
>> On Tue, Jun 9, 2009 at 10:46 PM, John Kalucki <jkalu...@gmail.com> wrote:
>>
>> > The follow by userID resources, /follow, /birddog and /shadow, stream
>> > all public statuses filtered by a list of userIDs. In addition to
>> > updates created by users in the list, explicit replies now also match
>> > and are streamed to consumers.
>>
>> > Mentions, statuses that contain a given screen name ("Hello @user!"),
>> > but aren't explicit replies, are not matched.
>>
>> > -John Kalucki
>> > Services, Twitter Inc.
