Replies: 5 comments 5 replies
-
I have wondered about this, I don't recall ever needing the option. If some servers do need it could it not be made transparent to the user? For example I don't recall the exact errors but if SAB does a body/stat etc. and gets a So upon every connection to the server at most one request might need to be retried. |
Beta Was this translation helpful? Give feedback.
-
iirc this is more of an artifact of the past for some really legacy usenet service providers (this was 15+ years ago) so i'd be shocked if its honestly still needed.. but i second mnight's logic that we should just be able to detect and do it if needed.. but doing it per article would prob not be the most optimal so we would just set it for the session/instance if needed or something so its just a one time hit on first article or something. but a bit moot if its not even needed |
Beta Was this translation helpful? Give feedback.
-
I have it switched on for a server, don't know why actually, the setting was copied from older programs and settings. |
Beta Was this translation helpful? Give feedback.
-
Only server I've seen in the last years that required it is a free one that allowed 1 connection and extremely slow speed. I can't remember the name and I don't think it exists anymore. |
Beta Was this translation helpful? Give feedback.
-
This option has been active for 15 years or more, when I first registered. It's no longer of any use to me. I'd even forgotten about it. |
Beta Was this translation helpful? Give feedback.
-
I was hoping to remove this option under Config > Servers.
If you, the user, have configured this:
Can you check if your server also works fine if you have
Send Group
disabled in the Server's configuration?If not: can you let us know which servers still require this?
EDIT: Since nobody seems to be using it, we will remove it.
Beta Was this translation helpful? Give feedback.
All reactions