Open JoseALermaIII opened 5 years ago
Can reproduce on Oreo (I bet 7.1 is still well in the "lots of people using it" category)
I think it's not about user registration probably but the minutiae of various ircds handling pre-login phase differently
I think it's not about user registration probably but the minutiae of various ircds handling pre-login phase differently
Don't know what ircd Freenode uses off the top of my head, but mine is a bare-bones ircd-hybrid
configuration. It was surprising I couldn't make a non-SSL connection either.
Can anyone make a connection on a newer/older version of Android? My tablet's all I have to test with on hand.
I can connect with a Huawei P20 Lite, Android 9.
Current setup of Revolution IRC
:
i just remembered that this happens if there's already a person using your nick on the network, I completely forgot about that bug. Maybe it's the issue here?
i just remembered that this happens if there's already a person using your nick on the network, I completely forgot about that bug. Maybe it's the issue here?
That makes more sense. It also happens to me. Probably the app should auto set the nick to something like nick#
, where # is a random number in case that the current nick is already in use, so we could proceed with the connection?
Just set more aliases.
i just remembered that this happens if there's already a person using your nick on the network, I completely forgot about that bug. Maybe it's the issue here?
That's what I thought, too. So I used my IRC server which has no registered nicks (because nicks cannot be registered) and it did the same thing with both an SSL and non-SSL connection.
In this instance, I was trying to connect to my IRC server as jose_
with Revolution IRC, but it still gave me a "Registration timed out":
However, I was able to connect with another IRC client:
If there's a way to provide logs, I'd be glad to fetch them.
Scratch that, problem was between chair and tablet:
So it looks like using a registered nick without validating really is the issue.
i just remembered that this happens if there's already a person using your nick on the network, I completely forgot about that bug. Maybe it's the issue here?
That makes more sense. It also happens to me. Probably the app should auto set the nick to something like
nick#
, where # is a random number in case that the current nick is already in use, so we could proceed with the connection?
Some IRC servers change it for you if you don't validate within a certain amount of time. I think it depends on your settings when you register with NickServ
Never heard of such IRC servers, but I guess, in the world of IRC, anything can happen.
Oh, nvm, if you don't validate; yes, if you don't validate then they change it for you, but not during the registration phrase.
I'm trying to connect to ircs://irc.freenode.net:6697 with the following settings:
It connects, but eventually disconnects me for "Registration timed out":
I've tried on my own IRC server (both SSL and non-SSL), but it does the same thing even though user registration is not required.
Using Revolution IRC version 0.5.2 from F-Droid on a Nexus 7 2013 LTE with LineageOS 14.1 (Android 7.1.2). It may just be a compatibility issue with an older version of Android.