has anyone successfully gotten cZ to use sasl? I've followed the instructions on libera.chat/guides/chatzilla

do I need to do a /sslserv or something?

nvm.. will test it out

hrm anyone got SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data @ <chrome://chatzilla/content/static.js-> file://<profilepath>/scripts/cz_sasl/init.js> 108 ?

ergk

ok.. finally.. found the reason for my issues.. apparently the format of the preferences have changed. it's now JSON.. where as previously, it was a string.

Is there a way in ChatZilla to turn off message throttling? I can't seem to find it in the FAQ.

cyndaquil: You sure it isn't the server doing that?

yeah, it isn't.

I'm testing in a private server of my friend

Yeah, that invite isn't throttled

lol

tonymec|away: instead of sending messages to me would be better to send them to IanN he is doing the patches i am only dong the builds. SO if you send messages to me I just have to forward to IanN.

that is realted to SASL

other palces where others do patches but IanN is doing the SASL changes

WG9s: ah, OK. That detail had escaped my knowledge. I shall do so in the future.

sometimes I do the patdches sometimes frg deos the patches but IanN is the point guy for cZ SASL

i already told him you wanted disabling SASL form the menu should result in te plug-in still working. I suspect this is an issue mostly becuase the built-in SASL works neither with latest releast nor with the 2.57 pre versions

otherwise i thinkk you would not care is a way to use sasl that works with everything you are trying to run?

not wnating to speak for you and looking at this from my perspective if the built-in works with latest releast, latest next 2.53 version adn 2.57 then no one cares of the cz_sasl plugin still works

which is more convoluted now that we moved to libera.caht and the cz_sasl thing they point to does not understand the configuration they suggest.

Best remove the plugin and use latest 2.53.9b1 pre. If I understand InaN_Away it should work then with the built-in sasl

yes but I think tonymec is looking for a way to sue SASL that works with release, my 2.53b1pre version and my 2.57a1pre versions

so still stuck on no SASL

that is cerainly what I am looking for

Only with different profiles. 2.53.8 needs the plugin. 2.57 too until all is reviewed and checked in. In general should not mix profiles anyway.

otherwise no SASL for me! Yest aht was a soup nazi reference!

otherwise no SASL for me! Yes that was a soup nazi reference!

well oddly mixing profiles is only an issue if you use about:config to change things better to change user.js anyting you cange in about:config where the 2 versions you go backand forth betweeh have different defaults is where the issue begins.

if youdo it with about:config and then go to a version where what you tried to override is the default that change will be thown away

when the borwser exits and prefs.js is rewritten anything that is reset to the default value is thrown away.

if you really want to overrride you need to do it in user.js

if you run multiple version with same profile

Of course if some database has a new structure the still don't use same profile apples.if you go from old db to new there is a translation that happens, going from new to old, not so much.

I see no reason why you should not expect to be able to got from 2.53.8 to 2.53.9 using the same profile.

and it seems this will fail for people currently using cz_sasl

so this is an issue not yet there but will be when pople try to update form 2.53.8 to 2.53.9

are you aware that there is the cz fork Ambassador (wich is abandoned afaik) ? github.com/Ascrod/ambassador

so once 2.53.9 is released and we have updates actually working anyone using the cz-sasl plugin once auto updated will not be able to use chatzilla

WG9s: IanN_Away: one problem I have with built-in SASL is that it stores passwords separately for separate servers of a single network, or even for ports 6697 and 7000 of a single server. As a result, when I get disconnected and cZ reconnect, I may get a password prompt — behind the browser window. Then Ctrl-6 or Window→IRC Chat stops working and I have to use the keyboard's Windows button...

...to put all windows side-by-side and mouse-select the popup to write the password in it. Then I get disconnected again because of timeout but at least the cZ window is up.

tonymec|away: now that you mention that, I don't use SASL, but certainly I face a similar situation here

for example I connect to the same servers always, but depending on the command used to connect (and as of 2.53.8, the new default SSL port), I have always to create the same auto-perform command lists (in other words: msg NickServ IDENTIFY <blah>) for each port instance

furthermore, now that Libera is a first-class network for cZ, it won't pick my already stored auto-perform lists since these were for a explicit declaration of port 6697

...while as on 2.53.8, it defaults to not displaying port at all (despite still being 6697)

Would probably be best to comment in Bug 1717545 Bug 1713470

I now have 7 separate network settings for 3 networks

tomman: I never had problems with ns identify, but I write it in the "lists" preferences for the network. Defining the servers of the network is by means of the chatzilla/networks.json in my profile.

password storing is per origin in gecko so if something like the scheme or port changes it will not pick up the stored password. Was per host in 2.38 pre times but has been changed then.

for example that just bite me again on Rizon, hadn't noticed that I have been not logged in for 3 days, until I got reconnected due to some DSL downtime

and that's because the new default SSL port is 6697, not 9999... but my lists were saved for 6667 and 9999. D'OH!

(I had never connected to Rizon over 6697 until I upgraded to 2.53.8b1)

Well 9999 was plain wrong. That is why I also recommended to upgrade to 2.53.8b1 is you use libera. With the new network editor in 2.53.9 you can clean out the cruft easy.

In fact, Rizon is the only network I use that still listens on 9999, for whatever reason

all others (correctly) reject any attempt there

what is the history behind 9999? was it the ssl port at some point in time?

njsg probably german for no no no no

nein nein nein nein

also have no diea where port 7000 for this came from