03 Oct 23: One server was relocated, the server currently doesn't have a public IP address since in the meantime it is running on starlink. 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 posts flood mass posted by a few nzb indexing websites using usenet servers as private storage for their members to download the posts - the situation with the content is pretty chaotic since their purpose is to post in such a way, so users must use their website exclusively, when the website disappears - the encrypted posts just eat usenet providers' hard disk space uselessly. If you can't find something specific please let me know at alexbirj at gmail dot com what exactly you can't find for me to check how it is possible to retain the posts. Non-obfuscated posts shouldn't be affected at all, let me know if you notice anything missing.
29 Nov 23: The search protocol had to be upgraded to extend 3 byte (16M+) limit on the server side for number of sets per instance, so at least the version 5.8.3 is needed to access it, otherwise should be no any difference.
I have used the search service until my computer halted. After reset, the search service is failing almost every second search, sometimes with timeout messages, and sometimes it's just stays on "searching" status forever. Reseting the search database does not help.
It would be very helpfull if i could have somekind of a log to know why it is failing instead of guessing and getting mad....
it must be firewall. you can try to reinstall it, check whether the search works ok after you uninstalled it (if it uninstalls correctly). try to disable it first, maybe it will help to spot the problem.
when it is failing it would give some error box with the system error message like timeout.
maybe it is some temporary connectivity issue which coincided with the halt? from the computer you connected from it works ok? (you can try to search from trial version as well). the computer you connected from and computer you connected to sit on the same connection? if so maybe to try to reset router, if not maybe it is connectivity problem on that connection.