31–40 of 49 posts
Earlier quoted context omitted.
Unfortunately it's all fun until Integruru or you get a cease and desist. Will Integruru support you in your legal fight in court? Most devs aren't ready to lawyer up.
You get a cease and desist letter, you cease and desist doing the stuff if you don't want / can't afford a legal fight. Then you post the cease and desist letter on your website, and post about it on hacker news.
Very risky business.
Earlier quoted context omitted.
Indeed. It also seems more like Plaid than ElcomSoft.
If this is indeed like Plaid, a simple clause in the README would put a lot of people at ease (I looked carefully for this before making my comment): This Unofficial API was built with the express written consent of Venmo (or whatever their LLC is called). It’s an easy thing to add to the README if it’s true. But if it’s not, that’s a problem.
The negativity is shocking. This is HACKER News. Elegant workarounds of limitations are usually celebrated. IMO, this should be standard procedure. If you don't want to provide the means to build greater things off of your product, expect that others will. It's a bit ironic, given that they're using open source libraries to build their product.
There’s no need to offer bad unsolicited legal advice on behalf of a mega corp. Just stop.
To everyone criticizing this project, you should probably dig a bit to find out what's the context of this project. From the integuru page: > We build integrations with platforms lacking official APIs. We specialize in low-latency integrations via reverse-engineering. All integrations are open-source. So these warnings are probably wasted on someone that is very much aware of what he is doing.
i noted this in a previous thread with them, to which they replied if its your data you can access it which ever way you like. Which is like saying i can hack into my bankers computer remotely to view my account balance. Which is still illegal.
Using unapproved apis is unauthorized access to a computer or network, illegal in the US at least, which ever way you want to try and look at it
Remember both Plaid and Aaron Swartz did this, it can end if very different ways. Obviously the government can pick and choose who to send to jail, but that’s a risk
To everyone criticizing this project, you should probably dig a bit to find out what's the context of this project. From the integuru page: > We build integrations with platforms lacking official APIs. We specialize in low-latency integrations via reverse-engineering. All integrations are open-source. So these warnings are probably wasted on someone that is very much aware of what he is doing.
I looked at the website before commenting just to be sure. Judging from the quality of the design (which, yes, I think is an appropriate way to arrive at this conclusion), I would not be surprised to find out that this is a couple recent college grads who don’t realize what this business entails.
Half of the respected users in this forum have websites like that.
To everyone criticizing this project, you should probably dig a bit to find out what's the context of this project. From the integuru page: > We build integrations with platforms lacking official APIs. We specialize in low-latency integrations via reverse-engineering. All integrations are open-source. So these warnings are probably wasted on someone that is very much aware of what he is doing.
they can try to justify it all they want, using these apis still breaks multiple federal laws i noted this in a previous thread with them, to which they replied if its your data you can access it which ever way you like. Which is like saying i can hack into my bankers computer remotely to view my account balance. Which is still illegal. Using unapproved apis is unauthorized access to a computer or network, illegal in…
Earlier quoted context omitted.
You get a cease and desist letter, you cease and desist doing the stuff if you don't want / can't afford a legal fight. Then you post the cease and desist letter on your website, and post about it on hacker news.
And everyone using the API will break. Very risky business.
The likelihood of things breaking or behaving in unexpected ways are data points I think about when assessing risk irrespective of whether an API is public or not. In some industries even the public APIs are more risky than using the unofficial Venmo API likely is.
This is actually dangerous. This is how you see spammers, scammers and grifters target people with fake bots on most platforms and the producer i.e. Venmo traces it to an SDK and will kill all these unofficial API consumers. And once captchas are introduced it's over, I wouldn't be surprised if stuff like captchas would be implemented more into websites to stop scrapers for good.
lol, not really. Captcha solving services like DeathByCaptcha and AntiCaptcha cost like $1.90 per 1,000 successfully solved captchas. They have APIs and you can easily implement them into your existing code in a few lines.
tl;dr = captchas do nothing and they also do nothing to stop scrapers. its a non-issue.
source: I scrape a lot of things and defeat captchas daily.
Earlier quoted context omitted.
Indeed. It also seems more like Plaid than ElcomSoft.
Plaid use screen scraping which is why it breaks all the time. In terms of reverse engineering undocumented but official APIs, you’re thinking of their competitor Teller.
I've personally noticed it tends to break a lot less than it used to.