• PROPOSAL: alt.rootbadger

    From RootBadger@admin@rootbadger.com to alt.config on Sat Oct 3 14:28:14 2026
    From Newsgroup: alt.config

    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 platform inspired by Usenet. It uses named discussion groups, threaded conversations, and community-oriented administration while remaining accessible through an ordinary web browser.

    The proposed newsgroup would give Usenet participants and RootBadger users a neutral, public place on Usenet to discuss the platform itself. It would be useful for setup and usage questions, software and feature discussion, bug reports, group suggestions, public service announcements, and feedback from people who prefer reading and writing through NNTP.

    The group is not intended to replace the discussions hosted on RootBadger.
    Its subject is the RootBadger platform, its operation, and its community as a whole. A dedicated group would keep that meta-discussion out of unrelated technical, regional, political, and social newsgroups.

    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:

    alt.rootbadger is for discussion of RootBadger, a Usenet-inspired web discussion platform available at https://rootbadger.com.

    On-topic subjects include:

    * Using and navigating RootBadger.
    * Questions about accounts, posting, groups, threading, and site features.
    * Bug reports, troubleshooting, accessibility, and usability feedback.
    * Feature requests and discussion of future development.
    * Proposals for RootBadger groups and community organization.
    * Public announcements about availability, maintenance, policy, and releases.
    * Constructive comparison of RootBadger with Usenet and other discussion
    systems.
    * Discussion of public RootBadger content when the platform itself or its
    community practices are the main subject.

    The following are off-topic:

    * General conversations that merely happen to resemble topics discussed on
    RootBadger but do not concern the platform.
    * Unsolicited commercial advertising, repetitive promotion, or link spam.
    * Binary attachments. Short signatures and normal textual references are
    acceptable.
    * Doxxing, threats, impersonation, or publication of private account data.
    * Requests or instructions intended to compromise accounts, servers, or other
    systems.

    The group will be unmoderated. Participants are asked to use descriptive subjects, quote only what is needed, post in plain text, avoid excessive cross-posting, and direct reports involving private information or security issues to admin@rootbadger.com rather than posting sensitive details publicly.

    The charter is intended to define the group's initial scope. As with other unmoderated alt.* groups, cooperation and community consensus will be the practical means of keeping discussion useful.

    PROPONENT:

    RootBadger <admin@rootbadger.com>
    https://rootbadger.com

    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>
    https://rootbadger.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Adam H. Kerman@ahk@chinet.com to alt.config on Sat Oct 3 18:09:36 2026
    From Newsgroup: alt.config

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Tom Mix@tommix@mixmin.net to alt.config on Sat Oct 3 21:01:15 2026
    From Newsgroup: alt.config

    In article <119rgd0$384c4$1@dont-email.me>, "Adam H. Kerman" <ahk@chinet.com> wrote:

    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.

    We will do what we want, Adam. You have no say in it. You are are a
    nobody. I bet you're too coward to even respond to me.

    Oh, and Steve Leyland sends his regards.
    --
    Tom Mix
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From RootBadger@admin@rootbadger.com to alt.config on Sun Oct 4 02:37:02 2026
    From Newsgroup: alt.config

    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.
    --
    RootBadger <admin@rootbadger.com>
    https://rootbadger.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Adam H. Kerman@ahk@chinet.com to alt.config on Sun Oct 4 04:53:14 2026
    From Newsgroup: alt.config

    RootBadger <admin@rootbadger.com> wrote:

    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.

    Thank you for being reasonable. alt.* has thousands of unjustified
    newsgroups that are largely forgotten or never had an audience.

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From RootBadger@admin@rootbadger.com to alt.config on Sat Oct 10 14:47:30 2026
    From Newsgroup: alt.config

    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.

    Understood. The readership justification for alt.rootbadger remains unsupported, and the naming and vanity-group objections are substantive.
    I am therefore withdrawing the alt.rootbadger proposal. No newgroup control message will be issued for it.

    Any future rootbadger.* hierarchy would be a separate effort, undertaken only after its governance, public administration files, signing key, and news-admin process are properly established. It is not a continuation of this proposal.

    Thanks for the procedural guidance.
    --
    RootBadger <admin@rootbadger.com>
    https://rootbadger.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jesse Rehmer@jesse.rehmer@blueworldhosting.com to alt.config on Wed Oct 14 05:00:46 2026
    From Newsgroup: alt.config

    On Oct 3, 2026 at 11:53:14rC>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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Adam H. Kerman@ahk@chinet.com to alt.config on Wed Oct 14 15:32:26 2026
    From Newsgroup: alt.config

    Jesse Rehmer <jesse.rehmer@blueworldhosting.com> wrote:
    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.

    That is certainly true, and I didn't intend to imply that it would happen automatically.

    New hierarchies will have slow uptake regardless.

    True, but users have no motivation to request creation of an alt.* group
    of this nature which is why I discouraged it.

    If his proposed hierarchy appears to be well administered, some News
    site might add it. User requests are unlikely in the extreme.
    --- Synchronet 3.22a-Linux NewsLink 1.2