Hi there,
I looked into this a bit and it looks like non-admins are not
seeing the field. Hoping I can make Google Code play ball, otherwise
I'll keep doing the triage comments.
— Matt
On Feb 23, 2009, at 12:17 PM, Chad Etzel wrote:
On Mon, Feb 23, 2009 at 3:13 PM, Alex Payne <[email protected]> wrote:
Just start typing?
Eh? I don't see an option to choose between "Enhancement" or "Defect"
either when creating a new issue. Is it hiding somewhere?
-Chad
On Mon, Feb 23, 2009 at 11:44, iematthew <[email protected]
> wrote:
Just curious, but how does one go about setting the type of an issue
in the bug/feature request system? I haven't seen any option for
doing
so, so my "Enhancement" gets entered as a "Defect".
On Feb 23, 2:39 pm, iematthew <[email protected]> wrote:
Yes, there are more important things. But for future planning and
keeping things clean, I think it would be a good thing to have. For
apps that cache Twitter users and have tons in their system,
requesting updates on each user can be resource-consuming, not to
mention whitelist-consuming.
A features request has been submitted as suggested:
http://code.google.com/p/twitter-api/issues/detail?id=311
On Feb 23, 2:11 pm, Alex Payne <[email protected]> wrote:
Yes, please do:http://code.google.com/p/twitter-api/issues/entry
On Mon, Feb 23, 2009 at 09:28, jstrellner
<[email protected]> wrote:
I second this, it would be useful. Although, if you are
requesting
info for that user, Twitter should be returning that the user no
longer exists, and your app should remove them.
Your solution would be good for bulk cleans, but incremental
would
probably be more efficient.
So while it would be useful, I'm not sure its required. I'll
vote 1/2
of a +1, as it would be nice to have available, but here are more
important things.
Maybe you should add it to their API feature request site?
iematthew wrote:
I haven't seen anything on the group or otherwise for a basic
house-
cleaning method for getting a list of suspended/canceled/deleted
Twitter accounts. As our Twitter apps continue to grow, having
methods
for clearing out the dead wood from our systems would be quite
useful.
I don't think anyone wants to end up a few years down the road
with a
million non-existent Twitter accounts in their system, and I
don't
think it helps Twitter to have traffic coming back to them for
accounts that no longer exist.
What I propose is a simple method for grabbing the Twitter IDs
of
those accounts which have been permanently removed. If we
could have
returned an array of these ids (much the same as the new
Social Graphs
methods return only the IDs of a user's friends or followers)
it would
help us all keep our systems clear of these defunct accounts.
Perhaps
options for a since_id or since_time would also be useful so
we only
get the IDs we haven't already cleared out.
Thoughts on this?
--
Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x
