TASclient update installs Spring lobby

[TheFatController]

Yeah that's my big problem, imo Satirik has proved he is not responsible with the autoupdate which is very serious.

TASClient is now in theory a large risk and i'd go as far as saying Spring should have its installer emergency patched to remove TASClient incase he does something worse.

[jennington]

Springlobby doesn't work for me. Battle window won't show up even though I'm in battle, and yes, I know how it should work, but there is no effing tab. It's bugged somehow. I tried reinstalling Spring and now have the version of Springlobby that came with it (since the version TASClient updated to was apparently incomplete), but that didn't change a thing. I should be able to provide a screenie if anyone wants it, it was already posted and discussed on #springlobby though - no solution found.

TASClient doesn't work either after the update, I'm having the same problems as reivanen. The next thing I'm going to try is reinstalling Spring again without any lobby, and then downloading the old version of TASClient that TheFatController provided. We'll see...

Oh, and btw, I'm using Vista.

[CarRepairer]

reivanen and jennington and anyone else having these problems, I had the same problem. With a little help from Satirik and a little bit of rooting around, I found that it helps if you do the following:

1) Uninstall spring.

2) Go to your registry (regedit) and under HKey local user -> software, delete spring ("SJ" I think) and tasclient stuff.

3) Go to your local user folder (one up from your "documents" folder) and delete the spring folder, if it exists.

4) Reinstall.

And please go easy on Satirik, he just ate a bad crepe.

[Argh]

The Lobby clients are such a vital part of Spring that we can't let this happen again, or we're going to have a complete breakdown as a project. I can't even begin to describe how awful that would be.

I think we need to go ahead and do two things, right now, whether or not the Powers that Be want to make up with Satirik:

1. Put SpringLobby source in Git. No more trusting people outside the main codebase with something that important, where we don't have version control. It's the only one that we know can be compiled, so we're stuck- thankfully it's improved so much since last summer, it may be a great thing in the long run. No offense meant to the current maintainers, but we really should take some concrete steps to ensure the project's survival.

2. We need to take similar steps about the Server. Preferably get Aegis to finally release UberServer, so that a backup could be up and running in a reasonable timeframe, if something happens.



We can't have this happen again, though, it's a potential project-killer.

Guys, I don't give a shit what the backstory is, this time... bad crepes, too many people bitching about the new News stuff, which was clearly WIP and I'm sure had issues, but was a very significant step forward. Enough. Satirik can come apologize and agree to sin no more, but we should not put ourselves at anybody's mercy again, I've seen too many excellent projects die because of that, and this makes my stomach do bad things just thinking about it.

This kind of nonsense is a lot more of a threat to us than the disappearance of UnknownFiles, which was mainly an annoyance. Time to take some concrete steps, and end the real threat, which is that we're left without a working Lobby, and no source we can compile... because somebody flaked out, had RL issues, computer melted down, whatever. We can't go on like this, guys, we're courting disaster.

If there's anything I can do to help get this stuff back under control again, I'll do it.

[lurker]

Springlobby and uberserver are in repos that many people have copies of, by virtue of being git.

[Argh]

Ok. That makes me feel considerably better, tbh, that we're not faced with complete disaster if koshi gets hit by a bus tomorrow or whatever.

[Tobi]

1. Put SpringLobby source in Git. No more trusting people outside the main codebase with something that important, where we don't have version control. It's the only one that we know can be compiled, so we're stuck- thankfully it's improved so much since last summer, it may be a great thing in the long run. No offense meant to the current maintainers, but we really should take some concrete steps to ensure the project's survival.

http://springlobby.info/trac/wiki/Git

2. We need to take similar steps about the Server. Preferably get Aegis to finally release UberServer, so that a backup could be up and running in a reasonable timeframe, if something happens.

TASServer is still reasonably runnable, AFAIK. At least in LAN mode I can put it up on an otherwise empty server in a few minutes. (There are various other people who can.)

Finding a decent server on a reasonably stable connection will be the hardest part wrt TASServer.

I agree with the rest of your post..

[lurker]

I took it to mean 'the main spring git repo'.

[KDR_11k]

Yeah that's my big problem, imo Satirik has proved he is not responsible with the autoupdate which is very serious.

TASClient is now in theory a large risk and i'd go as far as saying Spring should have its installer emergency patched to remove TASClient incase he does something worse.

To me he already proved that with the youradick.exe incident. I stopped using failclient because of that.

[lurker]

Onward to faillobby!

[zwzsg]

I'm so glad I click "No" most of the time a program want to self update.

Beside "updating" to SpringLobby and youradick.exe for aegis and Wisse (can it affect anybody else?), are there any other hidden hooks in it?

What is the latest safe version of TASClient?

[lurker]

