Bonum Certa Men Certa

Supplying Techrights With Leaked Material

tl;dr We prefer not to know who is sending the material

What Was New York Times Reporter James Risen’s Seven-Year Legal Battle Really for?
Reference: What Was New York Times Reporter James Risen’s Seven-Year Legal Battle Really for?



Summary: An updated advice or guidance for sending documents and/or information to us without getting caught by prying eyes, not even if we are legally threatened by an out-of-control institution that bends the law

THE number of leaked documents that we have received from EPO insiders is very high and we prefer not to comment about the number of leakers/sources. Last year, upon request, we published some tips for submitting leaks to us.

Some people requested further clarifications and some people have suggested improvements to the article since it was first published, as better options became available (not that our advice was altogether bad, just suboptimal or deficient). "Please help," one person wrote to us. "I saw your article "How to Securely Provide Techrights With Information, Documents". Could you please clarify the following in a future article?"

"We never got caught publishing anything fake, which means we have a 100% accuracy record, as far as source material goes."The main amendments suggested to us were the sorts of sites/services to use for increased anonymity/privacy/security. These sites, as one might expect, are not well known or even mainstream. Some people wish to send images, some send plain text, some send rich text, and some send documents, scans of documents, or photographs (if not screenshots) of documents. We generally think that photographs of things are less likely to leave legible watermarks (like kerning signatures) and the same goes for plain text, so it's probably safe to reduce everything down to images and plain text. We prefer not to know where these are coming from, even if we can manually remove personally-identifying metadata. It makes both us and our sources safer when neither side has identity information. Put bluntly, we typically prefer not to know where material comes from; we just need to know that it's verifiable (given context and/or accompanying explanation) and then we can cross-check to ensure its authenticity. We never got caught publishing anything fake, which means we have a 100% accuracy record, as far as source material goes. We do check everything carefully before publication. We don't wish to get tricked into publishing fake material as that would be self-discrediting and it's a commonly-used tactic for muddying the water or poisoning the well.

"I am unsure whether it is safe to send you a .pdf document," a person told us anonymously, "including text only."

We don't really need the original PDFs if there is enough to verify by; PDFs are of a clunky format type that tends to migrate with it all sorts of signatures and it drips metadata. If people can upload an image somewhere on the Web (preferably not through service such as Google's, as they have a poor record on anonymity) and then send us a link, that ought to be enough. Remailers can be used to send us anonymous messages (or links) and we can typically cope with the input without having to even reply to the source.

"We do check everything carefully before publication.""Anonmgur does no longer exist," we were told, "but Anonmgur now refers to anonimag.es as an alternative. I've tried anonimag.es, several times, but it does not work properly."

We got into some discussions last year about which image and text 'bins' are best or safest for preserving anonymity (even at the face of legal threats, which are rendered useless if logs are purged permanently). If we recommend one particular service (there are many), it will enable the surveillance lackeys at EPO to latch onto particular domains, so we prefer not to suggest just one particular service. Diversity breeds safety here.

"Thanks for updating or amending your article "How to Securely Provide Techrights With Information, Documents" so that thing become clearer for me and others," we were told, but we decided to lay things out again, rather than modify the previous article (we rarely edit old articles, except just hours after publication).

"If we recommend one particular service (there are many), it will enable the surveillance lackeys at EPO to latch onto particular domains, so we prefer not to suggest just one particular service."To date, the most damaging EPO leak was probably this one. It generated a lot of media coverage and caused a great stir among EPO stakeholders, who rightly felt like they had been discriminated against.

Today or last night Research and Markets published details about an upcoming one-day seminar with tips for EPO applications and another for advanced drafting. We could not help joking about it because in today's EPO it seems like anyone can just pay under the table or lobby for preferential treatment. We are certain that many examiners have come across examples of that and we hope for more leaks to that effect.

"Like any publication out there, we strive to have impact, as do our sources."Regarding the timing of disclosure, it's not always immediate (upon receiving material) because we need to verify authenticity, we need to wait for relevant development/news, and sometimes there are two connected stories that we investigate at the same time and they can be fused together. Like any publication out there, we strive to have impact, as do our sources. So if we don't release something promptly, then there is probably a reason behind it. We rarely post teasers (quite rarely we do, for a change) because the element of surprise enables us to catch the EPO's management, for example, unprepared and unable to properly respond, distract, or undermine publication (as attempted in the past).

