Sam

@Pham test

@Pham hello

... if I can remember the creds to my bot account

Just making sure my chat lib works smoothly with chat.se

Hiya :D

Sure thing. Just wanted to keep you guys in the picture.

@Hakase Hiya. Are you still using the chatexchange.net lib? If so, just a quick heads up, the lib is going offline and is being replaced with a new lib soon-ish™ (within a couple of weeks hopefully). You might have already heard, but SE are deprecating their openid login in a few months; annoyingly, the old lib relied on that to auth, so the lib will be completely dead by that point.

@Hakase Yeah, it's still there. Just moved to a different class.

@Gao Np! Sorry that things got screwed up in the first place.

Cya o/

Fair enough lol

@Hakase That, or you were right about simply removing the reference instead.

Anyway, it's all under review. I hope to make it less ugly with the next major release.

Because you won't have access to user collection properties in the meantime.

It runs the initialisation code on a separate thread.

You should use .JoinRoom(<url>, true);

Oh

So it's merely precautionary.

I have known several people to get ip banned before.

Granted it's ugly.

It was probably there to avoid flooding the server with a bunch of requests when you join a room with lots of users.

Do you have that installed as a package perhaps?

lol

Oh nice. What was the problem?

Well if that's the case, it's just a matter of deleting the native implementation class (and reference).

No, I thought the exception was only thrown if you attempt to create an instance of the websocket class.

@Hakase Done.

I have no idea. I don't remember much of the old libs.

You can still set a timeout though.

Yeah, the library handles auto-reconnecting now.

lol

@SimonForsberg No idea. I'm semi-actively (spare time at weekends) developing my new chat library that should work across all of SE.

@quartata Yeah, that does indeed work.

hmm

Yes

Or rather, you had to do that. I'm not sure if they've changed that.

AKAIK, you have to login to SE if you want to access SE chat rooms.

@quartata Haven't tested that case yet.

SO does not.

SE still uses openid when authenticating with an email/pwd.

@SimonForsberg Yeah. However, as I've just found out, it appears to only work for SO.

@quartata I'll keep that in mind, thanks.

Too many loc to post here.

@SimonForsberg Uh, the link I posted earlier was my solution. :)

(Our bots need to be able to interact with chat, so the SE API isn't an option here.)

It's the simplest solution I've come across so far.

:p

:)

@SimonForsberg Yeah. The library is still far from complete though.

Yeah, I've just switched to directly logging in with the account's email/pwd for each community.