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.
Change the port number to 2021. Remember to change it back after a few hours if 2020 is working OK again, though. It should be on 2020 unless there are problems.
the problem has been resolved, my router account has been accidentally deleted, in the future i'll be able to reset the router myself promptly if it reoccurs.
also true registered users can choose between ports 2020 or 2021 if it happens again before the router is replaced.
I can't seem to "telnet" to either of the ports 2020 or 2021 on the indexing server, but the address resolves, so it's not a DNS issue. The search service worked as recently as last night, but something seems to be amiss again. I'm happy to be proven wrong, but don't think it's a client-side thing.
Thanks for any help.
try again. internet access was temporarily unavailable due to preparations for contractor work tomorrow. While every effort will be made to maintain access for the next two days, some periodic downtime may occur.