Re:Google Algorithm Leaked
by lambdaxyzw on Wednesday May 29, 2024 @09:02PM
(#40519010)
>published alongside a copy of the Apache 2.0 license (intended for the document warehouse API SDK), which officially sanctioned freely copying and using the code. So there is really nothing Google can do about it.
This sounds good to us, tech nerds, but I'm pretty sure law doesn't work like this.
At minimum, even if (clearly accidentally) putting a code next to a open source license world be legally binding, the person doing the leaking was not the intellectual property owner. Google will just - correctly - say, that the person that leaked the code had no right to do so, especially under free license.
Re:Google Algorithm Leaked
by natpalmer1776 on Wednesday May 29, 2024 @10:04PM
(#40519384)
To continue this train of thought, what is stopping a company from saying "This team did not ask for permission before they published XYZ under this license" and just rescinding access to a widely used library?
At what point can you no longer say "oopsie" ?
Re:Google Algorithm Leaked
by bqmjjx0kac on Wednesday May 29, 2024 @11:41PM
(#40519851)
The law is JIT. We don't need an answer now, just ask a judge when it happens.
Re:Google Algorithm Leaked
by natpalmer1776 on Thursday May 30, 2024 @10:38AM
(#40524317)
The law is JIT is honestly the best computer-nerd analogy for legal precedent I've ever heard.
This has been fixed, but the commit and all it’s changes are out there—and tragically, published alongside a copy of the Apache 2.0 license (intended for the document warehouse API SDK), which officially sanctioned freely copying and using the code. So there is really nothing Google can do about it.
[1] https://ipullrank.com/google-algo-leak