If it's that big of an issue for valve... then just force users to register servers to their steam account. Then valve could easily inform everyone on policy changes and there should be no excuses.
Honestly it wouldn't be that much of an inconvenience to register a server with valve. And there really should be no reason to ban TF2/DODS/CSS/whatever other game server just because someone didn't feel like listening to valve. And I say this as someone who should probably be happy that my "competition" got banned. Yet it doesn't feel quite right, so I should say something. On Fri, Jul 24, 2015 at 2:21 PM, Daniel Barreiro < [email protected]> wrote: > Please try to keep this thread specifically to the GSP issue. We know you > were banned and you can yell in other threads but there is the inherent > issue of IPs getting banned and affecting GSPs > > I've been brainstorming methods to deal with the inherent issue of GSPs > getting blacklisted due to malicious users and I've come up with a few. > > The first would be similar to the auth system but for GSPs. In this system > a GSP would be able to register themself as a GSP and get a token. They > would then add this token to the launch parameter of any server so it'd be > flagged as a GSP to the master servers. When Valve then goes to blacklist > servers, they blacklist any unregistered servers and then notify whoever > registered the GSP token that their servers are being used to do it, > provide the IP, and if they don't remove the plugins within 48 hours the > IPs will be blacklisted. > You could make this token easy to obtain (automated signup) or slightly > harder to obtain (you apply as a gsp with your site, email, etc and then > they assign a token). I would suggest the first though as I don't see much > benefit from an approval system. > > > The second one would be a similar system where GSPs could sign up and > input their IP ranges. If any of these servers are flagged by Valve the > person with the IP registered would then be notified when a no-no is > detected and give them 48 hours to remove it or else get it blacklisted. > > > The third would be a combination of the two (hardest to code but most > secure). A system where GSPs can register their IP ranges and then receive > an auth token that links back to them. When an abusive server is found it > checks for an auth token and if it finds one checks that auth token against > the IP to see if the IP is registered to the GSP. If it is give them a 48 > hours warning to deal with it or else the IP gets blacklisted. > > > A benefit I can see with an auth system like this would be it could also > open up a way for users to report community servers to the GSP. If someone > reports a server it could notify the owner of the token as well as Valve > > The second two are just variations of the first and there are caveats of > this, but I would appreciate if we could have a proper discussion of how to > resolve the issue involving Game Server Providers without anyone hijacking > this thread. > I realize this probably wont stay civil sadly but if we want to get a > response we need to keep it that way. > > > I know there is a split community on whether or not GSPs should baby-sit > their users and this isn't about that. Web hosts have methods to deal with > DMCAs and abuse reports for a reason. They let their users do whatever and > if someone reports a site the web host then deals with it. > > I personally don't think GSPs should baby-sit their users but they should > take responsibility for dealing with abusive users when one is found. If > they are notified and don't take action that's when you punish them. > > ~Daniel > > _______________________________________________ > Csgo_servers mailing list > [email protected] > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers >
_______________________________________________ Csgo_servers mailing list [email protected] https://list.valvesoftware.com/cgi-bin/mailman/listinfo/csgo_servers
