(2014-03-08, 02:56 AM)dthiago Wrote: If MySteam is a suite ..plz create a register/login with steam separately.
If I add a Steam login capability, it will either be able to be enabled or disabled with a setting or come in a separate edition, don't worry. I'm all about configurability, and I know that external login features like that are controversial.
(2014-03-08, 04:07 AM)Verilog Wrote: Wow this is a very nice plugin for gaming forums
I'm glad you think so.
(2014-03-08, 05:43 AM)crazy4cs Wrote: Hey,
Just a tip from the skim read at your thread. I have myself made a steam signature plugin too in past with the help of their web XML API. However, if you are not authenticating it, after several http requests, steam will ban the server IP as it will consider a form or attack (maybe "DDoS"). So you may want to look into authorizing it via their API instead of the web XML API (in case you use that).
Thanks for the tip.
I'm pretty sure I know what you're referring to. There are currently two Steam APIs. There's what Valve calls Steam Community Data, which is returned in XML from a Steam user's profile link. That is older and now deprecated. Then there's the Steam Web API, which is Valve's newer (and now preferred) API. This plugin uses the newer API for all of the routine functionality.It does use the Steam Community Data interface for obtaining a user's Steam ID from their profile URL during the initial Steam Integration. The number of requests from that should be infrequent and small in number, so I would be surprised if the Steam network recognized it as an attack. And currently the Steam Web API has no method for "discovering" a user's Steam ID, so using Steam Community Data is required for this function.