Recent Techrights' Posts

Windows is an Unnatural Disaster, It is Also Avoidable
there's a wide window of opportunity opening
Killing the News With Spam and Slop Benefits Those Whose Desire is an Uninformed Population
adoption of Free software depends indirectly on political activities/activism
Open Source Initiative (OSI) Privacy Fiasco in Detail: An Introduction
Perhaps tomorrow or perhaps next week we'll share more information about what happened and what was reported to the California Privacy Protection Agency
IBM's BS (Bait, Switch) Regarding Ways to Stay Onboard
PIPs, RTOs, and forced relocations are just an illusion of choice (or ability to recover)
Banned evidence: Ars Technica forums censored email predicting DebConf23 death, Abraham Raji & Debian cover-up
Reprinted with permission from Daniel Pocock
 
Links 30/03/2025: "Quantum Randomness" and "F-1 Visa Revoked" in US
Links for the day
Gemini Links 30/03/2025: US as a Threat, Returning to the WWW
Links for the day
Links 30/03/2025: Judge Blocks Dismantling Of VOA, Turkey Arrested Many Journalists
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, March 29, 2025
IRC logs for Saturday, March 29, 2025
Judges Would Never Rule for Men Who Strangle Women or Against Women Who Merely Wrote Articles About Abuse They Had Received From Men
We don't intend to do "trial by media", so we won't be disclosing claims and defences until it's over
Gemini Links 29/03/2025: Less YouTube and More Station
Links for the day
In Some Countries, Such as Thailand, Firefox is Already Measured at Less Than 2% (One Day Firefox Will Get Blocked, Not Only Lack Support)
Web consolidation around Chrom-isms will doom the Web as we know it
Links 29/03/2025: Trademarks Battles, Fires Destroy More Than 3,000 South Korean Homes
Links for the day
Links 29/03/2025: More Crackdowns on Science, "Hey Hi" Slopping is Flopping
Links for the day
Costa Rica Almost Bankrupt Because of Microsoft
the incidents in Costa Rica are Windows incidents
Gemini Links 29/03/2025: Art of Looking, Wireguard, EMacs
Links for the day
Links 29/03/2025: Attacks on Social Security and War Updates
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, March 28, 2025
IRC logs for Friday, March 28, 2025
Intimidation, Threats, and Bullying Not Tolerated by Techrights
When it comes to our reporting, safety always comes first
A World Without Rules
We're long insisted on better laws and actual enforcement of them (applicable to all, not selectively applied)
statCounter Sees Microsoft Windows Falling to New, Unprecedented Lows in Palau
Taking Android into account, Windows is now down to an all-time low of 14%
Google News Lost the Fight to LLM Slop (While Google Itself Sells Slop, Nowadays Under the Name "Gemini")
Many people say that "Google is getting worse"; that's almost an understatement
Links 28/03/2025: AirAsia Trouble Again, UMich Culls All DEI Programs
Links for the day
Gemini Links 28/03/2025: Alexa is for Gullible People, Rant About Feature Overload
Links for the day
The SLAPPs From the Microsoft Strangler (and Sidekick) No Better Than Patent Trolling
one must never settle with trolls
Something to Celebrate in Gemini Protocol
More capsules and users join in
Links 28/03/2025: Last Reminder "to Delete Your 23andMe Data", "UK's First Permanent Facial Recognition Cameras Installed"
Links for the day
Microsoft Canonical Continues Its FUD (Fear, Uncertainty, Doubt) Campaign, Reveals Google Too Sponsored It
They're paid-for lies from a Chinese company that takes GAFAM money to write puff pieces about them
Android Rises Above 76% in Mozambique, Leaving Windows in the Dust
Windows may soon be measured as smaller than Apple's iOS
IBM, Red Hat and Microsoft Probably Also Manipulate Metrics (It Helps Con the Shareholders)
Wall Street's credibility will depend on enforcement of "checks and balances"
Slopwatch: trendhunter.com and Other Pure Junk From "Google News"
The need to vet sources is hardly new; anyone can spew out anything, anywhere. There's a need for vetting.
Gemini Links 28/03/2025: Rewatching The X-Files, Slop Concerns, and NOSTR Censorship
Links for the day
Links 28/03/2025: Australia at Risk, EPO Grants Illegal Patents With Illegal Effect
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, March 27, 2025
IRC logs for Thursday, March 27, 2025