WOIB autorship article
All Media Reports > Brighton
Forensic Style Report – What’s On In Brighton (WOIB) Derivative Article Analysis
By Riccardo Gresta – The Record Speaks
Updated: June 2026
Updated: June 2026
This report documents my forensic analysis of the article “Eastbourne man sentenced in Hove after council blue badge fraud”, published on 27 December 2022 on the website What’s On In Brighton (WOIB). The article was removed from the site in May 2026 following my GDPR requests and the broader delisting actions already applied to the related publications from ITV, SussexWorld, and The Argus.
The purpose of this report is to establish the origin, authorship pattern, and editorial reliability of the WOIB article, and to situate it within the wider chain of derivative and unverified reporting that amplified inaccurate and harmful information about me.
1. Context and Nature of the Publication
What’s On In Brighton is part of the WhatsOnIn network, a commercial content platform that aggregates local news, events, and directory listings across multiple UK cities. It is not a journalistic organisation in the traditional sense: it does not employ named reporters, does not provide bylines, and does not disclose editorial staff.
The article concerning me appears under the “Brighton News & Events” section, but:
- contains no author name,
- contains no editorial signature,
- contains no source attribution,
- and is structured in a way that strongly suggests automated or semi‑automated ingestion of external content.
This already distinguishes it from legitimate news outlets such as ITV or The Argus, which at least maintain identifiable editorial structures.
2. Forensic Comparison With Known Source Articles
The wording of the WOIB article is not original. It reproduces, almost verbatim, the same narrative structure found in the SussexWorld / The Argus ecosystem.
For example, the article states:
“Riccardo Gresta, of Elms Avenue in Eastbourne, submitted a letter from a neurologist claiming that he was unable to walk further than 20 metres.”
This sentence is identical in structure and sequencing to the SussexWorld version published on the same date.
Similarly, the passage:
“On closer inspection, grammatical errors in the letter tipped off East Sussex County Council that the claim was false.”
is a direct derivative of the Argus/SussexWorld reporting.
This confirms that WOIB did not conduct independent reporting, did not verify facts, and did not contact any authority.
It simply republished an existing narrative.
It simply republished an existing narrative.
3. Derivative Publication Chain (ESCC → Regionals → WOIB)
My forensic reconstruction shows that the WOIB article is not merely derivative: it is a copy of a copy.
The chain of derivation is:
1. ESCC
Original press release (later withdrawn at all levels).
Contained inaccuracies, invented details, and sensitive personal data.
Contained inaccuracies, invented details, and sensitive personal data.
2. Regional media (The Argus, SussexWorld, ITV)
First‑generation reproductions.
Republished the ESCC narrative almost verbatim, maintaining the same errors.
Republished the ESCC narrative almost verbatim, maintaining the same errors.
3. What’s On In Brighton (WOIB)
Second‑generation derivative.
Copied the regional articles, not the ESCC source.
No verification, no editorial oversight, no attribution.
Copied the regional articles, not the ESCC source.
No verification, no editorial oversight, no attribution.
This means that WOIB did not merely republish inaccurate information: it republished inaccurate information that had already been republished inaccurately.
Each step in the chain amplified the original errors and further detached the narrative from any factual basis.
4. Probable Authorship (Forensic Attribution)
Because the article contains:
- no byline,
- no editorial metadata,
- no author profile,
- no publication signature,
- and no stylistic fingerprint,
the most probable “author” is not a human journalist, but rather:
→ an anonymous or automated content generator within the WhatsOnIn network.
This is consistent with:
- the network’s known use of syndicated content,
- the absence of any editorial identity,
- the mechanical structure of the article,
- and the fact that the article was removed silently, without correction or notice.
In forensic terms, the article is best classified as:
“Derivative, unsigned, non‑journalistic content produced through automated or semi‑automated aggregation.”
5. Editorial Reliability and Legal Implications
The WOIB article reproduced:
- judicial data,
- health data,
- allegations,
- and narrative framing
without any verification, context, or editorial oversight.
It also repeated factual inaccuracies and misleading statements already present in the SussexWorld/Argus chain, including:
- the claim that I “submitted” a forged letter,
- the claim that I “complained to the Ombudsman”,
- and the claim that I “initially denied the allegations”.
These statements were reproduced without any independent fact‑checking, and without any legal basis to process or republish sensitive data.
The removal of the article in 2026 confirms that the publisher was unable to defend the legality of the content under GDPR.
6. Forensic Conclusion
My analysis demonstrates that the What’s On In Brighton article was:
- not written by a journalist,
- not independently verified,
- not editorially supervised,
- not original,
- and not compliant with data‑protection law.
The most probable “author” is an anonymous internal system, not a human reporter.
The article functioned as a derivative amplification node, republishing inaccurate and harmful information originally circulated by SussexWorld and The Argus. Its removal in 2026 aligns with the broader pattern of unlawful data processing identified across the Sussex media ecosystem.
This report forms part of the digital evidence archive published on The Record Speaks, documenting the propagation and subsequent removal of inaccurate and harmful content relating to my case.
Additional Forensic Conclusion – Liability and Legal Continuity
Although the What’s On In Brighton article was removed and de‑indexed approximately one month prior to the date of this report, this late removal does not alter or diminish the underlying liabilities associated with the unlawful republication of inaccurate and sensitive information. Under data‑protection law and within the framework of the international proceedings currently underway, the timing of the removal is irrelevant to the assessment of responsibility.
The article remained publicly accessible for more than three years, during which it continued to process and disseminate:
- inaccurate judicial information,
- sensitive health data,
- and derivative allegations originating from an already flawed institutional source.
The fact that the content was eventually removed does not erase the period during which the data was unlawfully processed, nor does it mitigate the harm caused by its prolonged availability. In forensic terms, the removal constitutes a post‑hoc corrective action, not a defence.
Within the context of the ongoing international proceedings, the liability for republishing and amplifying inaccurate information persists regardless of the article’s current availability. The removal simply confirms that the publisher was unable to justify the legality of the content when challenged, reinforcing rather than weakening the evidentiary basis of my case.
Consolidation Paragraph (Forensic Style)
Across the different components of my archive — Brighton article analysis, Brighton source code analysis, Comparative Analysis: WOIB vs ESCC Newsroom, and WOIB authorship article — a consistent forensic pattern emerges. The What’s On In Brighton publication is demonstrably a second‑generation derivative: a copy of the copy, produced by ingesting and reproducing the already inaccurate and unverified regional reporting that itself originated from the flawed ESCC press release. My source‑code inspection confirms the absence of any journalistic structure, byline, or editorial identity, while the comparative analysis shows that WOIB replicated the same factual sequencing, the same invented elements, and the same distortions found in the SussexWorld/Argus chain. The authorship assessment further establishes that the article was not written by a journalist but generated through an anonymous or automated aggregation system within the WhatsOnIn network. Taken together, these findings demonstrate that WOIB acted as an amplification node within a multi‑layered propagation chain, republishing inaccurate judicial and health data without verification, oversight, or legal basis. The fact that the article was removed and de‑indexed approximately one month before this report does not alter the underlying liabilities for the unlawful republication of sensitive and inaccurate information, particularly within the context of the international proceedings currently underway.
Consolidation Paragraph (Forensic Style – Bourne Free Live Section)
Across the different components of my archive — Bourne article analysis, Bourne source code analysis, Comparative Analysis: BFL vs ESCC Newsroom, and BFL authorship article — a consistent forensic pattern emerges. The Bourne Free Live publication is demonstrably a first‑generation derivative of the Sussex regional reporting, itself based on the flawed and subsequently withdrawn ESCC press release. My source‑code inspection confirms that the article was formally attributed to Peter Lindsey, whose name appears in the WordPress author tag, establishing him as the author of record and therefore the individual assuming editorial and legal responsibility for the publication. The comparative analysis shows that the BFL article replicated the same narrative sequencing, the same invented elements, and the same factual inaccuracies found in the regional press, without verification or independent assessment. The authorship assessment further demonstrates that Lindsey’s byline constitutes a binding declaration of responsibility for the processing and dissemination of sensitive judicial and health data. Taken together, these findings show that Bourne Free Live acted as an amplification node within the wider propagation chain, and that the article’s removal and de‑indexing in January 2026 — confirmed to me via email — does not alter the underlying liabilities associated with its prolonged publication.
Systemic Failures Across Multiple Controllers – Misclassification and Non‑Response (Consolidated Master Paragraph with Integrated Page Titles)
A broader systemic issue emerges when examining the conduct of all controllers involved, as evidenced across the full set of analytical pages on this website — including ITV article analysis, ITV source code analysis, Comparative Analysis: ITV vs ESCC Newsroom, ITV – Digital Evidence Analysis, SussexWorld article analysis, SussexWorld source code analysis, Comparative Analysis: Sussex Express/SussexWorld vs ESCC Newsroom, Sussex Express – Digital Evidence Analysis, The Argus article analysis, The Argus source code analysis, Comparative Analysis: The Argus vs ESCC Newsroom, Request and Misinterpretation by Newsquest – The (WOIB) Brighton source code analysis, Comparative Analysis: WOIB vs ESCC Newsroom, WOIB authorship article, Bourne article analysis, Bourne source code analysis, Comparative Analysis: BFL vs ESCC Newsroom, and BFL authorship article.
Across all these pages, a consistent pattern emerges. Both ITV and Newsquest/The Argus misclassified my communication of 30 March 2026. I, Riccardo Gresta, did not submit a Subject Access Request and did not request erasure. My communication was a collaborative proposal, intended solely to offer a pragmatic resolution following the withdrawal of the original East Sussex County Council press release. Despite this, both ITV and Newsquest independently treated my proposal as a request for deletion, issuing formal refusals under Article 17 UK GDPR to a request that I never made. This demonstrates a shared failure to correctly identify and route non‑GDPR correspondence.
This pattern is further confirmed by Newsquest’s handling of the SAR submitted by (Former Carer), which was a standard access request under Article 15, yet Newsquest again treated it as a request for erasure, applying journalistic exemptions and refusing deletion — even though no deletion had been requested. The fact that Newsquest misclassified both a collaborative proposal (mine) and a formal SAR (submitted by (Former Carer)) in the same manner indicates a structural problem in their internal processes for recognising and handling data‑subject rights.
In parallel, several other publishers — including Sussex Express (National World), BourneFree Live, and What’s On In Brighton (WOIB) — have not responded at all either to my collaborative proposal or to the SAR submitted by (Former Carer). This includes WOIB, which removed the article from its website but nevertheless failed to issue any SAR response, provide any Article 15 information, or communicate any lawful basis for its processing. Removal of the article does not extinguish the obligation to respond to a SAR, nor does it satisfy the transparency requirements under Articles 12 and 15 UK GDPR.
Taken together, these behaviours — misclassification by ITV and Newsquest, the identical misclassification of a formal SAR submitted by (Former Carer), and total non‑response by the remaining controllers — demonstrate a systemic failure across multiple publishers to correctly identify, classify, and process data‑protection‑related correspondence. This pattern is consistently reflected across all analytical sections of this website, from article‑level textual analysis to source‑code forensics, comparative assessments, and digital‑evidence evaluations. It raises concerns regarding the adequacy of controllers’ internal procedures, their ability to distinguish between collaborative proposals and statutory rights requests, and their compliance with the transparency and accountability principles under Articles 5(1)(a) and 5(2) UK GDPR.
