Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Unfortunately the only data sources for tags and features are the store pages, so my script needs to download them. The more games you have in your library, the more time it needs. I tried some optimizations, but no one speeds things up enough. However, I do not exclude to be able to try different approaches in the future.
Just wondering, is this python or something? Maybe (if you have the space) cacheing the tags on the server would be useful. Then once a game is hit once, it can be refreshed every week instead of pulled down every time its requested.
I agree it taking a long time to work sucks, but its 100% better than nothing; which is what we had yesterday.
Yeah, that's because "OmegaNine" is the ID of your VAC banned account. If you check your new account URL it's "Omega_Nine", and that's what you have to type in the field. For anyone having this kind of problem, just paste the entire profile URL in the field and it should works: in Steam, you can get your profile URL by right-clicking in an empty spot on your profile page, there's something like "Copy page URL" in the popup menu.
Saving one's results to my website DB should not be a big deal. The problem is that if I save all data and then give a unique URL to check it later (that's the idea), results will not be updated if someone adds games to his library.
A more "transparent" idea is the OmegaNine's: caching games data in my DB. As soon as someone get data for a game, next time him or someone else needs it, it will be extremely faster because I have not to fetch Steam store page again. The problem here is DB space and cache updating (refreshing it once a week looks a good idea to me). I have no clue how hard it will be to handle that cache if it grows too much, but that's a problem I can deal with once it happens... I think I'm going to try this solution first.
It is not Python or any other server-side language, it's 99% Javascript. It runs practically all on the client (your browser). The server part is very minimal at the moment, and it's needed only to prevent some SOP (same-origin policy) issues in passing Steam store pages to the Javascript program.
I am amazed at the things being done in javascript now a days. I had no idea it was robust. I think it might be time to pick up a book on it.
You did great work here, thank you, I have already used it to find something to screw around with while I should be doing homework :P
Thanks
There are over 3000 games on Steam, so i think you can see i do not have many of them
Also you may note i do not have almost any new games, only old once, and also no CoD games
So, what's now? Simply put, it's something like 100x faster than before.
That is, a few seconds if you have hundreds of games.
Enjoy: http://www.lorenzostanco.com/lab/steam/