IT NEVER AFFECTED AEGIS AEGIS ONLY SHARED THE BUG THAT WISSE WAS COMPLAINING ABOUT

Thank you for your time.

[dizekat]

LOL@argh

Yeah that's my big problem, imo Satirik has proved he is not responsible with the autoupdate which is very serious.

TASClient is now in theory a large risk and i'd go as far as saying Spring should have its installer emergency patched to remove TASClient incase he does something worse.

To me he already proved that with the youradick.exe incident. I stopped using failclient because of that.

Agreed.
Auto-updates are really a big deal.
Satirik controlling updates = Satirik having MUCH more power than any server admin out there.
That is just stupid, not to trust someone to do stupid relatively harmless shit like kicking and banning off server, but trust him to root all the windoze user's machines (which is far more power).

[Regret]

The Lobby clients are such a vital part of Spring that we can't let this happen again, or we're going to have a complete breakdown as a project. I can't even begin to describe how awful that would be.

I think we need to go ahead and do two things, right now, whether or not the Powers that Be want to make up with Satirik:

1. Put SpringLobby source in Git. No more trusting people outside the main codebase with something that important, where we don't have version control. It's the only one that we know can be compiled, so we're stuck- thankfully it's improved so much since last summer, it may be a great thing in the long run. No offense meant to the current maintainers, but we really should take some concrete steps to ensure the project's survival.

2. We need to take similar steps about the Server. Preferably get Aegis to finally release UberServer, so that a backup could be up and running in a reasonable timeframe, if something happens.



We can't have this happen again, though, it's a potential project-killer.

Guys, I don't give a shit what the backstory is, this time... bad crepes, too many people bitching about the new News stuff, which was clearly WIP and I'm sure had issues, but was a very significant step forward. Enough. Satirik can come apologize and agree to sin no more, but we should not put ourselves at anybody's mercy again, I've seen too many excellent projects die because of that, and this makes my stomach do bad things just thinking about it.

This kind of nonsense is a lot more of a threat to us than the disappearance of UnknownFiles, which was mainly an annoyance. Time to take some concrete steps, and end the real threat, which is that we're left without a working Lobby, and no source we can compile... because somebody flaked out, had RL issues, computer melted down, whatever. We can't go on like this, guys, we're courting disaster.

If there's anything I can do to help get this stuff back under control again, I'll do it.

[reivanen]

Yeah, got it working by removing the spring folder from user profile. But still, what an awful thing to do of him, and what an awful thing by someone to trust such a person with such responsibility.

[zwzsg]

IT NEVER AFFECTED AEGIS AEGIS ONLY SHARED THE BUG THAT WISSE WAS COMPLAINING ABOUT

Sorry, what did you just say? No really, actually I do not know what you mean by "shared the bug".

Beside, calling that a bug is purposely deceiving as from what I understood it was the intended behavior.

[lurker]

1. there was a bug, many people had it, including aegis and wisse
2. wisse complained too much about the bug for satirik's taste
3. wisse got the fake error message broken client thing

so in short there WAS a BUG and aegis had the BUG AND ONLY THE BUG

Go back and read the original posts again (my posts) instead of saying what they meant.

I'm just upset that I thought I clarified it fine, and now someone is still confused so much later.

To make absolutely sure: to everyone else: ignore what zwzsg has said; don't be a victim of the rumor pile like him

[Wisse]

What lurker said.

It would be rly sad if Satirik droped TASClient tho. I rly like this lobby and wouldn't want to change. But we should be able to use it for quite some time, even in worst case scenario, where there are no more updates.

[Masure]

1. there was a bug, many people had it, including aegis and wisse
2. wisse complained too much about the bug for satirik's taste
3. wisse got the fake error message broken client thing

so in short there WAS a BUG and aegis had the BUG AND ONLY THE BUG

Go back and read the original posts again (my posts) instead of saying what they meant.

I'm just upset that I thought I clarified it fine, and now someone is still confused so much later.

To make absolutely sure: to everyone else: ignore what zwzsg has said; don't be a victim of the rumor pile like him

Agree.

They're too much unacceptable shit already, please don't add some lies on top of this.

When I read some posts about TASClient ability to hack your comp, it's just silly. Satirik NEVER wanted to damage anyone's comp and NEVER will.


That said, today's real shit :

* Players insulting devs when something doesn't fit exactly what they want when they do NOTHING but complaining.

* Satirik using his TASClient maintainer privilege to force people to switch to SpringLobby (with or without dick error)


With a bit of understanding from each other, that shouldn't be such a mess.

[Hoi]

Satrik is an idiot, he's an immature child and needs to be banned, there's less people in the lobby than there were before, also, even if someone wants to take over tasclient development, afaik satrik didn't release the source, so he/she will have to start with betalord's last version (if that's even still around).