|
|
|
|
|
by klohto
1858 days ago
|
|
Atleast put some effort into reading all the material if you want to shame somebody. 1) Initial email was sales pitch that did not touch the problem at all. Which retool responded to by the way. 2) CDN is hardcoded into the JS library. Why would you even do that and then shame people? If it’s against the ToS then you need people point to the ToS first. It’s the author’s fault here. 3) MIT license. How many times do we have to go through this. Retool could just fuck off but even before this witch hunt began, they were already donating. 4) Some human communication explaining the problem wouldn’t hurt. Personally I’m more likely to turn down using faker.js now. |
|
It’s worth noting that before the fakercloud.com URLs were hard-coded into the library, the library was hard-coding a different service’s S3 URLs (uifaces.co) and only stopped when they became inaccessible:
https://github.com/Marak/faker.js/commit/e45648439ff5dd9adbe...
https://github.com/Marak/faker.js/issues/1055
So it seems a little unfair to complain that Retool are embedding URLs to your CDN when this library was doing the same thing to UI Faces a few months ago.