On May 31, 6:57 pm, kylel...@gmail.com kylel...@gmail.com wrote:
I completely agree with some type of blocking for specific apps. It
kills me that I am dealing with the annoyance of Facebook on Twitter.
Twitter... please for the love of God. Save us from spymaster.
@kyleplacy
Isn't it
Sorry, but I still cant agree on why asking for a API key on the normal API
cannot solve this. A whole application can be banned/throttled/controlled
using the API key if needed this way. At present applications register and
gets API keys anyway, so all this will do is add an extra layer of
agreed, I'd like this as well.
On May 31, 6:52 pm, Jesse Stay jesses...@gmail.com wrote:
Not going to name names, but there are a few really noisy apps out there
right now. It would be really nice if, via either the API (my preference as
it would be less work on your part and fits well with
Floated the idea. Until we funnel everyone through OAuth (that means no
Basic Auth) this really isn't possible. It's something we'll keep in our
back pockets for the long-term.
Great suggestion though, Jesse.
Cheers,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On
Chad is correct. Until we have everyone pushed through a funnel where API
keys are required or applications can be deduced (as with OAuth) we have no
way of knowing which application actually sent an update or DM in some
cases. Furthermore, we don't have the notion of tweet level spam reporting.
But how would the blocked app work out the API key for TweetDeck unless
TweetDeck makes their private API key public?
2009/6/2 Chad Etzel jazzyc...@gmail.com
--
cashflowclublondon.co.uk
(`-''-/).___..--''`-._
`6_ 6 ) `-. ( ).`-.__.`)
Thanks for considering this Doug. I figured it probably wouldn't be
possible until 100% OAuth was in place, but at least the idea's out there.
Looking forward to when that happens!
@Jesse
On Tue, Jun 2, 2009 at 2:11 PM, Doug Williams d...@twitter.com wrote:
Chad is correct. Until we have
We have source blocking built into our service :)
On Jun 1, 3:52 am, Jesse Stay jesses...@gmail.com wrote:
Not going to name names, but there are a few really noisy apps out there
right now. It would be really nice if, via either the API (my preference as
it would be less work on your part
I second this request. Ideally via both web and API, API being
immediate and web when your UI guys can get to it.
On May 31, 2009, at 3:52 PM, Jesse Stay jesses...@gmail.com wrote:
Not going to name names, but there are a few really noisy apps out
there right now. It would be really nice
I completely agree with some type of blocking for specific apps. It
kills me that I am dealing with the annoyance of Facebook on Twitter.
Twitter... please for the love of God. Save us from spymaster.
@kyleplacy
On May 31, 6:52 pm, Jesse Stay jesses...@gmail.com wrote:
Not going to name names,
Interesting idea Jesse. I'll float this idea internally tomorrow and get
some feedback.
Thanks,
Doug
--
Doug Williams
Twitter Platform Support
http://twitter.com/dougw
On Sun, May 31, 2009 at 3:57 PM, kylel...@gmail.com kylel...@gmail.comwrote:
I completely agree with some type of blocking
11 matches
Mail list logo
