Earlier quoted context omitted.
If you used any IMAP accounts (not from Google), you would need to enter the password. And Spark will quietly send it to "the cloud" and keep it there, with servers accessing your mail whenever they please. This is kind-of mentioned in the Privacy Policy, but in a way that wasn't clear to me at all. I found this unacceptable, so I can't use Spark, which I regret. I also lost trust for Readdle, so now, even though the…
Storing the IMAP password is basically the same as storing the Gmail OAuth token in terms of access control, not sure why you think storing one is more evil or scarier than the other. AFAIK Spark’s push notification service relies on checking for mail server-side (so that they don’t drain your battery with constant background refreshes, I suppose?), so I wouldn’t consider it sneaky.
I didn't get paid, so I open-sourced my client’s project
251–260 of 272 posts
Re: I didn't get paid, so I open-sourced my client’s project
#252Earlier quoted context omitted.
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…
Which bank implements OAuth?
(disclaimer: I work here)
Re: I didn't get paid, so I open-sourced my client’s project
#253Earlier 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…
1) Robinhood only has my routing number and account number. 2) The Cash app only has my routing number and account number. 3) PayPal only has my routing number and account number. 4) My credit card only has my bank’s routing and account number. Despite these restrictions, the world keeps on spinning round and round.
Re: I didn't get paid, so I open-sourced my client’s project
#254Earlier 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…
Re: I didn't get paid, so I open-sourced my client’s project
#255Re: I didn't get paid, so I open-sourced my client’s project
#256INAL but even if you did not get paid does not automatically means the result of work for hire belongs to you. If you are a contractor this is a smart thing to explicitly stipulate in the contract.
Also NAL, but my understanding is that if no "consideration" (something of value) changes hands, the contract is null and void. This is why people sell things for $1 instead of giving them away, or why executives take $1 salaries instead of working for free. Thus, if he really never received anything of value for the work, it's as if the contract never happened, and ownership of the IP remains with the person who cre…
Re: I didn't get paid, so I open-sourced my client’s project
#257Earlier quoted context omitted.
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 b…
There is no defensible need for anything else
Re: I didn't get paid, so I open-sourced my client’s project
#258Earlier quoted context omitted.
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…
> I honestly don't know how the banks were placated in the end. because after many years into sofort, they still couldn't provide a modern authentiation flow for external services. like openid.
Dutch banks are behind in many things, but this is not one.
Re: I didn't get paid, so I open-sourced my client’s project
#259Earlier quoted context omitted.
> 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 AGPL covers using code in servers. They would have to provide code for any server side changes.
Considering the initial unethical behavior of the client, I doubt they'll respect the AGPL license.
Re: I didn't get paid, so I open-sourced my client’s project
#260Earlier 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…