Can't you just make the account/verify_credentials call and get back
the stuff you need?
On Aug 26, 11:08 am, Duane Roelands wrote:
> Quitter checks for updates, and like TTYtter it always asks permission
> and you can turn it off in the configuration menu.
>
> If your users have information tha
> I disagree. By granting the application access to my account, I tacitly
> accept the fact that they can access any information that the API provides.
Fine. Do it to your users and see what they think about that. :)
--
personal: http://www.cameronkaiser.com
I agree with your disagreement. The other day I was playing with a
service that made a background. When I clicked done, I thought it
would prompt me to save the image and I would be on my own to upload
it into my account.
That is not what happened. It auto replaced my background. I also d
I disagree. By granting the application access to my account, I tacitly
accept the fact that they can access any information that the API provides.
The API returns the user's screen name every time you fetch their posts. For
crying out loud, a malicious app could go through and delete your last 320
Quitter checks for updates, and like TTYtter it always asks permission
and you can turn it off in the configuration menu.
If your users have information that you want, ask them for it.
If the information has value to you, offer something of value in
return.
On Aug 26, 11:02 am, Cameron Kaiser w
> Here's the example:
>
> 1. You download my desktop Twitter client.
> 2. You install it and authorize it to your Twitter account.
> 3. -Without your consent or knowledge-, my Twitter client sends me
> your screen name.
>
> That's unethical. If you don't think so, go ahead and code that into
>
Here's the example:
1. You download my desktop Twitter client.
2. You install it and authorize it to your Twitter account.
3. -Without your consent or knowledge-, my Twitter client sends me
your screen name.
That's unethical. If you don't think so, go ahead and code that into
your client and wa
How could using JUST the screen name -- something that twitter explicitly
provides to you -- possibliy get your application banned? I'm failing to see
how something that is readily available that Twitter provides for
identification purposes is so bad, and despite my respect for many of the
develope
Doing it without the express, explicit consent of the user is sneaky.
It's also likely to get your application banned.
If it's important to you to know who your users are, ask them to
register. But it should always be "opt-in".
On Aug 25, 11:21 pm, JDG wrote:
> I fail to see how knowing the us
I fail to see how knowing the user's screen name only is "phoning home" or a
"sneaky thing".
On Tue, Aug 25, 2009 at 16:20, Joseph Cheek wrote:
>
> I agree. I've seen a lot of resistance to user apps that "phone home"
> in the past.
>
> Joseph Cheek
> jos...@cheek.com
> @cheekdotcom
>
> mcdade
I agree. I've seen a lot of resistance to user apps that "phone home"
in the past.
Joseph Cheek
jos...@cheek.com
@cheekdotcom
mcdade wrote:
> Thanks JDG for the advice but I wrote an App, not a webapp.
>
> The program runs on the users computer and they auth, I really don't
> want to do a whole
Do what zillions of other applications do:
"Would you like to register your copy of [application name]? We
promise not to spam you or sell your email address. Registration will
ensure that you know when new versions are released and it lets us
know who's using our application!"
Is this informa
Explain why not? I've written apps that can do it. It's a matter of knowing
how to parse the user token responses. If you're using an OSS library,
you're welcome to change it to suit your needs -- it is, at its core, the
beauty of OSS.
On Tue, Aug 25, 2009 at 15:55, mcdade wrote:
>
> Thanks JDG
> I really dislike when companies put in a some
> sneaky things to get the user info without the user knowing about it.
[...]
> Twitter really should provide a method of seeing this server side
That is an interesting dichotomy.
--
personal: http://www.camero
Thanks JDG for the advice but I wrote an App, not a webapp.
The program runs on the users computer and they auth, I really don't
want to do a whole "i'm going to quietly send your info to me while
you aren't looking". I really dislike when companies put in a some
sneaky things to get the user in
This won't work for mobile/desktop apps. Any ideas for mobile/desktop
app tracking?
thanks!
Joseph Cheek
jos...@cheek.com
@cheekdotcom
JDG wrote:
> they do. when you get an access token, the screen name and their ID
> are returned to you along with the token. Use it. Store it.
>
> On Tue, Aug
they do. when you get an access token, the screen name and their ID are
returned to you along with the token. Use it. Store it.
On Tue, Aug 25, 2009 at 15:18, mcdade wrote:
>
> Bumping on this since no one answered..
>
> And i'm up to 90 users who authed now but I have no idea who they are
> sin
Bumping on this since no one answered..
And i'm up to 90 users who authed now but I have no idea who they are
since i can't search my app's name.
Twitter needs to create a way for Developers to track users who are
using the product. Look at Facebook, they have amazing tools for the
Developer
-
18 matches
Mail list logo
