When using SSL you mean?Gfy wrote: Make the port change automatically to 563 if the value is still 119.
There's no consistency in ports for SSL.
When using SSL you mean?Gfy wrote: Make the port change automatically to 563 if the value is still 119.
A quick google reveals me that NewsLeecher has this feature for four years: http://www.newsleecher.com/forum/viewto ... 5a6be009f4Port 563 is traditionally recognized as the default port for encrypted Usenet traffic (NNTPS), while port 443 is recognized as the default port for encrypted web traffic (HTTPS). By supporting multiple ports for encrypted Usenet downloads, Giganews' customers will be able to switch between ports depending on which path offers the best performance.
I know NewsLeecher and AltBinz have it. If the providers choose a non standard port, the user would have to edit it anyway, so a default value would be much user friendlier. It's a crappy excuse not to do it anywayshypike wrote: You are aware that there are dozens of Usenet providers?
My SSL is on 443 .. so this would not work for meGfy wrote: Make the port change automatically to 563 if the value is still 119.
What is your provider? Are you sure they don't provide it at port 563 too?rascalli wrote: My SSL is on 443 .. so this would not work for me
If you leave it empty now, it will use the default port. If you make it required, you make it less user friendly. Put in default values and it'll be less possible to forget for 95% of the users.rascalli wrote:Maybe it is even better to set the port as : REQUIRED
That way lazy people / Newbies do not forget it
That's my whole point. Do this to make it even more so. Ask a usability expert. He will probably be able to help you even more than I can.rascalli wrote:Remember that the devs are trying to make it as userfriendly as possible.
True, but if you can avoid it, why wouldn't you?rascalli wrote:But you can not rule out all mistakes that people make .. sometimes they need to think 7 read a bit more