How do I know, well his header contains:

Injection-Info: google-groups.googlegroups.com;
posting-host=97.126.97.251; posting-account=WH2DoQoAAADZe3cdQWvJ9HKImeLRniYW

Means he is even using google groups right now.
From his cabin in the woods:

$ whois 97.126.97.251

OrgName: CenturyLink Communications, LLC
OrgId: CCL-534
Address: 100 CENTURYLINK DR
City: Monroe
StateProv: LA
PostalCode: 71201

Mild Shock schrieb:

Ha Ha, Rossy Boy will be the first moron not able to post
anymore when they shut down Google Groups posting channel.
The rubbish he posts here is just copy pasta nonsense from
a cheap Archimedes Plutonium copy.

Ross Finlayson schrieb am Mittwoch, 24. Januar 2024 um 03:54:52 UTC+1:

Well, tapping away at this, ....

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Ross Finlayson <ross.a.finlayson@gmail.com> wrote:

[ .... ]

Basically thinking about a "backing file format convention".

The message ID's are universally unique. File-systems support various
counts and depths of sub-directories. The message ID's aren't
necessarily opaque structurally as file-names. So, the first thing is
a function that given a message-ID, results a message-ID-file-name.

Then, as it's figured that groups, are, separable, is about how, to,
either have all the messages in one store, or, split it out by groups.
Either way the idea is to convert the message-ID-file-name, to a given
depth of directories, also legal in file names, so it results that the message's get uniformly distributed in sub-directories of approximately
equal count and depth.

A....D...G <- message-ID

ABCDEFG <- message-ID-file-name

/A/B/C/D/E/F/ABCDEFG <- message-ID-directory-path

So, the idea is that the backing file format convention, basically
results uniform lookup of a file's existence, then about ingestion and constructing a message, then, moving that directory as a link in the filesystem, so it results atomicity in the file system that supports
that the existence of a message-ID-directory-path is a function of message-ID, and usual filesystem guarantees.

[ .... ]

Then, threads and the message numbers, where threading by message
number is the

header + numbers + body

the numbers part, sort of is for open and closed threads, here though
of course that threads are formally always open, or about composing
threads of those as over them being partitioned in usual reasonable
times, for transient threads and long-winded threads and recurring
threads.

Then, besides "control" and "junk" and such or relating administration,
is here for the sort of minimal administration that results this NOOBNB curation. This and matters of relay ingestion and authoring ingestion
and ingestion as concatenation of BFF files, is about these kinds of
things.

What you've described is known as a news server, and several well
established ones exist. You're trying to reinvent the wheel.

--
Alan Mackenzie (Nuremberg, Germany).

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)