03 Oct 23: One server has been relocated, the server currently doesn't have a public IP address in the meantime. I wrote some additional tunnel code running separately to handle this. When the server is engaged the connection is 5600+ days uniform (since around 24 July 2008). In the unlikely case I disengaged the server because of some problem the retention is 1200-3800 days depending on newsgroup. If you experience any issue please let me know.
29 Nov 23: Because of encrypted and "obfuscated" flood mass posted by few nzb websites and newzbin-like communities using usenet servers as private storage for their members to download the posts - the situation with the content is pretty chaotic, since posts are disguised in such a way, that users must use the satellite ecosystem (whish is not a part of Usenet) exclusively to download them, when the website disappears - the encrypted scattered posts just eat usenet providers' disk space uselessly. If you can't find something specific please let me know what exactly you can't find for me to check how it is possible to retain the posts. Legible posts shouldn't be affected at all, let me know if you notice anything missing.
08 Aug 24: After being unchanged for many years the search service communication protocol had to be updated a few times in part to resolve a server side set feature limitation and properly handle trial searches on the relocated server. The searches themselves are not affected and it looks like the work is now complete.
15 Mar 25: It looks like the search service is currently down as there are no pings. The other server is no more on starlink, but the search requests are still routed and the access to it is through the first server, since it is safer, but the direct access is no problem if this will be a repeated issue. The connection will be restored or server restarted as soon as possible.
16 Mar 25: One server is currently still down, the other server was reconfigured and already connected directly, so the search service is running with minimum possible retention gaps.
I've updated newsgroup list. It appears the newsgroup list remains almost unchanged, so I will just update the list at periods less than header feed server retention, so all headers in new newsgroups will be included, unless someone will point to a missing new newsgroup, then I can do an immediate bulk update, it is fast anyway.
as to this particular newsgroup - i see it is on highwinds but not on astraweb, it has 14 movie posts all at all in the last 4 days and one text post 63 days ago (maybe it was created back then).
astraweb you can ask them to add it.
i'll try to make the bulk update within few days, it is safer than to add one by one.
the update will be a bit later, there were some deep changes in the client code towards the next release which kept me busy, i want to recompile the server, check it is still ok, then to update the list, i'm not sure about this particular group, i just download the whole newsgroup list and refresh the newsgroup list on all server instances. the work on the client is almost finished, so it won't take long, at worst within one week.
ok, i've updated the server executable, looks ok, i'll update newsgroup list a bit later, it may involve some downtime to preserve complete headers in added groups.
ok i've added it now, but take into account from now on i'll update the newsgroup list on monthly basis just before database backup, it is somewhat safer to ensure databases are in sync and right groups go into right places. if it is urgent, though, i can add one by one as well.
