n a matter of ~2 weeks Wikileaks (not Wikipedia) is turning 20. I used to write a great deal here about Wikileaks and some accounts associated with Wikileaks wished to replicate some of my posts.

Over the years many pro-Wikileaks accounts perished in Twitter (now X) and Wikileaks’ Twitter handle has been dead for months. I wonder if Wikileaks will bother saying anything at all on the day it turns 20.

here are LOTS of Microsoft layoffs right now. Insiders know it, but they cannot speak about it (too risky). Media does not report these. It’ll conveniently – in an arse-covering fashion – dismiss that as “rumours” and say, no WARN notices. But Microsoft bypasses the law. It says, “we’ll fire you unless you agree to this ‘voluntary exit’ agreement, then sign an NDA to keep quiet and outwardly happy about it.”

Same for PIPs and LITE.

IBM and Microsoft have TENS OF THOUSANDS of layoffs this year. Unlike Oracle, they hide these.

Below are articles from 2026:

began my school days with a notebook. Then notebooks. Pupils like myself learned how to read and write. We used notebooks. We had a blackboard, later a whiteboard (for health reasons). It generally worked. It can still work.

Earlier this year I used a notebook extensively to take notes. This week I begin turning those notes into digital articles. It’s not about copying the thing word by word. Typing is faster than writing and gives more time to consider one’s choice of words or which words are most important to capture.

Nostalgic. Yes, but it works.

am very proud to say that our persistent ‘activist’ writings (journalism) have worked. This is paying off. We also earn positive publicity (press) for it.

Techrights, for example, is making strong progress this year regarding much-needed SLAPP reform. To be clear, this is NOT about a single incident, it is about changing the whole system.

Days ago I also resumed coverage regarding patents. We are making the public aware of important issues. I say “we” because we began working with other publishers. They recognise this cannot go on.

he newspaper of 5 years ago is not read today.

The newspaper of today will be read today.

The newspaper of 5 years ago had impact 5 years ago.

What happened 5 years ago impacts what happens today.

5 years ago there were many days, many newspapers, and each thing reported each day impacted and still impacts the present.

So just because people no longer read newspapers from 5 years ago doesn’t mean the articles in them are of no impact.

t is fair to say that this blog is a lot more active this year than it has ever been. This was a conscious decision and one that I regret not making sooner. I still have many old PDFs and documents of a personal nature – ones that I wrote two decades ago. I estimate that the combined total of these is 200-300 pages. The plan was to revisit them some time in the future, maybe turn these into something publishable.

At the moment I try to focus on exposing wrongdoing, or use writings to illuminate to a large audience things they ought to be aware of.

Yesterday, for instance, I learned from reliable sources that cuts and mass layoffs at Microsoft are massive and under-reported. They still go on next month, but where is the media?

t’s already autumn (by some calendars) and today we resume a series about the EPO and another about the SRA over at Techrights.

We expect this coverage about these scandals to last well into next year. We have patience and resilience.

These are matters of public interest.

oday in the evening (or earlier tonight) I was typing up a rather long article in Techrights, where I am the main editor.

As usual, what typically happens is, strands (or trains) of thoughts quickly become streams of words, and words add up to sentences, paragraphs, then a draft of an article. Then I go through the article, which tends to be coherent as it was typed in one go (after planning, having had some time to condition myself to put together a topic to write about in the ‘correct’ sequence), I correct typos, improve the wordings, add some more links etc. (where suitable and readily available)

I do this on a remote laptop connected over the LAN with Barrier, so if there’s a network glitch it can result in lost keystrokes and long repeated keystrokes.

Not for the first time, the latter happened when I pressed “undo” (ctrl+z), so it began undoing things I edited, in effect deleting amendments made for several minutes (far worse than when it happens with backspace as the cursor goes all over the place). Typically I’d be “hands-off” when that happens, then re-do what was omitted. This time, however, two things went wrong: 1) I did not keep “hands-off”, not long enough anyway; so I could not re-do all the way. 2) I did not press ctrl+s (save) for quite some time, so reverting back to the file on disk wasn’t a possibility either. I tried, I even did so from another laptop.

Shit!

I lost some work.

On the bright side: 1) I remembered more or less 80% or more of the changes that I made and could reconstruct a lot (with slight variation, imperfect replication, maybe even better the second time around). 2) not much was lost (either words or time). 3) it was only the editing/correcting pass, not the writing pass. 4) there was a lesson or wake-up call here. I should take advantage of it.

I will probably still take the risk of writing over Barrier, but I need to save to disk more often and be vastly more prudent/careful when undoing gets ‘jammed’. There should be a way to re-do (ctrl+shift+z) everything and, failing that, there’s a file on disk that maintains a recent copy, not what’s on the screen/buffer.

My editing skills typically use past experience (incidents) to reduce chance of loss/error, so my wife was surprised that it happened to me. Writing this blog post probably takes a lot more time than the time the incident ‘cost’ me.

I wonder if other people can relate to this.

I’ve had a lot of time to think about this (over an hour already), so documenting to myself – and maybe to others too -what happened can be hopefully prove useful.

There is no perfect (error-proof) way to edit text, but there are ways to reduce the risk and the cost of mistakes/crashes.

was very serious when I said we’d take it up another notch after our long vacation. Right now I watch back as there are about 20 new blog posts since midnight (it’s only 5AM here). The headsup was based on the devotion of time, or based on the general allocation of resources. We now put foot on the metal/pedal, or push the pedal to the metal throughout the day today, as we expect more tactical intimidation and bullying from hired guns who are extremely rude. Yesterday tuxmachines.org served 665,042 Web requests and techrights.org served 479,275 (not the same as visits).

The sites’ reach only grew since the lawfare began 3 years ago (it was always Americans, it’s still only Americans).

Fast-forward many years and now I speak to millions, not hundreds. With exposure comes envy, however, and envy leads to litigiousness.

I’d rather choose the latter (with the price of litigiousness) than remain an obscure Ph.D. student who attends lectures.