Dr. McKay

When using Steam in-home streaming, network communication is encrypted with the auth secret. It's called a pre-shared key because it's an encryption key that is shared with both parties (in this instance, the machine the games are getting streamed from and the machine they're getting played on) by Steam, before the in-home connection is established.

https://github.com/DoctorMcKay/node-steam-user#getproductinfoapps-packages-incltokens-callback

I assure you that it doesn't.

Make sure the privacy settings allow people to view games.

Looks like that account owns these apps, beyond the basic ones everyone owns: 730 - CS:GO745 - CS:GO SDK236390 - War Thunder (free on demand)238960 - Path of Exile (free on demand)304930 - Unturned (free on demand)311730 - Dead or Alive 5 Last Round (free on demand)355840 - Survarium (free on demand)438100 - VRChat (free on demand)624820 - CS:GO - General763700 - Smart Mummy817760 - The Castle Disaster

It's not, you're doing something wrong.

ByteBuffer is a layer over Node's regular Buffer which adds some nice things. Basically what's happening here is that you're allocating 16 bytes + however many bytes you need to represent your name string + 1 more byte, then you're filling in those bytes with the values shown (the name tag ID in 64 bits, the item ID in 64 bits, the name as a string, and a 0 byte at the end to represent the end of the string). I'm unsure why that dash is being added. We might have missed a field, maybe. Try adding buffer.writeUint8(0); before the writeCString.

If you want my guess, fork node-globaloffensive and add this to index.js: GlobalOffensive.prototype.nameItem = function(nameTagID, itemID, customName) { var buffer = new ByteBuffer(16 + Buffer.byteLength(customName) + 1); buffer.writeUint64(coerceToLong(nameTagID)); buffer.writeUint64(coerceToLong(itemID)); buffer.writeCString(customName); this._send(Language.NameItem, null, buffer); }; If that doesn't work try swapping nameTagID and itemID. And if that doesn't work, you'd want to use something like NetHook2.

You might be logging in, but you're still trying to load your inventory before you're logged in. Login IP ratelimits typically last less than an hour.

You're trying to get your inventory but you aren't signed in yet.

No, it's not possible to get a friend's games list except through the WebAPI.

https://github.com/DoctorMcKay/node-steam-user#getownedapps

No.

My best guess is that it indicates that you want to post to a profile, not to a forum thread.

No such cookie is issued when you log on via the client.

It's now possible to generate a link to allow someone to add you as a friend without you needing to accept a request. These links look like http://s.team/p/user-id/token which redirects to https://steamcommunity.com/user/user-id/token You can also access a profile using https://steamcommunity.com/user/user-id which will just redirect you to /id/ or /profiles/, depending on whether the profile has a custom URL set. These user IDs look like aaa-aaaa. I don't know why it might be useful to convert a SteamID to friend-link user-id, but converting the user-id to a SteamID might be useful. The friend-link user-ids are just the account's accountid (the lower 32 bits in the 64-bit SteamID, or the x part in [U:1:xxxx]), encoded in hexadecimal, with some character replacements, and with a dash added. Here are the replacements: Hex = Letter ------------ 0 = b 1 = c 2 = d 3 = f 4 = g 5 = h 6 = j 7 = k 8 = m 9 = n a = p b = q c = r d = t e = v f = w To convert a SteamID to a user-id, encode the accountid in hex and perform string replacements for the above characters. The hyphen isn't necessary for a final URL to work. To convert a user-id to a SteamID, remove the dash and perform string replacements for the above characters. That gives you an accountid which you can turn into a SteamID using a platform-appropriate SteamID library.

I don't work for Valve.

You need to filter the inventory to get just the items you want. Array.prototype.filter will probably interest you.

The rate-limit is obviously not on your public IP. The change request is going through the proxy.

That's probably the case, yes.

You might just try retrying.

If you make too many purchase attempts (i.e. when testing things) then Steam will lock you out of future purchase attempts for an unknown (but long) period of time.

Nope, that should work.

You appear to be correct. It looks like the client uses the help site to change passwords now, so changing passwords through the client was probably disabled. I'll mark the method as deprecated.

The owner_descriptions array is empty unless you're the owner of the item.