Steam protocol

[watcher]

Black Sniper, your last post doesn't make any sense. Who enjoys what?

[Black Sniper]

watcher, sorry.
The protocol is unusable, constantly pops CAPTCHA. Disable protocol?

[watcher]

Black Sniper, yes, for a while, until unsane fixes it.

[unsane]

Black Sniper, yes, for a while, until unsane fixes it.

until valve fix it 

[Naith]

got the same problem,

what's the problem on valves side? :/

[Robyer]

Naith, nothing. It's something on Miranda's side, using login request wrongly or giving wrong parameters...

[Vulpix]

Darn, after the Tuesday maintenance, my steam stopped working too. It's in a loop of constantly asking for the captcha like a few people mentioned

[Robyer]

Darn, after the Tuesday maintenance, my steam stopped working too.

Sorry, I realized that my fix for automatically deleting SecretToken when it expires is wrong and deletes it even if you try to login while you don't have internet connection or when timeout occurs for login request (e.g. steam servers are down).

Now I don't know how to determine properly that token is expired or not... Anyway, if you have profile backup, you can put there old SecretToken and it will work again without login. (Only login procedure for getting token is broken).

[Vulpix]

Sorry, I realized that my fix for automatically deleting SecretToken when it expires is wrong and deletes it even if you try to login while you don't have internet connection or when timeout occurs for login request (e.g. steam servers are down).

Now I don't know how to determine properly that token is expired or not... Anyway, if you have profile backup, you can put there old SecretToken and it will work again without login. (Only login procedure for getting token is broken).

Thanks! Loaded my old DB backup and copied the "TokenSecret" variable, created a new unicode variable TokenSecret in my current DB and pasted the value there. Works again!

Can you make it so that the token is not deleted on regular DCs due to maintenance and such? :p Thanks!

[Robyer]

Can you make it so that the token is not deleted on regular DCs due to maintenance and such? :p Thanks!

Yep, done. Now it's not being deleted at all again (not even when it's really expired)

But now I at least know how to diferentiate it from clasic timeout, so... soon. But the login error is weird, I hope unsane will find the problem...

[Vulpix]

I see the new steam from Unsane's branch got merged. Looks solid, works here, no issues. Thanks!

Since we're now running on the new and improved (hehe), would it be possible to take a second look at offline messages?

To recap, I do not receive offline messages when I log in with miranda steam. When I use the regular steam web chat, I receive them, so it should be possible.

[Robyer]

I think we should primarily fix the login procedure, as no one is able to use the plugin (unless has saved old cookie) at the moment. We're probably sending wrongly encrypted password...

[Vulpix]

Fair enough. But when that is done, please don't forget to take a peek at offline messages too

[Robyer]

Funny... I woke up and started trying to fix the Steam.

I did some changes, compiled it, test it - and whoa! It worked!
Ok, let's check what part of my change really fixed it.
So I remove some part of it, compiled it, test it - ok, still works, so it was the second thing I changed.
Just to be sure, let's revert it all back to the original and test it. Hm... it still works.
Probably I copied the wrong file or compiled file stayed the same.
I clean and recompile it all, copy again. And -- it still works. Wut? Even with original file from Plugin Updater it works.
Hm, so perhaps Steam servers got update and fixed their own issue. Ok, good.

... then I looked into the SVN log and saw unsane's commit from the night with message "Steam: reworked login". 

Anyway, thanks unsane for fixing it 

[Vulpix]

  well then. Time to look into offline message retrieval? *hint hint* but yeah, I bet you were pretty surprised huh?