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've been trying to use the search service for several hours now and I get the message box "Search Failed A connection attempt failed because the connected party did not properly respond after a period of time, or"
i had a tech out to the house to install new internet service. It's still running off of the old one which is working fine, but one of the servers is now offline. He may have bumped it or done something else stupid. I should be home in 2 or so hours and check out what's up with the server.
Stupid tech decided to use one of the servers for the new internet (even with HUGE signs saying DON'T TOUCH on it) so essentially it was disconnected. All fixed.
search service monitor is not currently running (since yesterday), so i couldn't detect it in time, in one week the monitoring will be resumed, until then i'll be checking it twice daily, probability of those events is small.