>First, I want to thank Dan for continuing to support HyperNews.
Thanks for your support.
Part of the reason I continue is that I haven't achieved my original
goals. See the /hypernews/evolution forum for what I was originally
thinking.
>My questions continue! Are the group identifiers in .hngroupmembers
>important?
Not any more. There were several server bugs we had to work around that
resulted in the current design. But 1.9.7 will remove the .htgroup* files
altogether because they are not needed any more. I don't really want to
spend time documenting what we did.
>How are they generated? More specifically, how did some of my
>identifiers end up as "All1"?
The "All" group is for the top level - it has to have some name in
the group file. We can't put too many members on one group line,
so the group is subdivided into multiple subgroups, All1 through Alln.
Other installations can have their own groups and .htgroup files, and you
give them each a group name.
>... JS takes care of filling in the unique info for
>each installation and submitting to the different URLs.
Hmm. Neat, but do you look at the separate results somehow?
Maybe the setup is failing in some way that you can't see.
>When are you releasing the next version? Will it be a set of fixes, or
>are you going with new functionality, too? Will it be v2.0.0?
I was hoping to release 1.9.7 in a couple days. I suppose there are enough
changes in this version that it deserves some beta testing.
The 2.0 series will happen when the changes are drastic enough that
I am forced to drop compatibility with earlier versions. I havent really
started implementing it, but design ideas have been accumlating for a couple
years, and supporting libraries are only getting better.
dan
|
Grouips and versions 
.hngroupmembers
(Jim Gallagher)
Thanks! How about....
(Jim Gallagher)
MOre groups and versions
by Jim Gallagher, 1998, Jun 05
