Live data from Hacker News

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

github.com

201–210 of 272 posts

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

#201

Earlier quoted context omitted.

Agree that it's not the most professional look. However, the sort of client with the concern you mentioned has an NDA, IP agreement, lawyers... I don't think they'll care much. The greater risk to the contractor is that this advertises that they deal with shitty clients who don't have those things in place. Working with what sound like fly-by-night clients signals that you're not able to be picky about your work. If…

I don't know, the attention is also advertisement for himself. And HNs front page is pretty good. People say his code base is not bad, so if I would need contracting in the field right now, I would check this guy out.

feel free. you can my website through github

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

#202

Earlier quoted context omitted.

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.

On the contrary, the fact that services like Plaid are able to exist, indicates otherwise. If banks had a problem with the implementation, they would send cease and desists.

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

#203
post #103
post #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.

I agree with you, but hopefully he will do a follow-up and tell us what happens next. I guess he is hoping someone start using this project and asks him to expand or customize it.

I have some other project I'm working on now. No plans to continue with this one. I just wanted to give it away so people can learn some new stuff so my effort didnt go to waste completely

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

#204
post #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.

I don't agree with that assessment, but I do wonder why mention the client or client non-payment at all. If he wants to bother to mention the breach of contract, he should go all in and publish the client's name. Otherwise, just publish it as code written on his own time. (Which it was, at the end.)

I have no interest in exposing other people and tarnishing their names. Hes welcome to continue screwing people over if he chooses

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

#205
post #191

Earlier quoted context omitted.

That's how Mint works too last time I checked. It also wanted the BS security question answers of the type "what's your dog's favorite color?" Banks need to provide APIs, IMO.

Those questions are irrelevant, btw. It's the answers that matter, for safety. Someone could know your dog's name or mother's maiden name, but if your answers are "Doginator2000" and "Iron Maiden", you'll be safe and anyone trying to gain access will be locked out.

I just have a shitty memory, and if I game them, I won't remember what answer I gave. If I were to take that strategy I'd need to write them down, which is basically already a great sign of a terrible security policy.

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

#206
post #4

I wonder if the reverse has happened. Where a client pays for a project, and gets code, but it's terrible. So, open source it with attribution to the original developer and an appropriate README analysis of the low points. Edit: Wondering if it has happened doesn't mean I'm promoting it as a terrific idea.

that sounds like a dick move but a dev charing crap code should have that coming lol

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

#208
post #98
post #54

Earlier quoted context omitted.

I work at a bank that has a vendor that uses client credentials in order to html scrape their account pages. Most banks refuse to generate consumable methodologies for other financial services to use their data, so they go about it the hackiest way possible.

The bank has many reasons to specifically not provide that functionality. And if your value proposition as a company is to farm people's financial data for your own purposes, all I can say is tread carefully. It won't take much in terms of negative outcomes generated by increased attack surface to make bank/financial regulations even more strict. This practice is a clear violation of just about every bank I've seen's…

I don’t think it’s crazy for customers to be able to retrieve their own data.

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

#209
post #179
post #123

Earlier quoted context omitted.

If you aren't comfortable with that you better not use any fintech apps like Cash App, Venmo, Wealthfront, Robinhood, any Intuit products, etc. These services use Plaid (like this app does) or similar APIs like Quovo, Yodlee, etc. Even financial institutions themselves like Citi Bank, American Express, Chime, PayPal, etc use these APIs to link your accounts. And to be clear, the app itself never has access to your cr…

Well of course I won't use anything like that! I find it mind-boggling that people even consider giving a third party their bank account login+password. It's like saying "yes, I want to be robbed of all my money, please take these credentials and spread them forth to whichever leaked data pile they might end up in". My bank considers transactions done using login credentials to be final. There is no recourse if someo…

Interesting... I use Spark but when I authorized my gmail account I went through a Google Oauth flow, never entered my password into Spark itself.

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

#210

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…

Happened to me before so I can really feel your frustration. What I have learned, because it's not always easy to ask for 50% upfront, is to split the project into many phases and ask for payment when a phase is implemented. Hope you won't have to deal with a client like that in the future.
Post reply on HN