Re: [twitter-dev] Re: Twitter buying Tweetie
If anyone would like to help withe the development of http://www.thefrequency.tv -- which integrates a focused Twitter search result feed but adds value above the social layer -- I would appreciate it. The Pulitzer Center is using the site currently. Allan Hoving On Sat, Apr 10, 2010 at 1:24 PM, Dewald Pretorius dpr...@gmail.com wrote: Nigel, Other Twitter iPhone clients are now kaput. You cannot compete with the official Twitter iPhone client, which is given away free of charge. There are quite a few valued developers who are having a very ruined day. Clients like TweetDeck and Seesmic should still be okay, because they are more general social media clients. One would be very disrespectful of the value of one's own time, if one now starts developing something that's exclusively a Twitter service. Please read what Jesse wrote. It is an extremely smart strategy. One such definition of your core might be multi social services XYZ, which would describe the core of TweetDeck and Seesmic. On Apr 10, 1:49 pm, Nigel Legg nigel.l...@gmail.com wrote: Surely all twitter developers are getting their success on the coattails of Twitter, rather than twitter getting success on the coattails of the developers? If you as a user, as a supplier to users, cannot find something that tweetie doesn't do then maybe you haven't got your ear to the ground of what twitter users want to see. My aim is to carry on with what I'm doing, and [hopefully] do it well before twitter can do it; if twitter then want to come knocking, that's up to them; if they want to replicate my service, that's up to them; hopefully I'll have enough users to survive. To me, this just ups the ante, and makes the environment just a little bit more edgy and competitive. Which is great, if you don't see the people you're competing with. Not sure how I'd feel if I was going to #chirp. On 10 April 2010 17:21, Zhami stu...@zhameesha.com wrote: On Apr 10, 11:44 am, Jesse Stay jesses...@gmail.com wrote: snip I think the more beneficial, and long-term advantageous approach is instead to make Twitter a support for your application. Spot On!! -- To unsubscribe, reply using remove me as the subject.- Hide quoted text - - Show quoted text -
Re: [twitter-dev] Re: Opt-in beta of Popular Tweets for the Search API now available
The interesting thing I'm finding is that if I try to do anything that elevates popular or relevant tweets, it causes the results to appear less dynamic, more static, less lively, more dead. And that's bad for the user experience. Allan Hoving http://www.thefrequency.tv On Wed, Apr 7, 2010 at 6:09 PM, John Kalucki j...@twitter.com wrote: I'd have to say that everyone from Twitter who posts on this list is very much a Developer Advocate and brings the concerns and viewpoints of the developer community as a whole into every meeting and decision. If there's ever an internal tension between a competing priority and the developer ecosystem, you can be assured that someone from this list will be taking the ecosystem into account, if not explicitly taking the ecosystem's side. OTOH, this is a complex system, a diverse ecosystem and a complicated business. Most choices are win-win for everyone, but sometimes there are shades of gray and there are some non-winners and sometimes even some flat-out losers. In more than a few cases I hear gripes from some devs about changes that are making other devs jump for joy. -John Kalucki http://twitter.com/jkalucki Infrastructure, Twitter Inc. On Wed, Apr 7, 2010 at 1:15 PM, Dewald Pretorius dpr...@gmail.com wrote: Jaanus, Nobody intended to be mean, and nobody put into question whether everyone at Twitter is doing a good job. As Andrew noted, it's just that the job of Developer Advocate is not being done at all. I see no malice in that. I believe it is just a misunderstanding or a lack of understanding of the role. To boil it down to the simplest of levels, an advocate is a person who pleads for a cause or propounds an idea. Hence, a developer advocate speaks, pleads, or argues in favor of developers, particularly when their needs, wishes, desires, or interests diverge from the needs, wishes, desires, or interests of Twitter. On Apr 7, 12:22 am, Jaanus jaa...@gmail.com wrote: My oh my, what discussion about advocacy and what not. I think Taylor, Raffi and everybody else from Twitter are doing a great job here and everyone is eager to learn and they know they have ways to go. Let's not get mean. I'm with those who say injecting popular searches into the search API results by Twitter still doesn't entirely make sense, given the way the rollout/communication is handled. Here is the problem/conversation in a nutshell: Twitter: We are going to inject popular search results into the search API results, changing previous behavior that just returned recent results. Developers: Wait a sec, this is a bad idea because of A, B and C. Maybe you can version the API better or some such. ... time passes, nothing happens ... Twitter: Hi, we're starting to roll this out now. I don't particularly care for the popular results either way and I trust Twitter that it is good for users in the grand scheme of things, but the API behavior change is disturbing. It would be great to work against a fixed API target so that those who want search to work in a particular way can just work against a given API version, but with search, this is not an option, you only have one endpoint that's in this kind of flux. What I'm saying is Twitter as a company could just earn more developer street cred and respect here by handling this in a more graceful way. There comes a point in time where the moving parts argument as an excuse to not follow good API practices gets somewhat old. rgds, Jaanus -- To unsubscribe, reply using remove me as the subject.
Re: [twitter-dev] Re: What Exactly is a Developer Advocate? (was Re: Opt-in beta of Popular Tweets for the Search API now available)
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 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 to tell me what is *popular* right now. This popular tweet thing is diluting and violating your entire mission of real-time. If I search for earthquake I want to see what is *happening* in real- time. I have no interest in seeing a 30-minute old tweet from @aplusk or @ev just because they are trusted accounts and the tweet is being retweeted a lot (to simplify the popularity algorithm). If people have a need to see popular tweets, you know what? That is an ideal service to be provided by a third-party developer/service. Twitter is real-time, and has defined real-time information. Stick to it. Don't dilute your mission. On Apr 6, 1:03 am, Raffi Krikorian ra...@twitter.com wrote: we have the developer advocate we want, but, of course, please feel free to reach out to taylor with your concerns and what you would like him to do to help you all out. i'm sure he would welcome the help. as for what's going on behind the scenes, i'll describe it out as so: - tweet ID generation - this is a pure scalability problem that lays at the heart of twitter being able to grow. unless i'm mistaken, in the end, a centralized way of generating tweet IDs that are strictly increasing by one does not scale. the method that we generate tweet IDs, and therefore the IDs themselves, will, almost probably, have to change. - 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 real time search index operational is hard enough, but imagine keeping a service running that is simultaneously delivering relevant results along with time indexed results. that's significantly harder. those are the issues facing us. as i said, please bear with us -- once we have weighed all these issues internally, we will of course, let everybody know. we've heard the concerns, but, if there are new ones, please let us know! On Mon, Apr 5, 2010 at 8:28 PM, Orian Marx (@orian) or...@orianmarx.com wrote: 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 plan for Twitter, but the reality is that Twitter HQ has not conveyed a real sense of this bigger picture to the developer community - and it certainly hasn't conveyed why these recent changes need to align quickly. So inevitably the situation at hand seems to be that some serious developer concerns effectively need to be pushed aside in order to meet some internal goals of Twitter that have not been made public. I can understand that as a choice that Twitter management might make. What I think would be unreasonable would be for Twitter to expect the developer community to not push back. I think it's pretty clear that the developer advocate concept needs to be fleshed out more, and i'll try to push for that at Chirp. If anyone else is interested in helping make that discussion productive, lets get started :-) On Apr 5, 8:45 pm, Raffi Krikorian ra...@twitter.com wrote: 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 everybody on the team has also heard it personally. i hope we have more to say about both these topics soon. as you can all imagine, there is a myriad of moving pieces that we are all trying to get to align quickly -- there are technical issues, there are the concerns of our developer and user community, and then, of course, there are the overall objectives of Twitter, Inc. getting them all to align is, at times, ridiculously difficult. On Mon, Apr 5, 2010 at 5:01 PM, Dewald Pretorius dpr...@gmail.com wrote: To be fair to Taylor, we may be expecting too much from his role. When reading the job description
Re: [twitter-dev] Re: Introduce yourself!
Hi, Allan Hoving created pdfchecker.com, paycheckr.com, forthcoming podposter app master's project at quinnipiac is http://www.thefrequency.tv On Thu, Apr 1, 2010 at 12:34 AM, Mr Blog mrblogdot...@gmail.com wrote: Hi Folks, David Beckemeyer here, founder of BDT.COM, SF Bay Area ISP and consulting firm during in the 80's - 90's and founding CTO of EarthLink 1995-2005. http://www.bdt.com/david/index.html http://www.linkedin.com/in/davidbeckemeyer Twitter mashups include Taglets.org and Twitmart.org (which is under a re-design/restart phase). -- To unsubscribe, reply using remove me as the subject.
