Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

github.com

Post reply on HN
Print view View original

51–60 of 272 posts

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

#51

Post by ryan-allen »

tyingq wrote: 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.

Said client probably picked the wrong people in the first place, and if they couldn't tell then how could they tell now?

I think most small-end jobs end up going to shit for more reasons than bad code, I'm still trying to understand the whole dynamic of how it all goes to crap.

I'd also just like to add if your hypothetical was the case would said developer ever care? I doubt it, they'd just move on to the next sucker.

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

#52

Post by m-p-3 »

burlesona wrote: post #43
Animats wrote: 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.

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

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

#54

Post by textfoo »

burlesona wrote: post #43
Animats wrote: 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 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.

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

#56

Post by olliej »

trillcyborg wrote: post #37

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…

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

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

#57

Post by taormina »

kombucha11 wrote: post #38
sheeshkebab wrote: post #21

Earlier quoted context omitted.

You could - or could start without it. The code is really nothing special - relies on Plaid for processing payments and small dB to keep user profiles... it’s done well though, so could certainly build it up if this model is what you are looking for.

I'm trying to wrap my mind around what the author means by saying the value would come "from leveraging data to eventually create a rental marketplace where users can find the perfect apartment to move into."

I think the intention was that by building an audience of apartment renters, that he could pivot into a related idea with this audience.

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

#58

Post by ThePadawan »

Animats wrote: 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 "banks are too stupid to implement good auth", which, having worked both outside and inside the banking industry, I would strongly agree with.

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

#59

Post by ygra »

eecc wrote: post #48
Animats wrote: 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…

German online payment system called Sofort wants the same... ( https://www.klarna.com/sofort/ ) The instructions asked me to provide account, card number and OTP login code... then it’s just a matter of scraping all my past 10 years transactions and keep the session alive to snoop on exactly how many condoms I buy... Criminals

The idea behind the thing seems to be to initiate a wire transfer (which cannot be refunded as easily as direct withdrawal) and provides the merchant with an immediate confirmation of the same. I've never used Sofort for pretty much that reason that they want your online banking credentials and then automate stuff behind your back.

I've sometimes used giropay, though, which does the same, only directly through your bank's online banking interface. So you're interacting with your bank, not a third party; but that third party gets confirmation about the transfer. Still more of a hassle than direct withdrawal ...

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

#60

Post by OJFord »

edaemon wrote: post #24
coldtea wrote: post #15

Earlier quoted context omitted.

> whereas a license such as AGPLv3 would help ensure he'd actually get paid if this client decided it wanted to use it again. a) So would any competitor to the client. b) The client can use the AGPLv3 version gratis too, even if they modify it, as it will be on their own server anyway.

The AGPLv3 considers network use to be distribution so the client would have to publish the source. They could still use it for free, but it would have to remain open source.

I thought it also prohibits commercial use, so the client would have to publish the source _and_ not sell access?
Post reply on HN