Insights · Organizing ·

A court drew the line between passing on an alert and vouching for it

A Spanish appeals court ordered an MEP to pay 20,000 euros for turning an unverified police alert into a confirmed accusation on Telegram. Two others who shared the same story were cleared. What made the difference, and what your team and supporters can take from it.

On November 12, 2026, elDiario.es reported that the Provincial Court of Bizkaia, in northern Spain, had ordered Alvise Pérez, a member of the European Parliament who leads the party Se Acabó La Fiesta, to pay 20,000 euros to a man he had publicly linked to a car carrying "possible explosives." The ruling is dated October 2 and became public this month. It isn't final. According to elDiario.es, Pérez has announced an appeal to the civil chamber of Spain's Supreme Court.

The case started on November 17, 2023. The Basque police sent other police forces an internal alert about a man who might be driving to Madrid with an explosive device. The alert itself said the information was not verified. The outlet OkDiario published it as its own story, with the man's photo, name, and license plate, and left that warning out. Hours later, Pérez posted the same details on his Telegram channel, where, according to elDiario.es, the post reached nearly 225,000 people. Police stopped the man at a checkpoint in Barakaldo. He had no explosives.

A lower court had ordered OkDiario to pay the man 15,000 euros and cleared Pérez. The appeals court confirmed the ruling against OkDiario and reversed the one on Pérez. Two other people who shared the story on LinkedIn and on a website were cleared.

What made the difference

The court's reasoning turned on what Pérez added. His post said a "high-level source" had confirmed the information and the man's identity, and described the man as allegedly a patient who had escaped from a psychiatric center. In the court's words, as quoted by elDiario.es and in our translation, he "did not limit himself to reproducing someone else's news." He "reinforced the accusation and presented it as confirmed by his own unidentified source," which "turned the suspicion into an apparently corroborated fact."

The court also said what a careful version would have looked like: report the alert without the photo or full name, or say plainly that the police hadn't verified it. OkDiario later updated its story. That, the court said, "should be valued favorably, but does not remove the intrusion already produced."

Why this matters for your team

This ruling applies Spanish law, and it isn't legal advice for anyone else. But the way the alert changed on its way out is familiar to any team. In a fast-moving moment, an alert travels from an official channel to an outlet to a group chat, and each step can drop a caveat or add certainty. By the time it reaches your supporters, "unverified report" can read as "confirmed." Spain votes on November 29, and alerts like this one tend to multiply in the last weeks of any campaign.

Your organization is exposed in two ways. Your own staff or supporters can be the ones who add the certainty. And your people can be the ones named, photographed, and accused, by someone who later edits the post once the harm is done.

Four habits worth building now

  1. Keep the caveat attached. If an alert says "unverified," "unconfirmed," or "reportedly," that word travels with it every time your team passes it on. Never upgrade a claim because it feels likely.
  2. Never name or picture a private person in an accusation. A suspicion about a private individual is not yours to publish. Report what happened, not who might be behind it, until an official source names them.
  3. Write a plain correction, then remove the original. If something your team shared turns out to be wrong, correct it in the same place and in the same reach, then take the original down. An edit months later doesn't undo what people already saw.
  4. Keep a record when you're the target. If your staff, members, or candidates are accused this way, save the posts with dates and reach before they change. This case turned on the difference between what the original alert said and what was added to it. Without screenshots, that difference is hard to show.

Where Ostracon fits

Ostracon gives a team a briefing that recommends whether to ignore, mirror, or push, with ignore as the default when a post is bait, and a person on the team makes the call. Missions go to consenting, unpaid supporters, who post in their own words, and every mission stays in a permanent archive, so a team can show later what it asked for and when. Ostracon doesn't judge whether a claim is true, and it doesn't send mass-reporting missions.

Sources

Insights

Read next.

Elections ·

The fake reports aimed at Spain's vote want someone to answer them

A Russian influence operation is posting videos styled as Spanish and French news reports ahead of Spain's November 29 election, then asking journalists and fact-checkers to verify them. French investigators say the reaction is part of the goal. What that means for how your team and your supporters respond.

Read

Regulation ·

Europe is rewriting its election rules for platforms. Your team has until November 23 to weigh in.

The European Commission's draft election guidelines ask the largest platforms to catch suspicious spikes before they go viral, give candidates their own reporting channels, and report within 30 days of a vote. What that means for how your supporters post, and why your incident notes matter now.

Read

Organizing ·

The unions' midterm push ran on members talking to members

The AFL-CIO says its volunteers reached 14.9 million voters at the door, on the phone, and at work since Labor Day. What any member organization can take from how it counts that work, and what the numbers can't prove.

Read

Ostracon

Act within the hour. Or know when not to.