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

FOSDEM is Called "FOSDEM" Because of Richard Stallman (RMS)
The overlap there seems timely; yesterday RMS spoke in French-speaking (in part) Switzerland where questions in French were accepted
Video: University in Peru Honours Richard Stallman
Tomorrow, January 20, Richard Stallman speaks in France
 
[Meme] 404, Not Found
Kuhn: I'd like to interject for a moment, we made an alliance with the Microsoft-dominated LF to outsource projects to Microsoft GitHub and rich people gave us money to do this
Total Lock-down Ambitions - Part IV - The Latest Examples and the Perils (in Summary)
For further reading take a look at Musial's nice outline
Links 19/01/2025: Gaza Ceasefire and PR Stunt by Fentanylware (TikTok), Faking It by "Going Dark" to Incite American Addicts (Users)
Links for the day
Links 19/01/2025: TikTok (Fentanylware) Now Banned in the US, Convicted Felon Talks to Fentanylware CEO and Pooh-Tin About Undoing the Ban Despite the Supreme Court Unanimously Upholding It
Links for the day
FTC Realises Microsoft Buying Fake 'Clients' to Fake "Revenue" (Microsoft 'Buying' Services and Products From Itself!)
Ponzi scheme
Total Lock-down Ambitions - Part III - The Web Browser as DRM Pusher
A lot of "streaming" stuff is DRM
IBM Termination Story and Information From Microsoft About Mass Layoffs
In 2 weeks of 2025 Microsoft already had 2 waves of layoffs
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, January 18, 2025
IRC logs for Saturday, January 18, 2025
Links 18/01/2025: Restoring the Great Wall of China and Economic Expansion in China
Links for the day
Guardian Digital (linuxsecurity.com) is Spamming the Web With Microsoft's Promotional LLM Slop About UEFI 'Secure' Boot (Which is Against Real Security)
This is an attack on honest journalism
Links 18/01/2025: TikTok's Endgame, "Car Freedom", and Spying in Cars 'Fines' GM (Settlement)
Links for the day
January 20: Richard Stallman Talk in Europe
evening time in Europe, around midday in the United States and Canada
Links 18/01/2025: Apple Getting Out of Hey Hi (AI) Slop (Too Much Misinformation), Chaffbots/Chatbots Try to Settle Copyright Infringement Lawsuits
Links for the day
What Fake News Sites Are Doing to GNU/Linux
The LLM slop about Linux serves two purposes
Links 18/01/2025: Microsofters Upset at Microsoft's Ridiculous Rebrands (Excuse for Massive Price Hikes), Chaffbot Company ('Open'AI) Faces More Lawsuits
Links for the day
Gemini Links 18/01/2025: Surge in Illnesses, ctags, and Gemsync
Links for the day
Slopwatch: Too Lazy to Write Real Articles, Offloading to Chatbots Instead (LLM Slop About "Linux")
The Web was already full of garbage before the LLM frenzy. Now it's even worse.
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, January 17, 2025
IRC logs for Friday, January 17, 2025
RMS 'Inauguration' in Montpellier (Government Administration) on January 20th
Happy hacking
Even Technical Articles and HowTos From UNIXMen Nowadays Seem to be LLM Slop
We've just permanently removed the RSS feed of UNIXMen
The FSF's 2024 End-of-Year Fundraiser Succeeds: Over $400k to Support Software Freedom
That's worth bringing up again because the SFC is trying to 'crash' this achievement of the FSF
[Meme] Fentanylware (TikTok) Banned in the United States, Next Up European Union (EU)
And the United Kingdom (UK)
President Biden is Right, "Free Press is Crumbling" and the United States Exports Its Media-Hostile Culture to Other Continents
perhaps Biden should pay closer attention to how Donald Trump-inspired Americans take their battles to other continents
Links 17/01/2025: TikTok Banned by the United Stated (SCOTUS Rejects Appeal)
Links for the day
Software Freedom Conservancy Inc (SFC) Makes It Obvious It's Just a Copycat Trying to Exploit or Leech Off the FSF's (and GNU's) Work
They swim next to the rich people (who "match")
Links 17/01/2025: Fentanylware (TikTok) Herds Its (Drug) Users Into Even More Harmful "Apps"
Links for the day
Guardian Digital, Inc (linuxsecurity.com) Uses Microsoft-Controlled Front Groups and LLM Slop in Order to Spread Microsoft-Directed Anti-Linux FUD
Microsoft garbage likely produced by Microsoft LLMs, spewing out Microsoft FUD
Likely Fake 'Article' About Linux Mint 22.1
BetaNews fired up its plagiarism machine (LLM)
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, January 16, 2025
IRC logs for Thursday, January 16, 2025