Believe it or not but it requires resources to open source an internal product, especially one that may have been an experiment where some small team was able to convince leadership could become useful to the masses.
React.js at Facebook is a good example of this. It took a lot of effort to externalize and open source React, and tbh the codebase is still kind of garbage when it comes to contributions from those unfamiliar with its intricacies.
It certainly can be a cat and mouse game, but scraping at scale tends to be ahead of the curve of the security teams. Some examples:
Preventing access by requiring an account, with strict access rules can curb the vast majority of scraping, then your only bad actors are the rich venture capitalists.
I hope your resume is good clean fun, just like your meals.
I did, and I stand by what I said.
Review is both taken and given. Peer review does not occur in a single direction, it is a conversation with multiple parties. I can understand if someone misunderstood what I meant though.
As am I, it’s a two way street. You need to review the code, and have it reviewed.
A developer who is afraid of peer review is not a developer at all imo, but more or less an artist who fears exposing how the sausage was made.
I’m not saying a junior who is nervous is not a dev, I’m talking about someone who has been at this for some time, and still can’t handle feedback productively.
I used to work in the same office as sketchfab over a decade ago, founders are good people.
In a different world maybe, but I can already see the headlines, “Mozilla open sources lackluster AI tool”. PR is unfortunately a thing, and once you miss that initial wave of interest, you’re unlikely to grab attention later without another marketing push. Mozilla is experienced in open sourcing software, so by now they’re pretty good at knowing when to do it and when not to. In other words, it says something that they chose not to do it in this case.