PROPOSAL: alt.rootbadger
This is a proposal for the creation of the unmoderated newsgroup >alt.rootbadger. Comments, objections, naming suggestions, and charter >changes are welcome in alt.config.
PROPOSED NEWSGROUPS FILE ENTRY:
alt.rootbadger Discussion of RootBadger, a Usenet-inspired discussion platform
RATIONALE:
. . .
RootBadger is a web-based discussion plat
The proposed name uses the platform's established proper name. The direct >second-level name is short, unambiguous, and easier to discover than an >invented classification beneath an unrelated branch of alt.*.
CHARTER:
PROCEDURE:
This proposal is being posted to alt.config for public discussion before any >newgroup control message is considered. The proponent will monitor this >thread, answer reasonable questions, and revise the name, description, or >charter when the discussion identifies a useful improvement.
At least seven days will be allowed for discussion. If the proposal remains >viable after that period, a properly formatted newgroup control message may be >issued with a summary of the alt.config discussion, the final newsgroups file >entry, the charter, and a justification of readership. Individual news >administrators will decide whether to honor and carry the group.
HISTORY:
2026-10-03: Initial proposal, version 1.
RootBadger <admin@rootbadger.com> wrote:
PROPOSAL: alt.rootbadger
You don't need to name it at the second level. You aren't starting a second-level hierarchy. Find other newsgroups discussing Web forums and name it into an existing second-level hierarchy.
I advise you to provide support within your own platform and not on Usenet. This is, effectively, a proposed advertising group if not a vanity froup.
You cannot force Usenet users to discuss your product or service just
because you might send a newgroup message. That's not how it works.
This is a proposal for the creation of the unmoderated newsgroup
alt.rootbadger. Comments, objections, naming suggestions, and charter
changes are welcome in alt.config.
Oh, for fuck's sake. YOU get the charter correct in the proposal. THE
INITIAL NEWGROUP MESSAGE IS PERMANENTLY ARCHIVED AND NOT CHANGEABLE.
PROPOSED NEWSGROUPS FILE ENTRY:
Bad syntax. Read Russ's README. Do not guess the syntax.
ftp ftp.isc.org cd pub/usenet/CONFIG get README
alt.rootbadger Discussion of RootBadger, a Usenet-inspired discussion
platform
The one thing that's correct is the use of a tab character. Congratulations. The description is supposed to be a phrase with keywords that don't include components of the group name. Use of "discussion" twice is ridiculous and it's not a key word. Usenet isn't a keyword. Platform isn't a key word.
RATIONALE:
No rationale. RATIONALE is Big 8 nonsense to promote "yes" votes. Big 8 stopped voting decades ago and alt.* never had voting. In alt.*, we do justification, which is a count of articles discussing the topic. 10
articles a day over a recent 90-day period is the aim, else you get a group that won't be used.
As this is advertising/vanity and you are the only one initiating
discussion, this group cannot be justified.
. . .
RootBadger is a web-based discussion plat The proposed name uses the
platform's established proper name. The direct second-level name is short, >> unambiguous, and easier to discover than an invented classification beneath >> an unrelated branch of alt.*.
Your objection is "invented classification"? That's offensive. Any result of human activity had to have been invented first.
I strongly advise you not to fill your proposal with bullshit like that. In truth, you took no care in naming.
Vanity froups don't belong in alt.*. They cannot be justified. But you could start an institutional hierarchy at the top level.
rootbadger.*
Start with a rootbadger.general group. This has perhaps more likelihood of success than a vanity froup in alt.*. There is no need to justify a new top-level hierarchy.
Read Russ's Usenet Hierarchy Administration FAQ posted to news.admin.hierarchies.
I have no comment on your charter. My advice is not to proceed with an
alt.*, especially named at the second level because you simply reject alt.* taxonimy to the extent it exists. Groups for advertising and vanity projects do not succeed in alt.*.
An institutional hierarchy would be named at the top level. There is no justification process. Declaring yourself hierarchy administrator just means sending a different control message, checkgroups, and informing Russ. If you want it added to rone's control.ctl which is shipped with INN, you'll need
to do GPG. It's explained in the FAQ.
This is advice. Any fool may send an unwanted newgroup message in alt.* as the hierarchy is unadministered.
Traditionally, one overreacts at this point because I am attempting to discourage this vanity proposal in alt.* for a group no one would use.
CHARTER:
I have no comment.
PROCEDURE:
Big 8 boilerplate does not belong in an alt.* newgroup proposal. The Big 8 loves its boilerplate, utterly hated by the rest of Usenet.
This proposal is being posted to alt.config for public discussion before any >> newgroup control message is considered. The proponent will monitor this
thread, answer reasonable questions, and revise the name, description, or
charter when the discussion identifies a useful improvement.
At least seven days will be allowed for discussion. If the proposal remains >> viable after that period, a properly formatted newgroup control message may >> be issued with a summary of the alt.config discussion, the final newsgroups >> file entry, the charter, and a justification of readership. Individual news >> administrators will decide whether to honor and carry the group.
Again, this doesn't belong in a proposal. As long as you don't fuck up the syntax, your newfroup will get archived and acted upon by the INN server at ftp.isc.org.
The rest of Usenet will remain apathetic and ignorant. Newfroup messages don't create discussions, nor do they create newsgroups till a user requests creation locally. That's not how Usenet works.
Decades ago, there were a handful of "trusted rmgroupers" who attempted to enforce the 7-day discussion period. Generally they were poorly regarded and they all went away. After numerous Hipclone DoS atacks with massive numbers of control messages, administered hierarchies began signing checkgroups and most News sites stopped automatically creating groups in unadministered hierarchies locally. Lacking a user request, the group won't be created locally. Sorry, but this is why advertising/vanity groups like this don't
get widely created.
HISTORY:
2026-10-03: Initial proposal, version 1.
Versioning is more Big 8 nonsense.
Thanks for the detailed procedural correction. I will review the CONFIG >README and the hierarchy-administration FAQ rather than treating the >seven-day mark as a deadline to issue a control message.
The readership objection is substantive. The intended group is for >third-party discussion, criticism, support, and public operational notices, >not advertising, but intent does not demonstrate likely traffic. I will not >claim readership evidence that is not present.
I will also compare an institutional rootbadger.* hierarchy and suitable >existing alt.* branches before proceeding. If a revised alt.* proposal >cannot supply a defensible name, newsgroups-file description, and readership >justification, I will not force this proposal through.
If you go the institutional top-level hierarchy route and send
GPG-signed checkgroups, once it's listed in rone's control.ctl, that
might be enough for some News sites to process your control messages automatically, even without a user request.
If you go the institutional top-level hierarchy route and send
GPG-signed checkgroups, once it's listed in rone's control.ctl, that
might be enough for some News sites to process your control messages automatically, even without a user request.
On Oct 3, 2026 at 11:53:14 PM CDT, Adam H. Kerman <ahk@chinet.com> wrote:
If you go the institutional top-level hierarchy route and send
GPG-signed checkgroups, once it's listed in rone's control.ctl, that
might be enough for some News sites to process your control messages >>automatically, even without a user request.
The public key has to be added to the local keyring by the news admin.
New hierarchies will have slow uptake regardless.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 57:39:29 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 285,926 |