whit537

33 ms·

1. 361.▲
   by whit537 14y ago

   Thanks, Dave, lots of good pointers. I made these new Gittip issues based on your posts: use a fraud detection service: https://github.com/whit537/www.gittip.com/issues/357 detect and prevent botnets: https://github.com/whit537/www.gitti
2. 362.▲
   by whit537 14y ago

   I started a GitHub issue to track this for Gittip: "use a fraud detection service" https://github.com/whit537/www.gittip.com/issues/357
3. 363.▲
   by whit537 14y ago

   Thanks, I started a ticket for this: https://github.com/whit537/www.gittip.com/issues/357
4. 364.▲
   by whit537 14y ago

   Would you like to implement it? https://github.com/whit537/www.gittip.com/issues/14
5. 365.▲
   by whit537 14y ago

   The problem with hiding heuristics is that false positives get squished. I want to avoid the horror stories we hear about people getting their Google account shut off or their PayPal funds withheld.
6. 366.▲
   by whit537 14y ago

   Thanks Brandon! Great info. If you see a way for Sift Science to add value to Gittip then I'm open to a proposal. Balanced won our business by stepping forward and contributing the integration themselves: http://blog.gittip.com/post/283519
7. 367.▲
   by whit537 14y ago

   Right. https://en.wikipedia.org/wiki/Money_laundering I changed the blog post and GitHub issue to not refer to money laundering anymore.
8. 368.▲
   by whit537 14y ago

   Well, this thread just took a turn for the ... wow.
9. 369.▲
   by whit537 14y ago

   I want to explore openness wrt fraud prevention, not out of a facile rejection of "security through obscurity," but as part of Gittip's identity as an open company. It's accepted doctrine that "information asymmetry is probably your only ad
10. 370.▲
    by whit537 14y ago

    For the record, I've been waiting and watching for this to happen. It did happen sooner than I expected, however. Not sure if that means Gittip has grown faster than I expected, or our Jokers are earlier to adopt than I expected. ;^)
11. 371.▲
    by whit537 14y ago

    Sure, what's your Gittip? :^P
12. 372.▲
    by whit537 14y ago

    There were two primary factors, not three. And the point is that I'm planning to individually review and whitelist all new accounts. I'm able to adapt my heuristic in real time. ;^)
13. 373.▲
    by whit537 14y ago

    Fair enough. "Some" money coming into Gittip from stolen cards is in fact going out into bank accounts, some of them belonging to "innocent people" (myself included)--but some of them not. Theft, strictly defined, is in fact taking place. e
14. 374.▲
    by whit537 14y ago

    Thanks, good info. My plan at this point is to whitelist accounts, because I want to try to keep from charging suspicious accounts in the first place.
15. 375.▲
    by whit537 14y ago

    Thank you, good info. For privacy reasons, we've been hoping to not track IP addresses: https://github.com/whit537/www.gittip.com/issues/345 Even then, I'm not sure I would trust this approach. I feel much more comfortable white-listing a
16. 376.▲
    by whit537 14y ago

    Thanks for weighing in. I'm based in the US. I am going to proceed along the path of openness for now.
17. 377.▲
    by whit537 14y ago

    Sure. And yet from Gittip's POV as well as that of the original victim, it's still stolen money, on Gittip. No?
18. 378.▲
    by whit537 14y ago

    > That's only true until you start getting chargebacks. Phew. I'm saved from the moral burden by the financial burden. :^)
19. 379.▲
    by whit537 14y ago

    Informative, thank you both. On this ticket we discussed why Gittip isn't the best system for extracting value from a card: https://github.com/whit537/www.gittip.com/issues/329 The desire to verify stolen cards with the added benefit of r
20. 380.▲
    by whit537 14y ago

    @heathanderson?
21. 381.▲
    by whit537 14y ago

    I read up on money laundering, and changed the blog post to talk about "stolen money" instead. Thanks.
22. 382.▲
    Let's Apply for a Shuttleworth Fellowship(blog.gittip.com)

    1 points by whit537 14y ago|0 comments
23. 383.▲
    Status Report, and Priorities for Fall 2012(blog.gittip.com)

    1 points by whit537 14y ago|0 comments
24. 384.▲
    Defining Gittip's Scope(lyndsysimon.com)

    2 points by whit537 14y ago|0 comments
25. 385.▲
    A concise and limited query syntax for constructing MongoDB queries.(bitbucket.org)

    1 points by whit537 14y ago|0 comments
26. 386.▲
    by whit537 14y ago

    We just started adding Twitter support two weeks ago, so we're just getting started with non-programmers. Here's a few early adopters I'm aware of: https://www.gittip.com/joshuasven/ https://www.gittip.com/eriiicam/ https://www.gittip.
27. 387.▲
    by whit537 14y ago

    Hey, whoa, easy tigers! Yes, Gittip needs to solve the non-US payouts problem, and yes, Gittip can and should work for people in many different parts of the world with many different standards of living.
28. 388.▲
    by whit537 14y ago

    I think people would notice what Developer A is doing, and stop tipping him.
29. 389.▲
    by whit537 14y ago

    No. If anyone does, it'd be Balanced, our payment processor. Here's the Gittip ticket about this: https://github.com/whit537/www.gittip.com/issues/279
30. 390.▲
    by whit537 14y ago

    Yeah, the weekly rhythm has been a serendipitous boon to Gittip's growth. Definitely something to consider when building something.