Skip to main content
RootBadger RootBadger

Hierarchy information

RootBadger Usenet Hierarchy

Official administrative information for the proposed rootbadger.* hierarchy.

Current status

Status: Proposed — not yet active

No authoritative newgroup, rmgroup, or checkgroups control messages have been issued for rootbadger.*.

Overview

rootbadger.* is a proposed public, managed Usenet hierarchy for discussion of RootBadger, its community, software, operation, and administration.

The hierarchy is administered by RootBadger. Individual Usenet servers decide independently whether to carry its newsgroups.

Administrator

Hierarchy
rootbadger.*
Administrator
RootBadger
Contact
admin@rootbadger.com
Language
English

Proposed initial groups

rootbadger.general

Status: Proposed, unmoderated
Description: 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 discussions should go to rootbadger.config.

rootbadger.config

Status: Proposed, unmoderated
Description: Hierarchy policy and administration

Charter

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

Administration policy

The rootbadger.* hierarchy is an institutionally managed hierarchy administered by RootBadger. Proposals concerning its group list may be discussed publicly in rootbadger.config after that group becomes active.

The hierarchy administrator makes final decisions concerning group creation, removal, renaming, moderation status, and charter changes. Decisions will consider demonstrated need, expected use, naming clarity, technical feasibility, and feedback from users and news administrators.

Changes to the canonical group list will be published through authenticated control messages and reflected in the hierarchy’s official checkgroups file.

Participation and abuse policy

Participating servers and users remain subject to their own providers’ policies. Spam, flooding, malware, doxxing, illegal material, and deliberate disruption are not welcome within rootbadger.*.

Criticism of RootBadger is permitted. The hierarchy is intended for legitimate independent discussion and is not solely a promotional channel.

Each server remains responsible for its own access controls, filtering, retention, and abuse handling.

Control-message authentication

Control-message authentication package: Pending

A dedicated OpenPGP hierarchy-control key, public fingerprint, canonical checkgroups file, and recommended INN control.ctl configuration will be published here before any authoritative control messages are issued.

Information for news administrators

News administrators will remain free to carry all, part, or none of rootbadger.*. Publication of hierarchy information or control messages does not require an independent server to honor or carry the hierarchy.

Questions concerning hierarchy policy, future control messages, group status, or abuse may be sent to admin@rootbadger.com.

Last updated: