I acknowledge that I temporarily violated the Huxe Terms of Service in a recent post. Yes, I failed to read the TOS when I set up my account, but this is hardly uncommon. My violation was posting a link to content I created, even though sharing is not allowed.
Huxe is a new tool that enables AI-generated podcasts. At least this would be one way to describe the product. You identify sources or offer a prompt that sets a goal and you then have access to podcasts based on these designations. In addition, Huxe allows a user to interrupt a podcast and ask a question about the content – a very cool feature.
My attempt to include a link to my creation, and my intent to record the audio as an example for those who had not created an account, was quite innocent. I made assumptions based on what I saw on my screen. There was a way to change my creation from private to public and the button to share the link to the creation. How would you interpret these signals?
I discovered my transgression when I could not remember the process I had used to share my example and asked some AI sources to describe the sharing process. The second effort brought a response that sharing of this material was not allowed.
The first effort, which was a Google search that returned its AI summary before the links, not only indicated that sharing was legal but also provided a source for this claim. I checked the link, and ironically, the source was my original post, which included the offending link.
A couple of thoughts, I had always assumed that AI-generated content, being a summarization, was not protected by copyright. Perhaps the Huxe expectation is based on the “use of” rather than on the content itself. You cannot access the content without using the service, which seems to be the justification. I do think it somewhat ironic that, in comparison, the use of my content in a response created by AI without my consent would be acceptable. Something seems off in this combination.
I removed the shared example to resolve the issue, but the claim in Google’s response to my query did not change. This adjustment may take some time.