All this code shows is that all the passwords are stored with bcrypt now. Before using bcrypt they used SHA1 hashes with a salt pepper :(. Those are relatively easy to crack because SHA1 hashing is very very fast.

Sadly, they seemed to have used a single salt (so actually a pepper) for all passwords:

// SHA1Salt is the single salt used for all pre-BCrypt passwords
SHA1Salt = "theleakedcodecontainsthepepper"
// PasswordCutoffTime is the last time we reset passwords. Passwords older than this timestamp must be reset
PasswordCutoffTime = 1427025600 // March 22, 2015, never forget

If you logged in since March 2015, you'll have reset your password and it should no longer be stored as salted SHA1.

If a database ever leaks with the salted SHA1s still in them, it would be trivial to crack all those old passwords.

Nothing wrong with the late payment arrangement, that way more teams can play and banny gets more money at the end of the season.

The .vdf file makes your server load the plugin, so you'll need it to make it work.

FIA on VER
FIA on BOT

VER took 6 new elements, causing a grid drop of more than 15 places, which means you start at the back of the grid.
BOT took 3 new elements, causing a 15 place grid drop.

This was looking like the most boring qualifying this season, and then Russel put on the slicks

https://github.com/F2/F2s-sourcemod-plugins

All here, as a package or individually

I think this is a common misconception, the high ping of one (or even most) other players won't affect your experience by itself. John Carmack got it mostly right back in 1996.
The "teleporting timmy" example is way more annoying for other players, but a ping limit doesn't fix that.

The rule shouldn't exist at all.

A linux-based TF2 server started with -autoupdate will auto-restart if you send a kill signal. So the simplest thing to make the above suggestion work is to add a crontab entry that runs:

killall srcds_linux

In

tf/logs

He backed out in S3 :( Sadly, couldn't do it despite being cut from the team

https://demos.tf/about

I think most or even all of the demos are stored on Hetzner servers in Germany. Some ISPs love to fight with them over bandwidth and refuse to set up peerings, causing slow speeds for that ISP's customers.

He's a lucky boy

I think you can blame the driver that was behind, on the dirty side of the track, missing the apex, understeering into his opponent.

Hehe, those are some cool queries, I was hoping you were just missing some indexes or something, but it looks like you got all that covered.

An on-the-fly aggregation like the peers is always going to be challenging, especially since you're trying to find the top 100 players most played with/against.
One thing I would consider, is to move "log_wlt" and "player_last" from views to materialized views (unlike a view these need their own indexes). You could update these materialized views (concurrently) after a new batch of log files is imported. This might improve part of the peers query.