Every part of this is genuinely funny. Viktor launching basically OpenClaw for slack (because claw is MIT so yolo let's go mac some monnney and PJ outta Dubai etc etc). Some guy getting all their source code just by asking Viktor for it. Then rebuilding their core in a couple days because there's basically nothing there. push MIT to Github. TeamViktor's faces surely? But they're busy diamond handsing all the way to the moon so probably don't even care. XD
(I don't know anything about OpenClaw and on a deeper level, I don't wish to learn about it either considering all the security implications that it generally has)
There are gonna be some really interesting legal decisions to read in the coming years, that’s for sure…
---
The rest of this comment is irrelevant, but leaving for posterity, I had the wrong Viktor - it's getviktor.com not viktor.ai:
Edit: this one particularly interesting to me as both parties are in the EU. VIKTOR.ai is a Dutch company and the author of this post is Polish.
The ToS for Viktor.ai include the following fun passages:
> 18.1. The Agreement and these Terms & Conditions are governed by Dutch law and the Agreement and these Terms & Conditions will be interpreted in accordance with Dutch law.
18.2. All disputes arising from or arising in connection with the Agreement and/or the Terms & Conditions will be submitted exclusively to the competent court in Rotterdam, The Netherlands.
7.3. The Customer is not permitted to change, remove or make unrecognizable any mark showing VIKTOR's Intellectual Property Rights to the Software. The Customer is not permitted to use or register any trademark or design or any domain name of VIKTOR or a similar name or sign in any country.
8.5. The Customer may not cause or allow any reproduction, imitation, duplication, copying, sale, resale, leasing or trading of the Services and/or the Software, or any part thereof.
Terms of service might matter more for terminating that user account. Whole ordeal is just plain copyright violation. The author had no licence to that internal code, and whitewashing it with LLM will achieve nothing. That case is much clearer than that recent GPL->BSD attempt story.
If LLM-generated code isn't considered a derivative work of the original, then whether the author was licensed to use the code doesn't matter. But I'm sure the courts will rule in favor of your view regardless. Laundering GPL is in corps' interest and laundering their code is not.
I think it comes down to the company's appetite for legal action, doesn't it? This case is imo pretty clear but the vibe has quite the smell of Oracle v Google to me.
But, yeah. More than likely this case is a simple account termination and some kind of "you can't call your clone 'openviktor'" letter.
It's also disingenuous to call it open source as that might tempt others to use it believing that it actually is open source.
Let's call it what it is - stolen IP and released without permission of the author. Sure, it's good that it opens the debate as to whether that's ethical given that's essentially what the model itself is doing, but it's very clear in this instance that he's just asked for and been given a copy of source that has a clear ownership. That's about as clear cut as obtaining e.g. commercial server-side code and distributing it in contravention of the licence.
It's not completely clear that this is the original source. According to the post it's a reimplementation based on documentation created from the original source, or perhaps from developer documentation and the SDK. Whether that's the same thing from a legal standpoint, I don't really know - I think from a personal morality standpoint it's clear that they are the same thing.
I could do the same thing but not publish it, still getting the value of their product without legal concerns. Now, what happens when it becomes even easier thanks to AI improving, and takes few hours instead of few days?
You could certainly do that in private but that doesn't mean it's not 'without legal concerns'. But, not shouting about it and not creating a repo called 'openviktor' would probably be a safer bet.
I certainly think the whole idea of IP ownership as related to software will become very interesting from a legal standpoint in the coming years. Personally I think that, over time, the legal challenges will become pretty overwhelming and a sort of legal bankruptcy will be declared at some point in one direction or another (as in, allowing this to happen or making it extremely easy to bring judgement and punishment, similar to spam laws). However, I would not want to be the first to find out, especially in Europe.
Nice. Probably worth making a local copy before it gets taken down.
(Re: legal - why even bother with a court decision when it’s on GitHub? A takedown is much simpler. We've seen this before, like when Meta went after people reverse-engineering their API)
That said there may not be much here thats actually protectable. It's mostly a CLI orchestrating other tools, and the same functionality could likely be reproduced fairly easily, especially with AI.
Still, props to him for writing a proper blog post and explaining the process
(I don't know anything about OpenClaw and on a deeper level, I don't wish to learn about it either considering all the security implications that it generally has)
---
The rest of this comment is irrelevant, but leaving for posterity, I had the wrong Viktor - it's getviktor.com not viktor.ai:
Edit: this one particularly interesting to me as both parties are in the EU. VIKTOR.ai is a Dutch company and the author of this post is Polish.
The ToS for Viktor.ai include the following fun passages:
> 18.1. The Agreement and these Terms & Conditions are governed by Dutch law and the Agreement and these Terms & Conditions will be interpreted in accordance with Dutch law.
18.2. All disputes arising from or arising in connection with the Agreement and/or the Terms & Conditions will be submitted exclusively to the competent court in Rotterdam, The Netherlands.
7.3. The Customer is not permitted to change, remove or make unrecognizable any mark showing VIKTOR's Intellectual Property Rights to the Software. The Customer is not permitted to use or register any trademark or design or any domain name of VIKTOR or a similar name or sign in any country.
8.5. The Customer may not cause or allow any reproduction, imitation, duplication, copying, sale, resale, leasing or trading of the Services and/or the Software, or any part thereof.
But, yeah. More than likely this case is a simple account termination and some kind of "you can't call your clone 'openviktor'" letter.
Anyways, however you put this, I see this as a property theft and taking pride at open sourcing does not justify it.
Let's call it what it is - stolen IP and released without permission of the author. Sure, it's good that it opens the debate as to whether that's ethical given that's essentially what the model itself is doing, but it's very clear in this instance that he's just asked for and been given a copy of source that has a clear ownership. That's about as clear cut as obtaining e.g. commercial server-side code and distributing it in contravention of the licence.
I certainly think the whole idea of IP ownership as related to software will become very interesting from a legal standpoint in the coming years. Personally I think that, over time, the legal challenges will become pretty overwhelming and a sort of legal bankruptcy will be declared at some point in one direction or another (as in, allowing this to happen or making it extremely easy to bring judgement and punishment, similar to spam laws). However, I would not want to be the first to find out, especially in Europe.
(Re: legal - why even bother with a court decision when it’s on GitHub? A takedown is much simpler. We've seen this before, like when Meta went after people reverse-engineering their API)
That said there may not be much here thats actually protectable. It's mostly a CLI orchestrating other tools, and the same functionality could likely be reproduced fairly easily, especially with AI.
Still, props to him for writing a proper blog post and explaining the process