Absentee landlord?

If only Daniel had implemented the sandbox idea...

It's certainly not an easy task keeping the database consistent when uploading. In fact, it's quite difficult, in general.

But especially here on <CG>, with some of its quirky, if not even counter-productive, conventions.

What, no roses or chocolates from Hazz?!

<When the 30-year-old founder of a Canadian cryptocurrency exchange died suddenly, he took the whereabouts of some C$180m ($135m; £105m) in cryptocurrency to his grave. Now, tens of thousands of Quadriga CX users are wondering if they will ever see their funds again.>

Of course, my posts of late have been of a different nature than from a few years ago. At the time I really thought <CG> was amendable to new ideas. I know few biographers shared my technical interests, important or unimportant though they might be, but I did appreciate the support on my researches, and the few cases of fellow users, like <crawfb5>, who actually were willing to try some of the new ideas prototype implementations.

The long posts I wrote in reply to <Tab>, (endlessly!) outlining much of my ideas, originally had the hope of winning converts. But please don't think me naive, I soon knew <Tab> was firmly obdurate in his opposition - but I always hoped that there was an audience of at least one who I could ultimately win over - i.e. Daniel.

That's why I posted so much in detail - in the hope that someone experienced in actually implementing and managing such a large database, and who could truly appreciate the issues, would one day come to also appreciate the proposed solutions.

Let's face the facts - doing everything by hand doesn't cut it, and I exposed numerous examples of <CG> failures in this regard.

Daniel appreciated this as well, and the one time I actually used the email channel was in a shared attempt to implement bulk submissions for <CG>, in particular, Altona (1872). Unfortunately, after the inevitable first glitch Daniel lost interest. Though disappointed, I always hoped Daniel would take it up again.

Sadly, fate determined otherwise.

Still, I had some measure of hope, and did leave <Sargon> two important posts to try to orient him during the "troubles". But, at the time, he was MIA and/or otherwise occupied with learning how to run the site. I always intended to write a third post, one which might now get accepted given that <Switch> is now gone, but I never did.

Why should I really bother? <Sargon>'s management style is quite different from Daniel's.

Cleaning up my blog, I saw how that a tremendous amount of time and energy was spent writing software tools for <CG>, four years ago. In hindsight, this was a mistake, as <CG> is actually the most difficult case to work with.

No.

<I want to know whether CG is muzzling me only.>

Polugaevsky - Mecking Candidates Quarterfinal (1977)
FIDE World Championship Knockout Tournament (2001/02)

Umm, I'm thinking it's better say "by winning Corus Group B, he qualified for participation in Corus <Group A> the next year." Not just "Corus" next year or "Tata Steel" next year, but "Tata Steel Masters" as Sargon has it for 2019. Here's my suggestion:

Hoogovens (1996) --> Hoogovens Group A
Hoogovens (1997) --> Hoogovens Group A
Hoogovens (1998) --> Hoogovens Group A
Corus (2000) --> Corus Group A
Corus (2004) --> Corus Group A
Corus (2005) --> Corus Group A
Corus (2006) --> Corus Group A
Corus (2007) --> Corus Group A
Corus (2008) --> Gorus Group A
Corus (2009) --> Corus Group A
Corus (2010) --> Corus Group A
Tata Steel (2011) --> Tata Steel Group A
Tata Steel (2012) --> Tata Steel Group A
Tata Steel (2013) --> Tata Steel Group A
Tata Steel (2014) --> Tata Steel Masters
Tata Steel (2015) --> Tata Steel Masters
Tata Steel (2016) --> Tata Steel Masters
Tata Steel (2017) --> Tata Steel Masters
Tata Steel (2018) --> Tata Steel Masters

<Stonehenge> I've been processing a lot of your slips too, actually... mostly on player names. Thanks for the good work! :D

<MissS> I'd love to give you preferential treatment too, but many of your submissions tend to be less clear-cut than the ones I'm fast-tracking. Anything that requires checking up on (conjectures, drawing attention to corrections by other users, etc.) gets relegated to the second round of slip processions, because I'd rather implement the simple and uncontroversial corrections first. I did process quite a few of your simpler ones. :)

The game uploads have run into a little holdup in that the game viewer on the submissions page isn't working well yet. I can process them anyway, but I have to use some independent viewer to check them, which is inconvenient so I'd rather wait until Sargon works out the viewer's problem, given that I have the slips to do as well anyway.

But to help y'all feel better, I'm willing to take a few special requests to process uploads you feel particularly strongly about. ;)