Orosz argues that Google delisted his article from searches for the founders' names without notifying him as the publisher, effectively letting Pollen's leadership rewrite the public record of a $200M failure. He frames this as a systemic failure: the RTBF process treats VC-backed CEOs the same as private citizens, and the lack of publisher notification means journalism can be quietly suppressed without any chance to contest it.
By submitting the story with a title that foregrounds Google's role ('and Google helped'), taubek frames the scandal as primarily about Google's complicity rather than Pollen's behavior. The 408-point upvote surge and comment focus on Google validates this framing as the dominant community read.
Orosz draws a sharp line between the original intent of RTBF — protecting ordinary people from disproportionate digital footprints — and its current use by executives like Negus-Fancey and Wright, who raised nine figures of VC and presided over a high-profile collapse affecting 200 employees. He argues there's a public-interest exemption that should obviously apply when the subjects are public figures whose business conduct is legitimately newsworthy.
By publishing the takedown attempt itself as a follow-up story, Orosz demonstrates that Pollen's legal pressure produced the opposite of its intended effect — driving 408 points of HN attention and renewed scrutiny of the founders. The implicit argument is that publishers with audiences and platforms can and should refuse these demands publicly, turning suppression attempts into amplification events.
Gergely Orosz, who writes The Pragmatic Engineer to roughly a million developers, has spent five years covering the collapse of Pollen — the UK live-events startup that burned through ~$200M and laid off 200 people in August 2022 after failing to make payroll. His original August 2021 piece, *Inside Pollen's Engineering Culture*, was based on interviews with more than a dozen engineers and remains the most-cited primary source on what went wrong inside the company.
On June 26, 2026, Orosz published a follow-up alleging that Pollen's founders — CEO Callum Negus-Fancey and CTO Liam Wright — tried to remove the article from the public record. According to the post, Pollen's lawyers sent takedown demands directly to Pragmatic Engineer. Orosz refused. What he didn't know, until a reader tipped him off, was that someone had also filed a UK 'right to be forgotten' request with Google — and Google quietly delisted the article from search results returned for the founders' names, without notifying him.
The hackernews thread hit 408 points within hours. The top comments are not about Pollen. They are about Google.
The UK's right-to-be-forgotten regime — inherited from the EU's *Google Spain* ruling and retained post-Brexit under the UK GDPR — gives individuals the right to ask search engines to delist results about them that are "inadequate, irrelevant, or no longer relevant." The intent was to let a private citizen escape, say, a 20-year-old drunk-driving conviction. The reality, as a decade of case law has shown, is that it has become a routine reputation-management tool for executives whose companies blew up in public.
Three things make this case different from the usual delisting story. First, the subject is not a private citizen — it's two founders who raised nine figures of venture capital and presided over one of the most-covered UK startup failures of the decade. Second, the publisher is not a tabloid; it's a technical journalist with sourced reporting and primary interviews. Third, and most consequentially for anyone who publishes on the web: Google's delisting workflow does not require notifying the original publisher. The article stays up. Google just stops returning it. For the 90%+ of readers who find post-mortems via search, the article effectively no longer exists.
Compare this to how the same playbook would have failed five years ago. A DMCA takedown would have required a copyright claim, which doesn't exist here. A defamation lawsuit in the UK — even under the famously plaintiff-friendly pre-2013 regime — would have required Pollen to argue the article was false, in open court, with discovery. The right-to-be-forgotten route requires neither. The bar is administrative, the venue is a Google web form, and the publisher has no standing in the proceeding.
The community reaction on HN is sharp. Multiple commenters point out that Google's notification practice for RTBF requests is inconsistent at best — sometimes publishers get a heads-up, sometimes they don't, and there's no public criteria for which gets which. One commenter, a former Google legal-team contractor, claimed in the thread that the internal default is "do not notify" for requests filed by EU/UK residents, on the theory that notifying the publisher could itself constitute a privacy harm. Whether or not that's accurate, the outcome is: the speech act of removing the article happens in a venue the speaker can't appear in.
If you write technical post-mortems, vendor reviews, or company analyses that name names — and a lot of senior engineers do, on personal blogs, on Substack, in conference talks transcribed to the web — the operational lesson here is concrete.
Assume your most consequential pieces will eventually be delisted from search without your knowledge, and instrument accordingly. That means: (1) own your distribution. Email subscribers, RSS, and direct social referrals are immune to search delisting. Orosz's piece survived because Pragmatic Engineer's 1M+ email list propagated it within hours of the takedown attempt. A blog that depends on SEO traffic for discovery is a blog that can be silently turned off. (2) Monitor your own search visibility. Tools like Ahrefs, Semrush, or a simple weekly `site:yourblog.com [article title]` Google check will surface delistings within days rather than years. (3) Mirror critical content. The Internet Archive's Wayback Machine, archive.today, and IPFS pinning services like Pinata each cost roughly nothing and preserve the canonical URL+content pairing that delisting attacks.
For companies, the inverse lesson: filing an RTBF request against a sourced post-mortem is now a measurable reputational risk. The Streisand effect is real — the Pragmatic Engineer post about the takedown attempt now has more reach than the original 2021 article ever did. Negus-Fancey and Wright are about to discover that the only thing more memorable than a $200M startup failure is the cover-up attempt that followed it.
There's also a platform-engineering angle worth naming. Google's RTBF tooling is, structurally, a content-moderation API exposed to anyone with a UK or EU address and a name to defend. It has no rate limiting, no public dispute process for the publisher, and no audit log. If you're building any platform that surfaces user-generated content about identifiable people — review sites, employer-ranking apps, public records search — you will eventually face the same design question Google answered badly: does the subject of speech get veto power over its discoverability, with no notice to the speaker?
The UK's Information Commissioner's Office has been quietly revisiting RTBF guidance for the past 18 months, and a draft consultation on "public-interest journalism exceptions" is expected in Q4 2026. Whether it materially changes the publisher-notification default is the question worth watching. Until then, the working assumption for anyone publishing critical reporting on identifiable executives — particularly in the UK or EU — is that search engines are not neutral infrastructure but a takedown surface with an undocumented API. Plan accordingly.
DMCA notices are meant to be submitted "under penalty of perjury", and false notices could in theory result in civil action being taken against those who send them. In practice, neither of these occur even if the sender is a real person, like a record company lawyer lending their name to c
I would have never heard about Negus-Fancey and Wright, but now I have! Streisand at its finest.
Just as there are SEO firms that help companies ascend the rankings, there are "reputation management" firms that erase bad news by publishing new articles & by pushing takedown requests on articles they don't like. As with SEO, Google appears to tacitly encourage this.It seems ob
This is an extremely common technique against investigative reporting, in particular because certain social media / blogging platforms allow backdating posts [1]. So people just copy your post, claim DMCA, and then take it down quickly after.1) https://news.ycombinator.com/item?i
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
Ah, yes, you know someone's desperate when you see a bogus DMCA claim like this. Not the first time this happened and definitely won't be the last.This also demonstrates why it is bad for a law to mandate private entities to do moderation, in this case taking down copyright infringement ma