I'd like to preface this by saying I love the program, and know that giganews is not always popular, but it meets my needs.
From time to time I do a refresh of the newsgroups list, and have never had a problem until recently, I couldn't tell you the exact build this cropped up in, but I am using the most recent 64 bit version of the program.
The problem is that the new group names show up as garbage names, I sent a note to giganews support, and they are looking into it, but I think I'm the first person to bring it up to them, so I'm not sure if it is UE having a problem pulling down the data, or if it is something broken on their end.
I use data compression and an ssl connection, turning off data compression didn't seem to make a difference. I use your data compression implementation, and not giganews accelerator.
http://img253.imageshack.us/img253/6632/giga.jpg
I linked to the screen shot as it is 300+ kbytes and didn't want to slow loading for anyone.
Thank you for any insight into the problem.
Issue getting newsgroup list.
Logically downloading newsgroup list shouldn't be associated with the compressed headers, but the custom way giganews implemented compressed headers is to irreversibly change connection "mode", so in principle the mode may potentially affect any command and UE reuses connections when keep connection alive is enabled.
If you reset newsgroup list, then uncheck "enable compressed headers" in properties->general and restart UE (if you don't restart it it may still reuse those connections), does the problem still persist? If so it is completely broken, if newsgroup list appears normal it may be then intentionally or not their connection mode affects NNTP newsgroup list commands.
If you reset newsgroup list, then uncheck "enable compressed headers" in properties->general and restart UE (if you don't restart it it may still reuse those connections), does the problem still persist? If so it is completely broken, if newsgroup list appears normal it may be then intentionally or not their connection mode affects NNTP newsgroup list commands.
I did as you advised, reset the newsgroup list, disabled compression, then restarted, and the newsgroup list came up normal. So for now there is a work around, I just have to remember to disable compression and restart before getting new groups.
Would turning off keep connection alive fix this as well?
Thanks for the advice.
I got a reply from "Philip" at giganews, the important part of the message was this:
Would turning off keep connection alive fix this as well?
Thanks for the advice.
I got a reply from "Philip" at giganews, the important part of the message was this:
It's also possible that we have a code bug somewhere, but if we do, I
cannot find it. We have been pushing out some new code related to group
data compression to the servers, but it's been pretty heavily tested,
and like I said, I can't get any weird data to come through.
I'll try to get in some more testing today with clients I know have
working implementations of compressed data handling.
Ok, then reused connection is like spoiled when it was used once for header download.
Their implementation is not published so we don't know for sure which commands should be affected by enabling compression (e.g. when downloading article bodies there is still no compression).
If you are in contact with them ask them whether connection compressed state (xfeature) matters or not when downloading newsgroup list, in principle I can change it so not to reuse old connection potentially "spoiled" by prior compressed headers download (then it will work always) or to accept their compressed data when downloading newsgroup list if it is not a bug.
Their implementation is not published so we don't know for sure which commands should be affected by enabling compression (e.g. when downloading article bodies there is still no compression).
If you are in contact with them ask them whether connection compressed state (xfeature) matters or not when downloading newsgroup list, in principle I can change it so not to reuse old connection potentially "spoiled" by prior compressed headers download (then it will work always) or to accept their compressed data when downloading newsgroup list if it is not a bug.
I've sent them the question via the giganews.general support newsgroup on their servers. I quoted your message directly, so hopefully they'll know what you need to know.
Thanks for being prompt as always, especially on a holiday.
----
Replies separate from the 2 so far replies, as posted in the giganews.general support newsgroup. I'm not making a judgement, I'm just passing it on. If you want headers/senders, I'm happy to provide them if you don't have access to that group.
-----
I use x news, and have not seen that at all.
I use Agent 4.2 and have not seen that.
Thanks for being prompt as always, especially on a holiday.
----
Replies separate from the 2 so far replies, as posted in the giganews.general support newsgroup. I'm not making a judgement, I'm just passing it on. If you want headers/senders, I'm happy to provide them if you don't have access to that group.
-----
I use x news, and have not seen that at all.
I use Agent 4.2 and have not seen that.
agent and xnews don't support their compression.
you need reply from their technical support about details of their implementation or more exactly what commands are affected by the compression, or even more exactly I'm talking about "LIST" and "NEWSGROUPS".
my past experience with their support is they never replied on the essence, just sometimes as a result changes were performed on the server side silently, e.g. when standard header compression was enabled on giganews side, but still no official reply or recognition of any problem. it is one of the reasons i recommend e.g. astraweb and some other providers as a replacement, i feel like i'm dealing with a black box.
if you like try to check with giganews accelerator (in UE compressed headers must be disabled), if newsgroup list command works. also there are actually 2 commands to get newsgroup list "LIST" and "NEWSGROUPS", the latter when you get new newsgroups rather than all of them, you need manipulate your system date to check the "NEWSGROUPS" command for sure (when getting all need to set date e.g. 3 years backwards when after it is finished put date to normal and get new newsgroups only), or better pm me your giganews credentials and I'll check it out myself directly, it wouldn't take long (but better check first with accelerator if it works at all to be sure it is not a bug).
you need reply from their technical support about details of their implementation or more exactly what commands are affected by the compression, or even more exactly I'm talking about "LIST" and "NEWSGROUPS".
my past experience with their support is they never replied on the essence, just sometimes as a result changes were performed on the server side silently, e.g. when standard header compression was enabled on giganews side, but still no official reply or recognition of any problem. it is one of the reasons i recommend e.g. astraweb and some other providers as a replacement, i feel like i'm dealing with a black box.
if you like try to check with giganews accelerator (in UE compressed headers must be disabled), if newsgroup list command works. also there are actually 2 commands to get newsgroup list "LIST" and "NEWSGROUPS", the latter when you get new newsgroups rather than all of them, you need manipulate your system date to check the "NEWSGROUPS" command for sure (when getting all need to set date e.g. 3 years backwards when after it is finished put date to normal and get new newsgroups only), or better pm me your giganews credentials and I'll check it out myself directly, it wouldn't take long (but better check first with accelerator if it works at all to be sure it is not a bug).
Unlikely someone will be able to reply, it appears their marketing/support is completely separated from technical team, there is only one way communication from support to technical but not the opposite. Try to check with accelerator whether "rescan newsgroup list" (LIST) works, then i explain how to test "get newsgroup list" (NEWSGROUPS) in more detail.
Subject: ** GN Request
Hello Ryan ,
Thank you for contacting Giganews Technical Support!
I have escalated this issue to a manager, they will get back to you as soon
as they have had time to research this issue. Usually, you can expect a
response within 24 hours.
Thank you for your patience.
--
Mike
Giganews Support
--------------
I got this, so hopefully we'll get something.
Ryan
Hello Ryan ,
Thank you for contacting Giganews Technical Support!
I have escalated this issue to a manager, they will get back to you as soon
as they have had time to research this issue. Usually, you can expect a
response within 24 hours.
Thank you for your patience.
--
Mike
Giganews Support
--------------
I got this, so hopefully we'll get something.
Ryan
I got someone's account, checked in debug, it is a mess, LIST command is compressed, NEWSGROUPS is not compressed, their accelerator does recognize the LIST command so through accelerator it works. I'll change it in the next version, but also this Giganews black box approach is not so usenet client friendly in principle, given there is standard compression commands which work better - without changing connection mode (so the connection doesn't have "memory"), it would be polite for them at least to publish a short description for developers.