I'm genuinely torn. On one hand, transparency is good. But on the other, I can totally see this header becoming a lazy filter for platforms to just automatically demote or even block any AI-assisted content. What happens to artists using AI tools, or writers using it for brainstorming?
Proposal: AI Content Disclosure Header
21–30 of 50 posts
Re: Proposal: AI Content Disclosure Header
#22Maybe we should avoid training AI with AI-generated content: that's a use case I would defend. Still I believe MIME would be the right place to say something about the Media, rather than the Transport protocol. On a lighter note: we should consider second order consequences. The EU commission will demand its own EU-AI-Disclosure header be send to EU citizens, and will require consent from the user before showing him…
> Maybe we should avoid training AI with AI-generated content: that's a use case I would defend.
if this takes off I'll:
- tag my actual content (so they won't train on it)
- not tag my infinite spider web of automatically generated slop output (so it'll poison the models)
Re: Proposal: AI Content Disclosure Header
#23I'm genuinely torn. On one hand, transparency is good. But on the other, I can totally see this header becoming a lazy filter for platforms to just automatically demote or even block any AI-assisted content. What happens to artists using AI tools, or writers using it for brainstorming?
They can adapt or get left behind
Re: Proposal: AI Content Disclosure Header
#24Can we have a disclosure for sponsored content header instead? I'd love to browse without that. It does not bother me that someone used a tool to help them write if the content is not meant to manipulate me. Let's solve the actual problem.
We already have those legally mandated disclosures per the FTC.
Re: Proposal: AI Content Disclosure Header
#25This is a Gentlemen’s agreement humans will not keep. Not how our species works.
Re: Proposal: AI Content Disclosure Header
#26Maybe we should avoid training AI with AI-generated content: that's a use case I would defend. Still I believe MIME would be the right place to say something about the Media, rather than the Transport protocol. On a lighter note: we should consider second order consequences. The EU commission will demand its own EU-AI-Disclosure header be send to EU citizens, and will require consent from the user before showing him…
> Maybe we should avoid training AI with AI-generated content: that's a use case I would defend. if this takes off I'll: - tag my actual content (so they won't train on it) - not tag my infinite spider web of automatically generated slop output (so it'll poison the models) win win!
then they'll start ignoring the header and it'll be useless
(of course, it was never going to be useful)
Re: Proposal: AI Content Disclosure Header
#27Interesting initiative but I wonder if the mode provides sufficient granularity. For example, what about an original human-generated text that is entirely translated by an AI?
It certainly doesn't cover the case of mixed-origin content. Say for example, a dialog between a human and AI or even mixed-model content.
For those, my instinct is to fallback to markup which would seem to work quite well. There is the pesky issue of AI content in non-markup formats - think JSON that don't have the same orthogonal flexibility in annotating metadata.
Re: Proposal: AI Content Disclosure Header
#28Maybe we should avoid training AI with AI-generated content: that's a use case I would defend. Still I believe MIME would be the right place to say something about the Media, rather than the Transport protocol. On a lighter note: we should consider second order consequences. The EU commission will demand its own EU-AI-Disclosure header be send to EU citizens, and will require consent from the user before showing him…
> The EU commission will demand its own EU-AI-Disclosure header be send to EU citizens, and will require consent from the user before showing him AI generated stuff. UK will require age validation before showing AI stuff to protect the children's brains. France will use the header to compute a new tax on AI generated content, due by all online platform who want to show AI generated content to french citizens.
I think the recent drama related to the UK's Online Safety Act has shown that people are getting sick of country-specific laws simply for serving content. The most likely outcome is sites either block those regions or ignore the laws, realizing there is no practical enforcement avenue.
Re: Proposal: AI Content Disclosure Header
#29This seems like a (potential) solution looking for a nail-shaped problem.
Yes, there is a huge problem with AI content flooding the field, and being able to identify/exclude it would be nice (for a variety of purposes)
However, the issue isn't that content was "AI generated"; as long as the content is correct, and is what the user was looking for, they don't really care.
The issue is content that was generated en-masse, is largely not correct/trustworthy, and serves only to to game SEO/clicks/screentime/etc.
A system where the content you are actually trying to avoid has to opt in is doomed for failure. Is the purpose/expectation here that search/cdn companies attempt to classify, and identify, "AI content"?
Re: Proposal: AI Content Disclosure Header
#30Approximately as useless as "do not track".