Or, the first rogue Twitter app. that tweets a Tipjoy payment message
from the user who gives up their username/password to the rogue app.
It'd be a Tipjoy mugging!
At least Tipjoy lets you cancel transactions that aren't paid for yet.
But, if you pre-charge your account, and the money is sent from the
account, and the recipient has enough to cash out to a PayPal account
... before the transaction is cancelled ... what happens?
Sounds so very dangerous.
On 4/8/09 9:27 AM, Ivan wrote:
> Hi Folks,
>
> Tipjoy's Twitter Payments have been really successful for P2P and
> charitable payments. Now we've released an API for Twitter
> applications to do payments over Twitter:
> http://tipjoy.com/api
--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
This looks quite interesting. I do have one concern, though.
On the main tipjoy.com site, you have a prominent banner saying "click
here to sign up in 5 seconds without giving us your password."
...which then leads to the OAuth sign-in.
The Tipjoy API requires a twitter user/pass combo for authentication.
If I am User A who already has created an account on Tipjoy using
OAuth, and now I see another 3rd party application asking for my
twitter user/pass to interact with Tipjoy, I am going to be very
concerned that this other app is trying to scam me.
I guess it just looks like a conflicting message to me.
I know you said you are "hacking" something together for OAuth apps,
so maybe this concern is unnecessary, but wanted to give you that
feedback as a potential user of this system.
As a developer, the API looks very interesting. I don't know how many
people would actually want to tie their twitter account to actual
money transactions, but I guess there's only one way to find out...
Congrats on the API launch,
-Chad
Right, and OAuth is (at least) supposed to help curb that behavior
(imho). It does sound like you have been thinking a lot about an
OAuth solution, so thanks for that effort. I'm not knocking your API
work, I'm just in the paranoid minority :)
-Chad