RobotOpBuddy's forum posts

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#1  Edited By RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts
@crimsonbrute said:

Can't do EA, Bethesda, or MS but I should be able to do all day Monday and Tuesday and maybe Wednesday.

That necro :O

Well, no harm in re-using it for this year I guess - I'll be around to cover all the remaining conferences except maybe Bethesda/SE (but I'll probably show up for the start of them at least still) after that I probably won't be in the live chat much due to work and spending most of the spare time I do have catching up on everything I've missed.

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#2  Edited By RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts

They sort of do, though I agree that it'd help a lot if the default schedule page had the multiple common time zones at least rather than just the one.

Anyway, it's started at this point (though it's only the google stadia done so far, with the 1st big one, EA, starting while I'm typing this) but the schedules for US/UK/AU times are below.

PT(/ET): https://www.gamespot.com/articles/e3-2019-schedule-all-press-conferences-dates-start/1100-6465962/ - this page also has PT/ET/BST/AET times but you have to pick them out of the paragraphs rather than a simple list.

BST: https://www.gamespot.com/articles/e3-2019-press-conference-schedule-uk-times-and-dat/1100-6467466/ - the 2 that say PT instead of BST are actually BST times still, they've just made an error in the text.

AET: https://www.gamespot.com/articles/e3-2019-press-conference-schedule-au-times-and-dat/1100-6467479/

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#3 RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts

On the karma system/forum queue interactions:
Previously (quite a long time ago now, mind) it was +1 karma for the false flagger and no change for the person being flagged incorrectly when you ignore it.
Now it is to be -1 for the person flagged incorrectly and no penalty for the person false flagging.

It's an improvement at the very least, the false flagging penalty removal is debatable but I think with how often we get behind on the queue it's probably best this way - we can always manually up someone's karma if they're repeatedly abusing the system anyway.

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#4 RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts

Blatant fake news/troll thread, locked.

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#5 RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts

This is just a quick test

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#6  Edited By RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts

Missed the EA one in the end (catching up via articles now..), had intended to be on for it but other things got in the way unfortunately. I've got some time off from work this coming week so I plan to be on for as many of the conferences as possible, there's a good chance I won't be on for much of the Bethesda one due to the time though and will probably log off as soon as the sony one is done for the same reason.

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#7 RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts

From what I can tell the only bug (and a relatively harmless one at that) is that the div with class "well article-comments has-pad--max js-load-comments-container hide" is not removing the hide tag at the end of the class when the article comments section is locked (it should be bringing up the little box that tells you that it is locked when you click the view comments button - in much the same way as it brings up the comments as expected when it isn't locked via this same tag being removed from the div class) - locking of comments is normally done by staff when the article comments have gotten out of control and it's not longer considered worthwhile to keep the comments open on the article, in some cases this may be within a few hours after the article is made live on the site if the user response is particularly unsuitable, but the comments are normally open for a least a brief while to allow users to discuss the article - if some particularly bad ones ruin it for others early on then so be it. They may also be closed or even re-opened for other reasons such as whether or not anyone is available to keep an eye on articles likely to have especially volatile/inappropriate comments but it's a staff decision regardless.

I couldn't say what exactly caused these particular articles to be locked as I don't believe even moderators can view the comments in context within the article once it is closed.

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#8 RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts

I've gone through a bunch of these today but it looks like most of the ones in the list now are obvious spam that's already been dealt with - could we look at streamlining this a bit, for instance a lot of the spam ones will be a bunch from the same user and once they're nuked the rest isn't on the forums anyway, manually marking each one and individually confirming them all is time consuming for negligible benefit when they're all basically identical to the previous ones marked as spam and have already been deleted by the previous nuke - something we can skim through after marking one of the users posts as spam or after they're nuked by some other reason to just unmark non-spam posts might be more effective (I would expect most posts from a nuked user to be spam after all, others would mainly be there to mask the accounts but couldn't be used to find spam regardless), or just removing them from the queue outright if the user has been nuked already.

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#9 RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts

It's showing 3 stacks on your profile for me, even though you have 5 (the standard ones) - my own actually says -3 when I look despite also having 5 and angerawr's is showing -1 as well despite also having 5. I recall it being an issue with creating and deleting stacks that caused the number discrepancy originally, and I'm not sure if that number counts the 5 default ones that we all have or not, but I've never had any issues with creating new ones as a result of it.

I'm going by the number on the stacks header of course, the number on right hand side of the actual stacks page seems to be reliably correct, though I'm not sure why they'd be showing different things to begin with if they're meant to represent the same thing.

Avatar image for robotopbuddy
RobotOpBuddy

65499

Forum Posts

0

Wiki Points

472

Followers

Reviews: 0

User Lists: -3

#10  Edited By RobotOpBuddy  Moderator
Member since 2004 • 65499 Posts

@olddadgamer said:

Hey, @Byshop, @wcarle:

Another issue with the nuke: When term messes up, the nuke button still says "Nuke," so we have no way of restoring mistakenly nuked users when term does it, only when humans do it. An example:

https://www.gamespot.com/profile/stonesour/comments/

This doesn't happen often, but when we do have term being over zealous, we have to involve all y'all. Might be good if we had the ability to fix it ourselves.

It'd be nice to be able to fix these ourselves yes, but if term has made an error it's probably best to loop staff in regardless in this scenario in case it's something that can be avoided in the future or an update to terminator that has made it go on an unwarranted killing spree. You can always have a look at this thread if terminator has forgotten to add a note for some reason when it nuked an account too, as terminator logs all of it's nukes there. The keyword or rule trigger is typically a good indication if the problem is terminator's rule or if it's just a new-ish user using a term that is frequently used by spam accounts.