RTB not working?

[Danny Boy]

I hope it doesn't do that thing again where it stayed down for a good while.

[Ad Bot]

[jleneau]

I hope it doesn't do that thing again where it stayed down for a good while.

I think people are still having issues.

[Ephialtes]

I'm not near a computer at the moment but it seems to be the issue from before making a reappearance. I'll check it out and confirm that whenever I go home.

[jleneau]

I'm not near a computer at the moment but it seems to be the issue from before making a reappearance. I'll check it out and confirm that whenever I go home.

K

[rlcbm]

ephi fix this plz its the most usfull add on and the website works

[Twenky]

It's back up

[rlcbm]

yay

[jleneau]

yay

It is up?

[rlcbm]

its down agen

[Ephialtes]

Well, I've confirmed it's the same issue as before - the Blockland master server is blocking authentication requests from RTB. I've restarted the server with all non-essential requests to Blockland servers disabled so you won't be able to see what servers people are on or use the join server functionality.

Sorry, this is totally out of my control and will probably stay like this for the foreseeable future. If even this minimal amount of requests to the BL server causes problems again I'll have to just shut down the service as before until the issue is resolved.

[Kalphiter]

Couldn't you just cache successful authentication for an hour or something?

This issue happened before and I also suggested doing that. It would cause less requests to be sent which may or may not fix the problem, but it would at least keep the service usable by many people.

Seriously, hold a cache for an hour, problem solved.

[Ephialtes]

Well for one that's totally useless with regard to user behavior because people aren't signing in and out constantly. The typical user journey (and this applies to 99% of users) consists of connecting, authenticating, playing for a while then quitting. The cache hit ratio would be like 1%. This isn't an issue stemming from a handful of users disconnecting and reconnecting repeatedly.

Secondly, authentication is one of those things you shouldn't cache, and certainly not for an hour. I'd rather the service wasn't running than have it using stale authentication results which could be used in a variety of ways to cause trouble.

[Kalphiter]

Well for one that's totally useless with regard to user behavior because people aren't signing in and out constantly. The typical user journey (and this applies to 99% of users) consists of connecting, authenticating, playing for a while then quitting. The cache hit ratio would be like 1%. This isn't an issue stemming from a handful of users disconnecting and reconnecting repeatedly.

Secondly, authentication is one of those things you shouldn't cache, and certainly not for an hour. I'd rather the service wasn't running than have it using stale authentication results which could be used in a variety of ways to cause trouble.

There's a pretty low chance that a key is no longer valid by the time it's re-authenticated. That's a rare event and having a person with an invalid key for a little while is probably not a big deal. 24 hours is a better caching period.

What trouble could be caused? I was thinking that authentication is cached only for chat.

[Zeblote]

The auth works with name and ip
My ip tends to change
No thanks

[Kalphiter]

The auth works with name and ip
My ip tends to change
No thanks

Thanks for disregarding a potential solution because it only benefits you 99% of the time that it does for everyone else.