Froxz
-
Posts
3 -
Joined
-
Last visited
Posts posted by Froxz
-
-
Yes, because ignorant coders will almost definitely start passing API keys that don't belong to the account they're signed into, and start posting GitHub issues asking what's going on.
If you know what you're doing, you can set the
apiKey
property directly with the correct key, but please make sure you actually know what you're doing.Hi, thanks for reply, yes I ended up doing it directly:
user.on('webSession', function(sessionID, cookies) { console.log(data.login+': Got webSession'); manager.apiKey = data.api_key; manager.setCookies(cookies, function(err) {}); community.setCookies(cookies); });
Yes, I manually generate the API KEY (Because I use same KEY for LOGIN) just less request and hassle because I know the API KEY.
Thank you.
-
Hi,
it is possible to set API?
Trade-offers:
this.apiKey = null; this._community.getWebApiKey(this._domain, (err, key) => { if (err) { callback(err); return; } this.apiKey = key; callback(); });
I can make a pull request to change
this.apiKey = (options.apiKey || null);
Or there is a reason for not giving option to pass api key?
v4 question
in node-steam-user
Posted
Hi,
Currently I'm using v3 version:
And in v4 I should change to:
Can you advice please?
NOTE: so v4 node-user replaces steam-client?