Path: ...!fu-berlin.de!uni-berlin.de!not-for-mail From: ram@zedat.fu-berlin.de (Stefan Ram) Newsgroups: news.software.nntp Subject: After a server reboot from scratch . . . Date: 10 Sep 2024 10:14:37 GMT Organization: Stefan Ram Lines: 18 Expires: 1 Jul 2025 11:59:58 GMT Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: news.uni-berlin.de 3X7aj1vPcxIhJrvjISZ5BQvSKSEPN1luXNBREN0srJHojD Cancel-Lock: sha1:gaiMK6cDylN8yvDgVruo/OeWsNk= sha256:Oe42uN+OqTR3AGFUZ4sS0uAuk43dwhks8++i2B8JNyY= X-Copyright: (C) Copyright 2024 Stefan Ram. All rights reserved. Distribution through any means other than regular usenet channels is forbidden. It is forbidden to publish this article in the Web, to change URIs of this article into links, and to transfer the body without this notice, but quotations of parts in other Usenet posts are allowed. X-No-Archive: Yes Archive: no X-No-Archive-Readme: "X-No-Archive" is set, because this prevents some services to mirror the article in the web. But the article may be kept on a Usenet archive server with only NNTP access. X-No-Html: yes Content-Language: en-US Bytes: 2113 When a newsserver gets wiped clean and built from the ground up, like after the machine bites the dust, the articles in a newsgroup might end up with new numbers slapped on them, from what I know. So if a client's been keeping tabs on what it's already peeped, thinking "I've already eyeballed article number 1 from Group G", that info's now totally out to lunch. The client oughta treat this reborn server like it's fresh off the lot, even if it's rockin' the same web addy as before. But I reckon the user's got to step in and work some magic themselves. Or is there already some kind of official playbook for this scenario, where the server can give the newsreader a heads up via the NNTP protocol that it's sportin' a whole new article numbering in the newsgroups?