Live data from Hacker News

I didn't get paid, so I open-sourced my client’s project

github.com

81–90 of 272 posts

Re: I didn't get paid, so I open-sourced my client’s project

#81
Don’t understand why someone would throw away their integrity by doing this. When a client refuses to pay, the standard procedure is to take them to court and then make them pay what is owed + attorney fees.

Instead, this developer has put himself on industry blacklists by doing this. No way he’ll be trusted with sensitive projects. Don’t do this.

Re: I didn't get paid, so I open-sourced my client’s project

#82
post #41

This thing wants the password for your bank account? WTF? That's way more than it needs. Enough info to authorize an ACH transfer, maybe. But the login password for your bank account? No way. That voids Bank of America's security guarantee.[1] If you provide info for an ACH transfer, and the other party abuses that info, it's reversible. If you provide login info and the other party abuses that info, it's not. [1] ht…

It’s using the multi billion dollar Plaid integration.

Re: I didn't get paid, so I open-sourced my client’s project

#83
post #64

Hey guys its cool to see that you like my project. Unfortunately these types of things happen to independent contractors often and theres not a whole lot you can do about it but learn from mistakes. I used some awesome tech for the first time in this one like react-native-web which is now in Expo and react-spring for those sexy animations. Im happy for any of you guys to use this project as a boilerplate, learn some…

As a freelancer, always get a 50% upfront payment before starting a project.

I much prefer billing by hours/days with clear payment terms in the MSA, and iterative delivery,. Clients understand that if they don't pay, they're not going to get much. Project-based estimates with up-front payment probably is good for clients unfamiliar with software development processes, but I avoid projects like those.

Re: I didn't get paid, so I open-sourced my client’s project

#84
post #56

Earlier quoted context omitted.

Have you ever seen mike monteiro’s “fuck you pay me” talk? Assuming that your contract leaves you with copyright until you’re paid you could always have dmca’d them when they deployed. But that’s the vindictive side of me :D

> Assuming that your contract leaves you with copyright until you’re paid Why would this matter? If he's not paid, what validity does the contract have?

That's really a question for lawyers to answer with regards to the specific contract.

Re: I didn't get paid, so I open-sourced my client’s project

#85
post #41

This thing wants the password for your bank account? WTF? That's way more than it needs. Enough info to authorize an ACH transfer, maybe. But the login password for your bank account? No way. That voids Bank of America's security guarantee.[1] If you provide info for an ACH transfer, and the other party abuses that info, it's reversible. If you provide login info and the other party abuses that info, it's not. [1] ht…

How does Plaid work then? (https://plaid.com)

Re: I didn't get paid, so I open-sourced my client’s project

#86
post #52

Earlier quoted context omitted.

Yes, but this is increasingly common in online services. Reputable services like Wealthfront also work like this, requiring your bank login to work. The fact that Plaid has their entire business built around providing “bank logins as a service” speaks to that. I don’t like it either, but I’m not sure how you could get archaic banks and low-tech consumers to adopt something better.

Yeah, unless banks provide oAuth or APIs to get that information securely and easily revokable, I guess that's the best we have.

FAPI[0] should presumably be the way forward for Banks to do this, given the adoption actually happens at scale.

[0] https://openid.net/wg/fapi/

Re: I didn't get paid, so I open-sourced my client’s project

#87

Hey guys its cool to see that you like my project. Unfortunately these types of things happen to independent contractors often and theres not a whole lot you can do about it but learn from mistakes. I used some awesome tech for the first time in this one like react-native-web which is now in Expo and react-spring for those sexy animations. Im happy for any of you guys to use this project as a boilerplate, learn some…

How common as a ballpark percent? I’m asking because I’m trying to decide whether to try some contracting this year or not

The more you charge, the less likely it is to happen. Also, requiring some money up front before you begin weeds out many of the worst clients. Early on, it might be 10% of your clients that try to not pay. As you gain more experience, you can weed these clients out through a combination of the aforementioned things and just getting a better "feel" for when to turn down a job.

Or do like I did and end up working full-time for a client that does pay well. That brought my non-payment rate down to 0%.

Re: I didn't get paid, so I open-sourced my client’s project

#88
post #41

This thing wants the password for your bank account? WTF? That's way more than it needs. Enough info to authorize an ACH transfer, maybe. But the login password for your bank account? No way. That voids Bank of America's security guarantee.[1] If you provide info for an ACH transfer, and the other party abuses that info, it's reversible. If you provide login info and the other party abuses that info, it's not. [1] ht…

Yes, but this is increasingly common in online services. Reputable services like Wealthfront also work like this, requiring your bank login to work. The fact that Plaid has their entire business built around providing “bank logins as a service” speaks to that. I don’t like it either, but I’m not sure how you could get archaic banks and low-tech consumers to adopt something better.

and quovo. and yodlee was doing this 15 years ago.

Re: I didn't get paid, so I open-sourced my client’s project

#89
post #41

This thing wants the password for your bank account? WTF? That's way more than it needs. Enough info to authorize an ACH transfer, maybe. But the login password for your bank account? No way. That voids Bank of America's security guarantee.[1] If you provide info for an ACH transfer, and the other party abuses that info, it's reversible. If you provide login info and the other party abuses that info, it's not. [1] ht…

Yes, but this is increasingly common in online services. Reputable services like Wealthfront also work like this, requiring your bank login to work. The fact that Plaid has their entire business built around providing “bank logins as a service” speaks to that. I don’t like it either, but I’m not sure how you could get archaic banks and low-tech consumers to adopt something better.

> I don’t like it either, but I’m not sure how you could get archaic banks and low-tech consumers to adopt something better.

Laws that require banks to provide APIs so that any other service, including other banks, can consume the user's banking data.

Re: I didn't get paid, so I open-sourced my client’s project

#90
post #41

This thing wants the password for your bank account? WTF? That's way more than it needs. Enough info to authorize an ACH transfer, maybe. But the login password for your bank account? No way. That voids Bank of America's security guarantee.[1] If you provide info for an ACH transfer, and the other party abuses that info, it's reversible. If you provide login info and the other party abuses that info, it's not. [1] ht…

Well, the fact that banks traditionally allow reverting fraudulent transactions is becoming more and more of a unique selling point. So it would seem obvious that they want customers to give out their passwords so they become victims of fraud, only to then learn that the bank has excellent fraud protection (contrary to let's say cryptocurrencies). That is pure speculation of course. Hanlon's Razor would suggest "bank…

> Well, the fact that banks traditionally allow reverting fraudulent transactions is becoming more and more of a unique selling point.

Playing fast and loose with security because the bank will be on the hook (at financial cost to the bank) does not seem like a moral or ethical thing to do, and banks would be likely to pull transaction reversion from anyone who tried to use it as a feature.

Post reply on HN