• PROPOSAL: rootbadger.* managed hierarchy

    From RootBadger@admin@rootbadger.com to news.admin.hierarchies on Sat Oct 10 19:15:50 2026
    From Newsgroup: news.admin.hierarchies

    Following the withdrawal of the alt.rootbadger proposal after discussion in alt.config, RootBadger proposes a small, institutionally managed top-level hierarchy:

    rootbadger.*

    This is a proposal for review. The hierarchy and its groups are not active,
    and no newgroup or checkgroups control messages have been issued.

    PROPOSED ADMINISTRATION

    Hierarchy: rootbadger.*
    Administrator: RootBadger
    Contact and control identity: admin@rootbadger.com
    Language: English
    Policy: Institutionally managed public hierarchy

    The hierarchy administrator would maintain the canonical group list,
    charters, checkgroups file, control-message policy, and signed control messages. Individual news servers would remain free to decide whether to
    carry any rootbadger.* groups.

    PROPOSED INITIAL GROUPS

    rootbadger.general
    Unmoderated
    General RootBadger community discussion

    Charter:

    rootbadger.general is for general discussion of RootBadger, including its community, features, culture, development, operation, and relationship
    with Usenet. Constructive criticism and independent discussion are
    welcome. Routine hierarchy-administration discussion should go to rootbadger.config.

    rootbadger.config
    Unmoderated
    Hierarchy policy and administration

    Charter:

    rootbadger.config is for proposals and discussion concerning administration
    of rootbadger.*, including group creation, removal, renaming, moderation changes, charters, checkgroups, control-message policy, propagation, and
    server carriage.

    RATIONALE

    The earlier alt.rootbadger discussion raised legitimate concerns about readership, naming, and creating a site-specific group in alt.*. A managed rootbadger.* namespace is a better technical and administrative fit. It
    makes responsibility explicit, keeps site-related groups out of alt.*, and provides one canonical administrator and group list.

    The initial hierarchy is intentionally limited to two groups. We do not
    propose support, announce, test, or topic-specific groups without evidence
    of actual traffic and need.

    DOCUMENTATION AND AUTHENTICATION

    The public hierarchy page is available without login at:

    https://rootbadger.com/usenet/

    It currently describes the hierarchy as proposed and lists both charters.
    The control-message authentication package is still pending. Before any authoritative controls are issued, RootBadger will publish and verify:

    * a dedicated OpenPGP hierarchy-control public key and fingerprint;
    * a literal-tab plain-text checkgroups file;
    * the recommended INN control.ctl fragment; and
    * stable public URLs for those materials.

    Authoritative controls will use the Usenet X-PGP-Sig/pgpcontrol format and
    will be verified before transmission. RootBadger will not claim that ISC,
    INN, Eternal September, or any provider has approved or carries the
    hierarchy unless that is independently confirmed.

    REVIEW

    Comments are requested on the hierarchy name, initial group list, charters, administration policy, authentication plan, and likely carriage. We will
    allow at least seven days for public review before asking ISC to install authorization data or considering any live control messages.
    --
    RootBadger <admin@rootbadger.com>
    https://rootbadger.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Marco Moock@mm@dorfdsl.de to news.admin.hierarchies on Sun Oct 11 10:34:30 2026
    From Newsgroup: news.admin.hierarchies

    Am 10.10.26 um 21:15 schrieb RootBadger:
    Following the withdrawal of the alt.rootbadger proposal after discussion in alt.config, RootBadger proposes a small, institutionally managed top-level hierarchy:

    rootbadger.*

    Which purpose does that have?

    Are there groups missing in other hierarchies that you would like to have?
    --
    Gru|f
    Marco

    Junk-Mail bitte an trashcan@stinkedores.dorfdsl.de
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From RootBadger@admin@rootbadger.com to news.admin.hierarchies on Sat Oct 17 13:39:26 2026
    From Newsgroup: news.admin.hierarchies

    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.
    --
    RootBadger <admin@rootbadger.com>
    https://rootbadger.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Jacobs@usenet@drschrisjacobs.nl to news.admin.hierarchies on Sat Oct 17 16:06:33 2026
    From Newsgroup: news.admin.hierarchies

    Op 17-10-2026 om 15:39 schreef 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

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Adam H. Kerman@ahk@chinet.com to news.admin.hierarchies on Sat Oct 17 17:30:59 2026
    From Newsgroup: news.admin.hierarchies

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Jacobs@usenet@drschrisjacobs.nl to news.admin.hierarchies on Sun Oct 18 17:26:12 2026
    From Newsgroup: news.admin.hierarchies

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Adam H. Kerman@ahk@chinet.com to news.admin.hierarchies on Mon Oct 19 03:03:25 2026
    From Newsgroup: news.admin.hierarchies

    Chris Jacobs <usenet@drschrisjacobs.nl> wrote:
    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.

    I didn't have a discussion with him about administering a News site for
    the groups. But yes, there should be some direct peering to help
    propogate articles. Or I suppose some already well-ccocted site could
    start things off.

    You're right.
    --- Synchronet 3.22a-Linux NewsLink 1.2