On Tue, Mar 31, 2009 at 5:48 PM, Andrew Badera and...@badera.us wrote:
And there's no reason in the world to expose this list to people who
aren't making API calls -- period!
This line suggests that you should be currently developing an app (thus
making API calls) to access this list, which
Perhaps it may be possible to have some kind of community agreement on
a don't Tweet meta-character. Obviously this would be usless for
bots that didn't follow the request but would be a start.
On Mar 29, 11:23 pm, Chad Etzel jazzyc...@gmail.com wrote:
Hi All,
Wondering what everyone's
On 4/1/09 5:51 PM, rhysmeister wrote:
Perhaps it may be possible to have some kind of community agreement on
a don't Tweet meta-character. Obviously this would be usless for
bots that didn't follow the request but would be a start.
Maybe it wasn't a popular meme, but does anyone remember this
Chad,
As per our collective observations, I'm going to start better moderating
posts from new users. This includes heading off basic requests for
information that is already widely available before it goes public. I will
work to point users to posts, the FAQ, offering answers, etc... and avoid
HI Doug,
I have 2 comments here:
1) I think ChazziousJadamous's initial request was more along the lines of
how can we prevent scraping/feeds of this content to allow developers more
liberty in posting so there are fewer instances of posts showing up all over
the web Like, I would love a place
Peter,
You are indeed correct, and the post has deviated. Chad, the only answer to
your initial request is to connect with respected developers off list (
twitter.com is a good choice) and ask for their opinion. The open nature of
the list, and syndication feeds, promote collaboration. The classic
The way I see it now (or at least in the recent past), this board has
been mainly used for asking how to get a source parameter, basic
how-to-get-started type questions, and reporting twitter service
outages or glitches that the twitter team are probably already
painfully aware of. I know
I don't think anyone is suggesting the documentation become closed, by any
means. I think there is simply a desire to reduce the noise and exposure on
the developer channel. And there's no reason in the world to expose this
list to people who aren't making API calls -- period!
On Tue, Mar 31,
On Mon, Mar 30, 2009 at 8:58 AM, Clint Shryock cts...@gmail.com wrote:
How then would you propose acceptance to this group is determined?
I don't know, that's why I'm asking. I've never admin'd a google group before.
I think
it's in Twitter's best interest to allow information on their API
Chad: what you state IS quite desirable, but is, unfortunately, equally not
feasible.
You can moderate join requests, you can moderate members' posts, but the
distinction you seem to be looking for in your original email is
near-impossible to establish.
Perhaps membership to the list should be
Chad,
A number of people have asked on- and off- list where they should display
their app and ask for feedback. Do you think that a separate group for
feedback and suggestions for workable apps would be beneficial?
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Mon, Mar 30, 2009
On Mon, Mar 30, 2009 at 1:02 PM, Andrew Badera and...@badera.us wrote:
Chad: what you state IS quite desirable, but is, unfortunately, equally not
feasible.
You can moderate join requests, you can moderate members' posts, but the
distinction you seem to be looking for in your original email
Doug,
This forum is the appropriate place to bring up questions about the API,
regardless if you have an application in development. Therefore, please
don't feel like you cannot speak up just because you don't have code you can
show off. Chances are if you have a question, so do other developers.
On Mon, Mar 30, 2009 at 1:38 PM, Doug Williams d...@twitter.com wrote:
Chad,
A number of people have asked on- and off- list where they should display
their app and ask for feedback. Do you think that a separate group for
feedback and suggestions for workable apps would be beneficial?
If
What I would like to do is make the basic information much more accessible,
which would ensure that the more fundamental questions are answered
implicitly while the conversation can cultivate around more productive
topics. The link to the FAQ doesn't curb the thrice weekly request for
source
Let's please keep this list focused on developers working with/on the
twitter api... other uses, like the promotion of application or looking for
help with alpha testing of applications is not appropriate (though we can
sympathize with the problem).
RE: doug's question about making 'basic
16 matches
Mail list logo
