Raffi,
Tweet id is a no-brainer. We understand that an linear incrementing
number does not scale because at some point it must cycle back to 1.
Search is a different animal.
When I do a Twitter search, I expect your system to tell me what is
*happening* right now. I am NOT expecting your system
hi dewald.
we obviously feel that users want the most relevant tweets first (the
use of popular is unfortunate here). and the web interface of search.twitter.com
has begun an evolution in that direction.
it's still unclear what Twitter is going to do with the API (hence the
silence),
Raffi,
We obviously feel that users want the most relevant tweets first.
Has this been determined and confirmed with user focus groups, or is
this just an opinion that originated somewhere in a Twitter office or
meeting room?
I am one of those users, and I have just told you that I have no
But raffi why do you have to break the old to offer the new?
Basically I've just updated MyPostButler to work again after your last
unannounced changed the Thursday evening before a holiday break only to
open my email this morning and see you are going to modify search api
yet again in some
I think twitter forget that API developers are there customers as well, not end
users.
At the end of the day if this make my app unviable then you'll lose this
development community as a developer and pretty improbable to ever get us back.
I've never funded another application on the Adobe
Doesn't this always happen? Paths diverge (usually around money but
sometimes around principle) and then it gives rise to something new?
Allan Hoving
http://www.thefrequency.tv
On Tue, Apr 6, 2010 at 7:28 AM, Dewald Pretorius dpr...@gmail.com wrote:
Raffi,
Tweet id is a no-brainer. We
Dean,
sarcasm
lines
line rel=meSome developers have too much time on their hands./
line
lineSo, Twitter make these changes to give them something to do so
that they can STFU on these forums, because they are too busy chasing
the latest API mod./line
/lines
/sarcasm
On Apr 6, 10:14 am, Dean
Ha ha, love it.
I feel sorry for other developers, for me personally I can walk away from my
app at anytime as I see fit because I'm not reliant on any single project.
lol MyPostButler (or MyTwitterButler as it was known back then) was given away
for the first few months - It was just a
- Raffi Krikorian ra...@twitter.com wrote:
hi dewald.
we obviously feel that users want the most relevant tweets first (the
use of popular is unfortunate here). and the web interface of
search.twitter.com has begun an evolution in that direction.
it's still unclear what Twitter is
- Dewald Pretorius dpr...@gmail.com wrote:
Raffi,
Tweet id is a no-brainer. We understand that an linear incrementing
number does not scale because at some point it must cycle back to 1.
Search is a different animal.
When I do a Twitter search, I expect your system to tell me what
If you have no interest in seeing old tweets then pass the parameter that
indicates that you want to strictly see the most recent tweets (the legacy
behavior). You get what you want and those who are interested in more signal
amongst the ever increasing noise can find out the
But raffi why do you have to break the old to offer the new?
we do our absolute best not to do so. as i mentioned in some previous
thread - we do reserve the right to add things to the XML / JSON / etc.
outputs -- so, please make sure to have parsers that can handle that. for
me, that
We obviously feel that users want the most relevant tweets first.
Has this been determined and confirmed with user focus groups, or is
this just an opinion that originated somewhere in a Twitter office or
meeting room?
twitter does run user studies. yes.
I am one of those users, and I
On 6 April 2010 17:27, Raffi Krikorian ra...@twitter.com wrote:
our search and relevancy algorithms are constantly changing. we take in a
slew of signals like engagement or conversation around tweets, and use
that to pull it higher in search results. whether we will provide the exact
On Tue, Apr 6, 2010 at 09:31, Raffi Krikorian ra...@twitter.com wrote:
all in all - i hope a lot of you are coming to chirp, as i would absolutely
happy to have this conversation in person over some beers :P
How about orange juice for those of us who don't drink? :-P
Abraham
--
Abraham
Let's not kid ourselves. This change to relevant tweets is ad
revenue related, driven by a fear that Google will siphon off too many
search queries.
2 cents. *clink-a-ling*
--
To unsubscribe, reply using remove me as the subject.
On 04/06/2010 09:31 AM, Raffi Krikorian wrote:
all in all - i hope a lot of you are coming to chirp, as i would absolutely
happy to have this conversation in person over some beers :P
Black coffee for me, decaf if we're doing this at the hack session /
unconference ;-)
--
M. Edward (Ed)
Hey everyone,
My job title doesn't matter much. I do what I can and what needs to be done,
whether that's being a contributing programmer on upcoming platform
features, thoroughly testing an API before launch, analyzing implementations
for spec compliance, communicating to and with the developer
Taylor,
Your job title very much does matter. Any respectable public/open
API publisher needs to be concerned with the needs, wants and feelings
of their developer community. If you are part of Twitter's effort to
address this concern, then you need to be doing certain things. If you
are not,
Very well said, Andrew.
Taylor, a Developer Evangelist is supposed to be someone who is paid
by Twitter to represent the developers, speak on their behalf in
meetings and conversations, represent their interests even when those
interests are directly opposed to Twitter's, fight on behalf of the
Yikes, of course I meant to write Deveoper Advocate, and not Developer
Evangelist.
On Apr 6, 8:51 pm, Dewald Pretorius dpr...@gmail.com wrote:
Very well said, Andrew.
Taylor, a Developer Evangelist is supposed to be someone who is paid
by Twitter to represent the developers, speak on their
To be fair to Taylor, we may be expecting too much from his role.
When reading the job description of a Twitter Developer Advocate [1],
the only traditional advocate responsibility listed there is
Represent developer needs when planning new API features and
changes.
Now, if Taylor conveyed our
to clarify (from my personal view), what taylor has provided to the team is
a clear view into what developers want / think / feel -- basically, a pulse
on the developer community. he's doing a fine job. and for these
particular issues, not only has he conveyed the feelings of our community,
but
to clarify (from my personal view), what taylor has provided to the team is
a clear view into what developers want / think / feel -- basically, a pulse
on the developer community. he's doing a fine job. and for these
particular issues, not only has he conveyed the feelings of our community,
Raffi, one of the things that really stands out for me in what you are
saying here is that there are lots of moving pieces that the team is
trying to align quickly. The question is, who and what is dictating
the schedule? I get the sense that all the recent changes are parts of
a bigger picture
consider this an acknowledgement and a response, then :P
these are two pretty big issues (tweet IDs and popular tweets in search).
and the silence has been because we're working really hard behind the scenes
to make sure we, ourselves, have weighed all the options on the axes i laid
out, and we
- Raffi Krikorian ra...@twitter.com wrote:
• popular tweets in search - twitter is increasingly being relied
upon to be the place for relevant real-time information. most
end-users would say that a time indexed search stream is not as
valuable. as you all can probably tell, keeping a
27 matches
Mail list logo
