Next point.

There is no need to ask a third party about you as crtisism of members operating withing the CG guidelines is never aimed to hurt feelings. When someone is exploiting a certain role (coming with considerable duties) on the other hand that is difficult to ignore. It gets really ugly when someone is pushing into a role that is not appropriate to the community well-being (like cancerous 'selfless' Caissa bashing). You are far from that.

Susan Freeman the person is none of my business, still she uses (regrettably from early on) only one 'Susan Freeman' handle mixing up privat/job regularly. That leads to the strange behavior that almost everything that targets site issues will be addressed to the much more 'responsive' casual Susan persona. The same for stevemcd87 and you beatgiant. Everyone can take it 'personally' to their liking because all roles are shared by one handle. This invites speculation on your part towards my motives which is perfectly normal. To me there is an immanent flaw using one handle for different roles for more sensible discussions. Probably slowing things down on CG when several exchanges cannot pass the point of personal (not very productive) misconceptions so easily. Understand I post in beatgiant's forum but I need 'you both' to listen. Of my concern is 100% the dev only.

Attention: Never must members be allowed posting under more than one handle (abuse is wide open) in this context, totally different back office-staff (here this should be mandatory).

If you know a solution on how I can address beatgiant/dev without interfering with beatgiant/beatgiant in the future that would be most helpful.

That is my bottom line.

Now it's late and a busy week lies ahead.

Delete after reading.

Unrelated

https://www.youtube.com/watch?v=d-j...

But what's disappointing is to read vague remarks about taking "months" for something I delivered days after it came to my attention, assuming something is "easily fixable" although you can't have any idea what exactly caused that particular error, etc. Those reflect on my workmanship here. Yes, I haven't yet made everything absolutely perfect in a few months, but do you understand the scale of the tasks required?

My remark about joining this team was aimed at another kibitzer, but truthfully, I have no role in recruitment here and I agree it was out of place for me to say that.

Game collection errors do snowball. During the time I've been repairing them, already some collections were promoted to historical event pages. Before the repair, those almost always had glitches in the ½ characters in crosstables and score reports, often also in the player names, place names, punctuation marks etc.

Users also often clone collections from other users. I've repaired many of the same errors several times over because a collection and its clones all shared the error.

I've also seen it happen that a user deleted his broken collection before I had time to deploy the repair for it.

So there are a few reasons why game collection repairs have some urgency.

On the other side, yes there are still annoying errors in kibitzing, but it's a lot rarer than it was before the repairs last fall, and it doesn't look like it's making many contents illegible. There are still at this moment quite a few game collection contents that are in a much worse state.

Please, remember without site premium search one has to put some time into finding specific postings in time. There were no current updates on the issue to my knowledge and I wasn't in the the mood to go through a 'fresh' database dump for the date. Still a (formally correct) offhand remark like 'months' was not my brightest hour, lesson learnt.

The separation of roles was hinted at the impossibility to address something professional here without allowing recipients a chance to fall back on a personal level with a much more complicated outcome for both. My short statement made you disappointed which in the end does not help keeping motivation high to remove certain persistent hickups best which is for the benefit of everyone. I shoot myself (∈ ∀) in the foot so it should have been formulated with more care.

'Do you understand the scale of the tasks required'

That's part of my critisism and yes, I do think so by abstraction. Patching might 'never' end - see the 'snowball' example (severity of exacerbating feedback) later on. Giving a considerably short downtime a shot (hit or miss) remains my preferred scenario. Being aware what you and more so stevemcd87 are dealing with here - the difficulty working for a most voluntile and free spinning backoffice, I fear this might not going to end well. To jnpope he (with the help of certain sponsors) is selling himself very well, not sure if that's backed by reality most of the time. The owner is loaded due to personal circumstances and money should not be of a great concern. The site is doing ok during special times.

One more example why 'patching/fixing' on CG to me does not solve a root issue:

Remember fixing these ugly exuberant bios of all these old, famous, more or less interesting chess personalities? The godsend were overly happy and that theme (thankfully) never returned on the daily drama channels. But it is not gone at all unfortunately, still in plain 'sight'.

Give me a random ID that was affected/posted in the Bistro back then and I look it up.

Following an advice that repeating once is already one time too many future remarks will concentrate on encouraging team 'patching' - a most practical choice.

Opinions:

- Kibitzing (this steamship's fuel) is always my first priority as it generates most traffic, members staying on the site the longest all while it produces new content for different interests for free. At the same time 'it [a replacement character in kibitzing] doesn't look like it's making many contents illegible' is true at least for my reading experience. Corrupted input is/was my main concern, right now we are talking cosmetics.

- "Register now. It's quick, free, and anonymous. This will allow you to "kibitz" in our discussion forums, make game collections, and use other powerful features. " Game collections might be the most iconic CG feature ever, but I miss the love and willingness to make it more intuitively available for newcomers. Under normal circumstances not a priority at all, but snowballing within any system (living or dead) should be fought at all costs (nobody can predict where it breaks out). A bit undecided here. Gut feeling taking your observations more serious collections should be locked or stay untouched until a possible repairing schedule is created that is considerably faster and in effect able to catch up with possible new error production. Just a typical race scenario.

Boiling it down to something meaningful:

With a knife on my throat collections are my prio over kibitzing under this circumstances.

Again all this can go smoothly in the bin after reading, not much to add at this point.

Unrelated

https://www.youtube.com/watch?v=4s7...

From a past exchange, elsewhere, on analysis I've come to suspect that <beatgiant> is a pretty sharp card.

I also know, from reading various technical posts (and sometimes having to reread them), that the same can be said about <login>.

It's nothing urgent, but it would be nice to not have to abbreviate or truncate certain sources or event names just to shoehorn them into the current allotted field size.

<PS- All PGN tags should go with varchar(255) to match the standard.>

Avatar Area

https://www.youtube.com/watch?v=bS3...

…Ng5