Earlier quoted context omitted.
I thought it also prohibits commercial use, so the client would have to publish the source _and_ not sell access?
It allows commercial use. Here's more info: https://choosealicense.com/licenses/agpl-3.0/
Ah, thanks.
I didn't get paid, so I open-sourced my client’s project
91–100 of 272 posts
Re: I didn't get paid, so I open-sourced my client’s project
#92This 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
German law at least forces them to declare that they do so if they were doing that. Otherwise they would break a lot of laws. IANAL, but I believe that might actually get some people in jail.
I remeber that banks were very much opposed to that service when they started out, warning people off (against the banks ToS, grounds for sccount termination etc.) and trying to block Sofort from their servers. I honestly don't know how the banks were placated in the end.
Re: I didn't get paid, so I open-sourced my client’s project
#93Don’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.
Literally, good luck finding a real project that doesnt deal with mom&pop shops
Re: I didn't get paid, so I open-sourced my client’s project
#94Earlier quoted context omitted.
I don't see any context where it's necessarily a new, inexperienced coder.
Fine, what a terrible thing to do to an experienced coder. As an industry, we work so hard to build a culture of constructive critique via code reviews, of mentoring up new developers, of constantly improving our skills. We strive not to judge people for their code any more than we would want to be judged for our own. Naming and shaming coders because they wrote bad code is just uncool, as it fights against the aspec…
If a client has richly rewarded you for your work in good faith, is it not also a terrible thing to deliver a pile of crap? If I pay a developer thousands of dollars and the result is garbage, you can bet I’ll be judging them for it.
If I paid a photographer to take my wedding photos and they did a terrible job, am I a bad person for judging and shaming them to warn others who might be similarly conned? Or is it only developers who get the kid gloves treatment?
Re: I didn't get paid, so I open-sourced my client’s project
#95Don’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.
"we won't hire him because he will reveal sensitive data if we don't pay him"
Re: I didn't get paid, so I open-sourced my client’s project
#96This 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…
In France banks have pretty good auth and also they are obligated by law to provide API, so that you can have third parties app without ever giving your credentials.
Edit: if anyone is interested it looks like it’s an EU directive https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A...
Re: I didn't get paid, so I open-sourced my client’s project
#97Earlier 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.
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.
> I work at a bank that has a vendor that uses client credentials in order to html scrape their account pages.
Dear god
Re: I didn't get paid, so I open-sourced my client’s project
#98Earlier 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.
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 security policy. Normal practice would be to negotlate a data sharing of some sort, but that happening would be dependent on your company's ability to generate increased visibility for, or traffic to the bank.
Anyway, tread carefully
Re: I didn't get paid, so I open-sourced my client’s project
#99Don’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.
It sounds like the client abandoned the project altogether, rather than taking receipt and not paying. So it’s more like a project that was started but never finished — and now the developer is giving it away because there’s nothing else to do with it.
Re: I didn't get paid, so I open-sourced my client’s project
#100Earlier quoted context omitted.
The copyright of a work belongs to its creator by default. (That's U.S. law; no contract is required to make that happen.) A standard contract for a contractor will stipulate that the copyright will be assigned to the client upon payment. If payment never occurs, the copyright stays with the work's creator.
> The copyright of a work belongs to its creator by default. (That's U.S. law; no contract is required to make that happen.) If it meets the criteria for a work-for-hire, the contracting party is the creator from the beginning for copyright law purposes (this is significant for reasons other than those under discussion; copyright transfers can reversed by the legal creator during a legally-specified window that occur…
Without payment how can it be claimed that it was work "for hire"