1,489 karma · joined November 6, 2012
You're pretty much spot on. My average game length is 5 minutes and 7 seconds. lichess tells me my time spent playing is 54 days, 5 hours and 6 minutes and now 15,273 games.
It works out to average just under an hour a day, and I play most days.
Breakdown: 6,157 bullet (90+% are 1+0 but a few 2+1) 7,430 blitz (90+% are 5+0 but a few 3+2) 1,368 rapid (99+% are 10+0) 184 classical (100% are 30+0)
I've also played a small handful of correspondence, chess960, etc. which is why it doesn't quite add up.
Also, does chess.com have anything similar to https://lichess.org/insights/yourusername or https://lichess.org/analysis#explorer where you can select "Player" and see how openings play out for your games only (as well as masters and the whole of lichess of course)?
(for the obtuse, replace "yourusername" above with your actual lichess username)
Prominent example when you click "Play" you go to https://www.chess.com/play and get presented with a chess board. At this point, it actually lets you make an initial move. But you're not playing anyone! You then need to click, for example, "Play online".
The rest of the site is disorganised. For example there's stuff under "Learn" and "Resources" and I can never remember where to find things.
−7th: absop
−6th: absackle
−5th: absnap
−4th: abserk
−3rd: abseleration
−2nd: absity
−1st: absement
The line below that is worse:
strncpy(bloom_path , argv[optind], 128);
If you pass something >= 128 chars then bloom_path won't be null terminated. In general strncpy should never be used for copying strings.
For expansion on that: https://ramblings.implicit.net/c/2014/05/02/c-functions-that...
Here is it in 1997, it hasn't changed much.
https://web.archive.org/web/19971210131642/http://expect.nis...
like, you know, etc.
Australia reporting errors: https://downdetector.com.au/status/wikipedia/
But fine in North America from where I've tested.
SLO - Service Level Objective - the service level you strive for. If it's higher you have room for experimentation, etc.
SLI - Service Level Indicator - the actual metric(s) you use to measure a service level (latency, error rate, throughput, etc.)
Also, SRE here but not for Cloudflare -- I've never seen SREs directly involved in externally published SLAs, they usually come from legal. We deal with SLOs on more fine grained SLIs than overall uptime
In well designed WMs like i3 each desktop is typically bound to a key for instant switching, unlike the full screen atrocity of macOS where there is an unremovable delay when switching.
For example, you can try to imagine what it's like to be a dog, but it doesn't make much sense to ask what it's like to be a toaster.
What's it like to be an artificial neural network? I don't think that's valid, nor is there any good evidence that we're making progress.