🚀 go-pugleaf

rone <^*&#$@ennui.org> wrote:
>Adam H. Kerman <ahk@chinet.com> wrote:

>>It has now been three weeks. I noted the problems of hierarchy
>>administration of ba.* when the initial newgroup message for
>>ba.broadcast.moderated and incorrect "correction" booster were issued.
>>The situation has not been resolved and no one has even bothered to tell
>>us what is preventing the situation from being resolved.

>>This is a problem of extremely long standing, going back to the 1998
>>reorganization of ba.* 's configging newsgroups. The key continues to be
>>issued as if ba.news.config hadn't been rmgrouped in 1998, along with
>>the rest of ba.news.* groups. The current configging group is ba.config.

>>The entries for ba.* in control.ctl and as noted on the Web site in
>>http://ennui.org/ba/control.ctl, again because of this reorganization,
>>are not correct.

>>In the least important problem,
>>http://ennui.org/ba/ba.broadcast.moderated-charter.txt still isn't the
>>initial newgroup message, but a draft, so it's not controlling.

>>If this isn't resolved in the next few weeks and I'm so inclined, I'm
>>sure I'll mention this all again.

>Russ and i are still trying to sort this out.  I attempted to send out
>some more newgroups today but they failed to verify; my PGP keyring is
>a bit of a hash, so i am trying to clean it up and redo it.  I regret
>and apologize for the mess.

Did I misunderstand what Russ stated earlier?

The control.ctl entry and the public key on your Web site continue to
refer to the long defunct newsgroup ba.news.config. Isn't correcting all
that a necessary prerequisite to getting the key to work?

You sent more booster newgroup messages.