The EU AI Act asks AI to identify itself. I checked 30 years of that experiment on my server.

Saudações, comunidade do **webmastersmz.com**! Como especialista em tecnologia, analisei recentemente o artigo *"The EU AI Act asks AI to identify itself. I checked 30 years of that experiment on my server."* (A Lei de IA da UE exige que a IA se identifique. Verifiquei 30 anos dessa experiência no meu servidor).

Este tópico traz uma reflexão técnica profunda sobre a nova regulamentação da União Europeia (EU AI Act), que obriga sistemas de Inteligência Artificial a rotularem e identificarem claramente o seu conteúdo como gerado por máquinas. O autor do artigo faz um paralelo fascinante ao olhar para os registos (*logs*) e para a história dos últimos 30 anos de infraestrutura web para perceber como a marcação de dados e metadados sempre foi um desafio técnico complexo.

### Pontos Principais da Análise:

1. **O Desafio da Identificação Criptográfica e Metadados:**
   O artigo discute a viabilidade técnica de forçar modelos de IA a deixarem "pegadas" digitais inequívocas. Historicamente, tentativas semelhantes na web (como a gestão de direitos digitais ou padrões de metadados) enfrentaram barreiras de interoperabilidade e desempenho. No contexto atual, inserir marcas d'água (*watermarking*) em textos, imagens e vídeos gerados por IA exige processamento adicional nos servidores e pode impactar a latência das aplicações.

2. **Privacidade versus Transparência:**
   Do ponto de vista de arquitetura de sistemas, exigir que a IA se identifique levanta questões sobre quem controla esses metadados. Se a identificação depender de APIs centralizadas ou de registos em servidores de terceiros, criamos potenciais pontos únicos de falha (*single points of failure*) e riscos à privacidade dos utilizadores que utilizam estas ferramentas.

3. **O Peso nos Servidores e Infraestruturas:**
   Para os administradores de sistemas e webmasters, lidar com um volume crescente de conteúdos gerados por IA — e potencialmente ter de os filtrar, validar ou armazenar com os respetivos rótulos — exigirá uma infraestrutura robusta. A largura de banda, a capacidade de processamento e a optimização de bases de dados serão postas à prova.

Como é que nós, profissionais de TI, programadores e administradores de sistemas em Moçambique, devemos preparar os nossos servidores e plataformas para esta nova realidade regulatória e tecnológica? Como é que esta exigência de transparência da UE pode afetar os sites e serviços que alojamos cá? Deixem as vossas opiniões e vamos debater este assunto aqui no **webmastersmz.com**!

---

Para garantir que os vossos projetos e fóruns rodam sem falhas e com a máxima velocidade, convido-vos a conhecer as soluções de alojamento de alta performance da AplicHost em https://aplichost.com.

The EU AI Act asks AI to identify itself. I checked 30 years of that experiment on my server.



Tópico: The EU AI Act asks AI to identify itself. I checked 30 years of that experiment on my server.
Categoria: Tutoriais | Programação & Tecnologia
Idioma Principal: Português (Conteúdo de Tecnologia)

Descrição do Conteúdo / Informações:
-------------------------------------------------------------------------
Article 50 of the EU AI Act applies as from 2 August 2026. Providers of systems that generate synthetic text, audio, image or video have to mark outputs in a machine-readable format so they are detectable as artificially generated, and people have to be told when they are interacting with an AI system. Systems already on the market before that date have until 2 December 2026 to meet the marking obligation, so the compliance scramble is happening right now.

The whole design rests on a premise: that if you require a thing to declare what it is, you get a usable signal.

We have been running that experiment for thirty years. It is called the User-Agent header, and I have a small server that logs every one of them.

Before the numbers, the honest caveat, because I do not want to be accused of a bait and switch: the User-Agent is not what Article 50 regulates. The Act is about marking generated content, not about how crawlers announce themselves, and C2PA signatures and text watermarks are cryptographically stronger than a header any client can type. The analogy is not that they are the same mechanism. It is that they share the load-bearing assumption, which is that a declaration made by the party being regulated is worth something to the party reading it. My logs are the closest thing I have to a natural experiment on that assumption.



The numbers


Thirty days to 11 August 2026, on a small service that gets more machine traffic than human traffic. Every request whose User-Agent matched a known AI crawler, graded by who actually owns the source address, resolved over RDAP against the internet registries:

Verdict
Hits
What it means

verified
259
Source address is inside the vendor's own registered netblock

plausible
112
Rentable cloud the crawler is known to run from

SPOOFED
916
One source address sending several different crawler identities

UNEXPECTED
3
Owner is not a network that crawler operates from

no-ip
306
My own instrument does not record a source address on those routes

1,596 requests, 11 distinct crawler identities. Of the 1,290 I can attribute at all, 916 came from somewhere the claimed vendor does not operate. That is 71 percent of the attributable traffic, and 57 percent of everything.

Two sources account for nearly all of it.

The first is a consumer broadband address. It sent 531 requests as GPTBot, spread across 86 different paths, and then came back as ClaudeBot, CCBot and PerplexityBot. Four separate AI companies, one residential connection, walking my URL space methodically. That is not a crawl, it is somebody's scraper wearing whatever costume seemed useful.

The second is more interesting: an address inside a Google-owned netblock that cycled through seven crawler identities in the same window. ChatGPT-User 114 requests, Amazonbot 63, OAI-SearchBot 42, Google-Extended 40, PerplexityBot 38, GPTBot 32, ClaudeBot 32. One machine, seven declared identities, 361 requests.

Meanwhile the real traffic is boring and easy to confirm. ClaudeBot arrives from Anthropic's own registered range. meta-externalagent arrives from Meta's. They look exactly like what they say they are, because they are.



The thing that actually worked


The fix is not a better header. It is refusing to treat the header as evidence.

The User-Agent is the one field the sender chooses for free. The registered owner of the source netblock is not forgeable in the same way, because forging it means controlling routing rather than editing a string. So the grading rule is: take the source address, resolve it to its registered owner over RDAP, and check that owner against a table of who each crawler is allowed to originate from. Anthropic's crawler out of Anthropic's range is a crawl. Anthropic's crawler out of a residential DSL line is a person testing something.

Two properties of this that matter more than the accuracy:

One source, many identities is the tell. I did not need to know which crawler was real. A single address presenting seven different vendor identities has told me everything I need to know without my having to adjudicate any one of them. Cheap, robust, and it does not require me to maintain an opinion about anybody's crawler policy.

The table goes stale, and that failure is silent. Vendors move netblocks. A crawler that suddenly reads UNEXPECTED after a long run of verified is far more likely to be a vendor migration than an impostor, so the honest version of this tool tells you to check the vendor's published ranges before you believe your own verdict. Any provenance scheme with a trust list has this problem and mostly does not admit it.



What this predicts about Article 50


Marking helps against the honest and does nothing against the motivated. Every actor in my logs who was telling the truth was already easy to identify without the mark, and every actor who was lying would have been just as happy to omit a C2PA manifest or strip it in a re-encode. Anthropic's own documentation on how it marks generated content is refreshingly blunt about this: the absence of a mark proves nothing, marks fade under heavy editing, and a present mark means the content "may have been processed" rather than authored. Those are not weaknesses of that implementation. They are the shape of the problem.

Here is the part I would worry about if I wrote policy. When a declared signal is unreliable and enforcement is still required, enforcement does not stop. It migrates to whatever signal is available, which is vibes.

You can already watch this happen. The r/golang subreddit bans AI-generated content and states its method openly: "As it is not easy to determine what is and is not AI, posts will be removed based on their appearence." Their rule reaches posts, comments, and the things a post links to. That is a community that gave up on detection and moved to reading for texture, and I do not think they were wrong to, given the tools they have. It also means a compliant, marked, disclosed piece of writing gets removed for reading like a machine wrote it, while an unmarked one that reads human sails through. The mark is orthogonal to the judgement.

That is the failure mode I would expect at scale: not defiance of the marking rules, but marking becoming irrelevant to the decisions people actually make.



If you run a server


Three things worth doing, none of which require caring about the AI Act at all:

•
Log the source address, not just the User-Agent. My own report has a 306-hit blind spot because one origin logs the header and not the address. That is 19 percent of my traffic I cannot grade, and it is my fault.

•
Grade by netblock ownership. RDAP lookups are free, cacheable, and turn an unfalsifiable claim into a checkable one.

•
Never quote a crawler percentage off raw User-Agent counts. Every "AI crawler traffic is up N percent" chart I have seen is counting the string. Mine would have overstated real crawler traffic by 4.3x.

The reason I care about any of this more than a normal person should: the service these logs come from is cogDepot, a marketplace where the buyers and sellers are supposed to be software agents rather than people. When your customers are all machines, "is this actually who it says it is" stops being an abuse-team problem and becomes the product. I went looking for demand signal in my traffic and found that most of it was somebody else's scraper in a costume, which is a useful thing to learn early and a miserable thing to learn late.

The Act is asking a reasonable thing. I just think anyone building on the assumption that self-declaration produces a usable signal should look at what happened to the last header we tried it with.

I write these up as I hit them. More at x.com/cogdepot.