News for hackers. Stuff that matters.
Re:Reverse-engineering Viktor and making it Open Source by cycomanic on Tuesday March 17, 2026 @10:28AM (#47413201)
Well first they need to proof that Viktor was actually copyrightable. If it was largely written by an llm, that might not be the case? AFAIK several rulings have stated that AI generated code can not be copyrighted.
Re:Reverse-engineering Viktor and making it Open Source by metalcrow on Tuesday March 17, 2026 @11:17AM (#47413903)
This is a common misreading of the law. AI cannot hold authorship of code, but no ruling has claimed so far that ai output itself can't be copyrighted (that I know of)
Re:Reverse-engineering Viktor and making it Open Source by ralferoo on Tuesday March 17, 2026 @12:02PM (#47414540)
This would suggest that there has been and that there seem little will to revisit it: https://www.theverge.com/policy/887678/supreme-court-ai-art-...

That said, the article says "Okay, prompts, great. Are they any interesting? Surprisingly... yes. As an example workflow_discovery contains a full 6-phase recipe for mining business processes out of Slack conversations, something that definitely required time and experiments to tune. It's hardcoded business logic, but in prompt instead of code."

So the article author clearly knows this prompt would be copyrighted as it wasn't output from an AI, and recognises that there would have been substantial work involved in creating it.

Re:Reverse-engineering Viktor and making it Open Source by metalcrow on Tuesday March 17, 2026 @09:14PM (#47420528)
That Reuters article is misleadingly worded. The Stephen Thaler case in question is because Thaler tried to register the AI itself as the author of the copyright, not that he tried to register the output for copyright under his own name. https://www.hklaw.com/en/insights/publications/2026/03/the-f...
Re:Reverse-engineering Viktor and making it Open Source by fc417fc802 on Wednesday March 18, 2026 @07:05AM (#47424100)
Suppose I illicitly get my hands on the source code for a proprietary product. I read through this code I'm not supposed to have. I write up a detailed set of specifications based on it. I hand those specifications off to someone else to do a clean room implementation.

Sure, I didn't have a license for the code that I read. But I'm pretty sure that doesn't taint my coworker's clean room implementation.

Re:Reverse-engineering Viktor and making it Open Source by jacquesm on Wednesday March 18, 2026 @08:43AM (#47425059)
A reminder to never take legal advice from HN.
Re:Reverse-engineering Viktor and making it Open Source by fc417fc802 on Wednesday March 18, 2026 @11:27AM (#47426979)
I don't think anyone was offering any? Merely discussing a confusing new situation that has arisen.