Skip to content
This repository has been archived by the owner on Nov 16, 2022. It is now read-only.

Core Radar 85 #890

Closed
gratipay-bot opened this issue Nov 13, 2016 · 31 comments
Closed

Core Radar 85 #890

gratipay-bot opened this issue Nov 13, 2016 · 31 comments

Comments

@gratipay-bot
Copy link

gratipay-bot commented Nov 13, 2016

← Core Radar 84


🌻 Docs πŸ’ƒ Org Chart πŸ’ƒ Roadmap πŸ’ƒ Projects 🌻

@chadwhitacre
Copy link
Contributor

Laundry 1, Inbox 1, H1GHS 31, L2 Support 0, Vendors, etc. 1, Pipedrive 2.

@chadwhitacre
Copy link
Contributor

Oooooooooh ...

screen shot 2016-11-14 at 9 45 03 am

Aaaaaaaaaaaah!

screen shot 2016-11-14 at 9 44 46 am

@chadwhitacre
Copy link
Contributor

Hmm ... where is Paul's Queue? Not in gratipay.com.

https://github.com/gratipay/inside.gratipay.com/projects

screen shot 2016-11-14 at 7 02 51 pm

@chadwhitacre
Copy link
Contributor

@chadwhitacre
Copy link
Contributor

@mattbk @techtonik How about moving your queues from IG to global? I think we should only have global projects, so we only have one place to look.

@chadwhitacre
Copy link
Contributor

Laundry 0, Inbox 2, H1GHS 23, L2 Support 0, Vendors, etc. 1, Pipedrive 0.

@mattbk
Copy link
Contributor

mattbk commented Nov 15, 2016

How about moving your queues from IG to global?

That works. https://github.com/orgs/gratipay/projects/3?fullscreen=true

@chadwhitacre
Copy link
Contributor

I've revised the Twitter bio for the Gratipay account from:

Gratitude? Gratipay! Payments and payouts for open work.

to:

Gratitude? Gratipay! We help companies sustain the open source ecosystem they depend on.

I've also made a LinkedIn profile for Gratipay (with a support request filed for /company/Gratipay), in addition to dusting off my personal profile. Advice from Anton under #867 (comment) was "You have to have 500+ connections for people to know you're serious." Working on it! :-)

@chadwhitacre
Copy link
Contributor

Got a couple chargebacks ...

@chadwhitacre
Copy link
Contributor

Inbox 3, Sentry 8, H1GH 0, L2 Support 0, Vendors, etc. 3, Pipedrive 1.

@chadwhitacre
Copy link
Contributor

@mattbk I've added you to the Payday Runners team, so that you have access to the violations repo. Pinging you over there ...

@chadwhitacre
Copy link
Contributor

So! Turns out that we had a fraudulent user social engineer us. We marked them suspicious, but then they contacted support, and we unmarked them. We now know they're suspicious because we got hit with a chargeback. What can we learn from this? :-)

@chadwhitacre
Copy link
Contributor

One immediate take-away is that @mattbk needs access to the violations repo so he can be aware of and participate in fraud review. We need to cross-pollinate.

@chadwhitacre
Copy link
Contributor

Is there something we can tweak in one of our howtos to address this?

@chadwhitacre
Copy link
Contributor

I'm gonna go pick up some dinner and then I should have another hour or two of work in me before pumpkin time. I'm vacillating between zooming out and working on the roadmap, and diving in on gratipay/gratipay.com#4117.

Anyone particularly interested in a roadmap update?

@chadwhitacre
Copy link
Contributor

The silence is deafening. :-)

gratipay/gratipay.com#4117 it is! πŸ’ƒ

@chadwhitacre
Copy link
Contributor

I'm diggin' the queue. :)

@mattbk
Copy link
Contributor

mattbk commented Nov 17, 2016

What can we learn from this? :-)

I should have looked at the GitHub profile that was attached. No activity there = looks suspicious! As a suspicious bonus, the GitHub join date was the same day this user signed up to give on Gratipay.

Part of this I think was my misunderstanding of how a ~user giving money could defraud anyone. I understand better now.

@chadwhitacre
Copy link
Contributor

Live and learn. :-)

Check out the Delpan Incident for where we had our first run-in with fraud, and introduced the "suspicious" flag in the first place.

Did you ask me why I had marked them suspicious, and I missed that?

@chadwhitacre
Copy link
Contributor

I did notice some talk of a user writing in about being marked suspicious (I think it manifested in a ticket about emailing users when we mark them such, ya?). I probably should've noticed that as a red flag and investigated further. Sorry. :-/

@mattbk
Copy link
Contributor

mattbk commented Nov 17, 2016

Did you ask me why I had marked them suspicious, and I missed that?

Nope. Will do in the future.

@mattbk
Copy link
Contributor

mattbk commented Nov 17, 2016

@mattbk I've added you to the Payday Runners team, so that you have access to the violations repo

This will help me immensely. I see now that review tickets are a thing (and even explained at http://inside.gratipay.com/howto/review-accounts)!

@chadwhitacre
Copy link
Contributor

Cool. Sorry for not doing that sooner! :-/

@chadwhitacre
Copy link
Contributor

Alright, lessee here ...

@chadwhitacre
Copy link
Contributor

I'm going to spend some time with the roadmap, I think ...

@aandis
Copy link

aandis commented Nov 17, 2016

No payday? It's Friday already 😳

cc: @clone1018

@clone1018
Copy link
Contributor

Yeah, definitely forgot. Oops! Still thursday here and banks aren't closed anywhere in the US so running!

@clone1018 clone1018 mentioned this issue Nov 17, 2016
15 tasks
@chadwhitacre
Copy link
Contributor

Turns out that we had a fraudulent user social engineer us.

Update: they've now offered to deal us in. πŸ™„

We can cooperate in this direction for profit. I'm share with you very good percentage.

It's fully securely for your company. No chargebacks or something else.

Let me know please if you interested. Thanks.

We are ignoring them.

@chadwhitacre
Copy link
Contributor

Inbox 2, Sentry 8, H1GH 0, L2 Support 0, Vendors, etc. 1.

@clone1018
Copy link
Contributor

@whit537 How can I learn more about the user? Is it related to https://github.com/gratipay/violations/issues/32

@chadwhitacre
Copy link
Contributor

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants