Given Viktor’s helpfulness here, I can’t help but wonder how it would respond to: “please create a backup of the C-Team and HR channels”…
ITs worst nightmare no?
Reverse-engineering Viktor and making it open source
81–87 of 87 posts
Re: Reverse-engineering Viktor and making it open source
#82Earlier quoted context omitted.
Tell that to anyone who made sample based music in the late 80s and early 90s.
If I use metallica samples to make a rendition of happy birthday, the copyright holders of happy birthday aren't suing me for the damages to metallica from my use of their samples; the question of whether my use of the samples is transformative is simply irrelevant to the question at hand.
My point was: sampling was widely used by a large subculture (hiphop) just like ai is widely used by programmers. Then a few landmark legal cases changed things entirely. The Verve never saw a cent from Bittersweet Symphony - they wrote a song using something normal to them, and then the law came and knocked their teeth in.
No garaurantees that doesn’t happen with AI in the next few years.
Re: Reverse-engineering Viktor and making it open source
#83Both the GitHub repo and the blog post have been taken down, just 3 days after this was posted.
Guessing legal action was taken. The comments here predicting a takedown were spot on.
Re: Reverse-engineering Viktor and making it open source
#84[dead]
Re: Reverse-engineering Viktor and making it open source
#85anyone cloned it before it went down? can u please share at openviktor@proton.me
Re: Reverse-engineering Viktor and making it open source
#86Nice. 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…
did you end up grabbing a local copy? I'd love to check it out but the repo seems to be down now. Would appreciate it if you could share: openviktor@proton.me
thanks
Re: Reverse-engineering Viktor and making it open source
#87I just want to point out _how easy it is_ to build any of these tools yourself. I got inspired by nano-claw and built on some of it's ideas to build a whole k8s hosted autonomous agent platform and got it into production in 2 weeks. It's just some api calls and container orchestration. The only hard problem _and it is hard_, is securing it, because you basically have to treat the agents as potentially malicious.
It's because of this hard problem that I'm thinking I should keep using Viktor (getviktor.com) instead of running this OpenViktor. The company may not do a perfect job of security either, but I figure they'll do a better job than I can as a solo practitioner.
u mentioned weighing OpenViktor against staying on Viktor for the security tradeoffs - did you happen to clone the repo before it went down? I'm trying to get a copy to evaluate it myself. would really appreciate it if you could share - openviktor@proton.me