Following the withdrawal of the alt.rootbadger proposal after discussion in alt.config, RootBadger proposes a small, institutionally managed top-level hierarchy:
rootbadger.*
The purpose is to provide a clearly administered, public Usenet home for discussion specifically about RootBadger: its community, software,
operation, and its relationship with Usenet.
There is no existing hierarchy with an appropriate place for both that site-specific discussion and its hierarchy administration. The earlier alt.rootbadger proposal was withdrawn because a site-specific group under alt.* was a poor fit. A small rootbadger.* hierarchy makes the scope and
the responsible administrator explicit instead.
The initial split is deliberately narrow:
* rootbadger.general for ordinary community and project discussion;
* rootbadger.config for charters, group changes, controls, propagation,
and carriage.
This is not intended to duplicate general-purpose groups or to create a
large empty hierarchy. If traffic does not justify additional groups, no additional groups will be created. Providers also remain free to carry neither group.
The hierarchy is still only proposed. No control messages will be issued until the public review has ended and the control key, checkgroups file,
and control.ctl information are published and verified.
You have a site rootbadger.com
Just start the hierarchy on that site.
No need for control messages yet.
Look at xs4all.general as an example.
The first posts in it were start 1997
It was "officially created" september 2008
Chris Jacobs <usenet@drschrisjacobs.nl> wrote:
You have a site rootbadger.com
Just start the hierarchy on that site.
No need for control messages yet.
Look at xs4all.general as an example.
The first posts in it were start 1997
It was "officially created" september 2008
He wants it distributed.
Op 17-10-2026 om 19:30 schreef Adam H. Kerman:
Chris Jacobs <usenet@drschrisjacobs.nl> wrote:
You have a site rootbadger.com
Just start the hierarchy on that site.
No need for control messages yet.
Look at xs4all.general as an example.
The first posts in it were start 1997
It was "officially created" september 2008
He wants it distributed.
Then he should have something to distribute.
Sites are not going to carry the hierarchy if they don't find another
site to peer with.
And it would be a bad thing if they did because it would lead to
different unconnected instances of the hierarchy.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 57:40:15 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 285,926 |