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

Michael “Monty” Widenius: It Started in 1983 With Richard Stallman (RMS)
The other co-founder of MySQL is a bit notorious for confronting RMS rather viciously
For the Second Time in a Few Weeks Microsoft Lunduke Makes False Accusations Against Senior Red Hat Staff to Incite a Despicable 'Troll Army'
Nothing that Microsoft Lunduke claims of says can be trusted
su lisa && rm -rf /home/ibm/power
Novell was ruined by another person from IBM, Ronald Hovsepian
A Record Demand at Microsoft: Demand to Cancel
What we're witnessing is a very ungraceful destruction of XBox
 
Links 03/10/2025: Conflicts, Death of TypePad, and TikTok/CheeTok Gives a Boost to Far Right Groups in Europe
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, October 02, 2025
IRC logs for Thursday, October 02, 2025
Slopwatch: Linux Journal, Google News, and LinuxSecurity
They carry on polluting the Web with fake articles
Gemini Links 02/10/2025: Kubernetes With FreeBSD and robots.txt
Links for the day
Links 02/10/2025: 'Open' 'AI' Resorting to Gimmicks and Fake Funding, Europe’s ‘Drone Wall’ Discussed
Links for the day
Links 02/10/2025: Brave Passes 100M Users Milestone, Kodak Selling Its Own Film Again
Links for the day
Microsoft is Losing Europe
Hence all the "support" and "discount" offers that are limited to Europe
The Free Software Foundation Starts Fund-raising for 40th Anniversary
New pop-up 2-3 days ahead of the 40th anniversary event
Systemd Breaks Networking in Debian and Microsoft Staff Rushes to Make Face-Saving Excuses in LWN
Microsoft's bluca is already there in the comments, his Microsoft money pays for LWN to let him leave comments early
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, October 01, 2025
IRC logs for Wednesday, October 01, 2025
What the End of XBox Will Look Like: a Fiery Crash
XBox is the next Skype. It won't last much longer. Expect many more layoffs.
Richard Stallman is Going to Finland to Give a Talk Next Thursday
A day later he speaks in Sweden
Gemini Links 02/10/2025: SMTP Pipelining and End of ROOPHLOCH 2025
Links for the day
Slopwatch: Plagiarism, Fake Articles, and FUD About Linux
not a day goes by without Google News feeding FUD from slopfarms
Gemini Links 01/10/2025: Chat Control and End of Life
Links for the day
Links 01/10/2025: Long Covid Risk Reiterated, "Bitcoin Queen" Caught
Links for the day
Links 01/10/2025: EA $55 Billion Deal is Debt and Slop "Raises Vishing Risks"
Links for the day
Bluewashing at Red Hat Means Redundancies
The man who sold Red Hat to IBM meanwhile became a Microsoft Mono booster
After Killing OpenSource.com, IBM ('Red Hat') and OSI Told Us OpenSource.net Would Replace It (But That Didn't Happen)
Now it's time to move on, perhaps tarnishing the "Open Source" label some more (for whatever sponsor wants this)
Linux is Not a Community Project, It's a Wall Street Product
The core goal should be freedom
Bad Actors Abusing the Free Software Community, Vandalising It Using Rogue Politics and Old Tactics
Oil giants have long attempted to do this; now, the digital equivalent of Big Oil does this in technology
Social Control Media Isn't the Future, The Federation or Fediverse Isn't Growing, People's Accounts Vanish for Good
users' accounts will get deleted, not just become inactive
IBM is Failing, This Helps Show Wall Street is Entirely Detached From Actual Commercial Performance
IBM is unable to grow, it's just constantly shrinking
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, September 30, 2025
IRC logs for Tuesday, September 30, 2025
Clerical Aspects of Publishing and Development
In Free software, the management aspects are considerably reduced
Slopwatch: Fake Articles and Google News Promoting "Linux" Spam or Bot-Generated Fear, Uncertainty, Doubt (FUD)
These slopfarms help misplace blame
Third Wave of Microsoft Layoffs in September, This Time Many in Liverpool Affected
Be ready for more waves of layoffs ahead of the so-called "results" in late October