This should already be happening. I'll try reproduce this soon.

If the ticket was closed with no action taken then it was because the assigned admin deemed the ticket invalid.

I've forwarded this information as well as three other emails that I received on to our ads team who informed me that they're aware and trying to track down the malicious ads already. We're sorry about this issue, and I know it's been an issue in the past as well.

Originally posted by HusKy:

Originally posted by Sneeza™:

There's rate limiting on the amount of requests to Steam profiles that can be made, significantly reducing the throughput of each bot. It's a significant reduction in what they can process.

Actually, you can just read all the necessary information from the headers. You never have to visit steamcommunity website. Or perhaps I'm just missing something.

They can, but the request to resolve a steamid has rate limiting and just sends back an error when they try to request too many steamids too quickly.

Sorry that's a bug - will fix.

Edit: Should be fixed now.

Originally posted by HusKy:

Seems like it's not possible to search in "display" names. This was pretty useful. I hope this feature can be brought back.

You can still do this but the results are limited in quantity. There's no point searching for some generic username like "Bob", you'll just get thousands of results back.

Originally posted by HusKy:

This is a never ending story, they will find new ways how to obtain SteamIDs. They are already raping bazaar. Who knows, maybe one day Valve will wake up.

edit. Wait, is this just adding 1 extra http request?

There's rate limiting on the amount of requests to Steam profiles that can be made, significantly reducing the throughput of each bot. It's a significant reduction in what they can process.

As for Bazaar, they just don't have any protection at all. Your steamids are literally output into the code on the homepage. Each time one of us implements countermeasures the bots will just shift their focus to the other. It's a lose-lose situation for both of us.

Okay, I just pushed an update that should help throttle the amount of requests that the bots are able to send out. We'll continue to look into other solutions but for now you should see a reduction in the rate that invites are being sent.

https://steamhost.cn/steamcommunity_com/dev

I've just had a heated discussion with Zemnmez and we think we may have a good solution which should help throttle phishing bots. I'll keep you posted.