Hi, Dirk.
Interesting. I see the phenomenon, but I'm not convinced that it has
its boundary at six months.
You are absolutely correct. I've been checking on it quarterly since
December when the posts started aging out, with occasional spot checks in
betweeen. The last time I confirmed the posts were still aging out at six
months was the middle of March. Sometime after that the cut-off was changed
to seven months. Made a liar outta me for not double-checking that the time
limit had changed. Thanks for pointing this out.
I don't see where the retention
period is spelled out.
It's not spelled out, which means that they don't have to make a correction
to the help file whenever they up and decide to change it, like they did
last month.
Oddly, even before the September boundary, I see a good number of
threads with no rating of any kind. I'm a little puzzled at their
presence, given what the help window says about retention.
Expand the ones without ratings that are more than seven months old. You'll
see something special about at least one post in the thread, like somebody
marked a reply as "not the answer" ("0 of 1 people found this post helpful")
or a new post was added to the thread before the cut-off date. (The
application doesn't seem to be picky about what constitutes a new post,
since a new question of the same title will be added after the last reply
from the original question. Message ID's appear to be ignored in these
cases.) I think I saw only one thread older than seven months that defies
explanation in the Microsoft.Public.Access newsgroup.
I fear that this policy by Microsoft,
however well-intended or driven by practical requirements, may
ultimately force everyone to use <ptui!> the web newsreader instead of a
proper newsreader program and NNTP.
I think we're safe on this one for a while. In order to force everyone to
use only the Web portal for Microsoft's newsgroups, the repository would
have to be self-contained. In other words, Microsoft would have to refrain
from refreshing the Web portal's repository with the public news servers'
messages and publishing messages from the repository to the public news
servers. This isn't practical, even if the Web portal wasn't so buggy.
There would also be a huge drop in the number of answers posted, too,
because efficiency with the Web portal is about 60% to 70% as fast and
convenient as using a news reader, and many people would boycott newsgroups
that didn't allow them to use their choice of news readers to read and post
messages.
Update on this: I checked again and it appears that John Eddy has been
doing some housecleaning, so the percentage is now back to 60% to 65% of
threads being initiated from Microsoft's Web portal.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
Beware to those who use munged addresses: known newsgroup E-mail harvesters
for spammers are (e-mail address removed) and (e-mail address removed)