Maybe an ignorant question but at the dictionary level, how would one indicate that multiple providers/models went into the resulting work (based on the example given)? Is there a standard for nested lists?
Proposal: AI Content Disclosure Header
11–20 of 50 posts
Re: Proposal: AI Content Disclosure Header
#12This feels like the Security Flag proposal (https://www.ietf.org/rfc/rfc3514.txt)
Re: Proposal: AI Content Disclosure Header
#13This feels like the Security Flag proposal ( https://www.ietf.org/rfc/rfc3514.txt )
or end up like california prop 65 warnings: https://en.wikipedia.org/wiki/1986_California_Proposition_65
Re: Proposal: AI Content Disclosure Header
#14Why only for HTTP? This would be appropriate for MIME multipart/mixed part headers as well. ;)
Maybe better define an RDF vocabulary for that instead, so that individual DIVs and IMGs can be correctly annotated in HTML. ;)
Re: Proposal: AI Content Disclosure Header
#15Hoping I don't need to click on something, or have something obstructing my view.
The cookie banner just got 200px taller.
Re: Proposal: AI Content Disclosure Header
#16This is like asking the fox to announce itself before entering the henhouse
Re: Proposal: AI Content Disclosure Header
#17The bigger challenge here is that we already struggle with basic metadata integrity. Sites routinely manipulate creation dates for SEO - I regularly see 5-year-old content timestamped as "published yesterday" to game Google's freshness signals.
While this doesn't invalidate the proposal, it does suggest we'd see similar abuse patterns emerge, once this header becomes a ranking factor.
Re: Proposal: AI Content Disclosure Header
#18Maybe 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 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.
That's a Pandora box I wouldn't even talk about, much less open...
Re: Proposal: AI Content Disclosure Header
#19Seems like someone just trying to get their name on a published IETF standard for the bragging/resume rights
Re: Proposal: AI Content Disclosure Header
#20Maybe 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…
[deleted]