Forum:Moving Gaz Bot GE update notification

From Old School RuneScape Wiki
Jump to: navigation, search
Forums: Redwood Grove > Moving Gaz Bot GE update notification
Replacement filing cabinet.svg
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 21 November 2019 by iN008.

Formal petition to move Gaz Bot's GE update run started/finished messages from #wiki-osrs to #recent-changes-osrs.

This has come up on three(?) seperate occasions on discord, so it would be nice to just get a final decision on this and move on.

Discussion

Support - As nominator. iN008talk 21:28, 5 November 2019 (UTC)

Support - For every non-supporting vote. I will sacrifice a kitten to the rats of Ardougne. Shoyrukon (talk) 21:30, 5 November 2019 (UTC)

7li55AR.png -- Recent uploads SpineTalkContribs 22:28, 5 November 2019 (UTC)

Oppose - I like seeing GazBot out and about. -- Recent uploads SpineTalkContribs 22:27, 5 November 2019 (UTC)

Are you implying you don't check recent-changes-osrs mr. head admin iN008talk 23:36, 5 November 2019 (UTC)
Let me amend that. I would like to have GazBot on both channels. -- Recent uploads SpineTalkContribs 23:52, 5 November 2019 (UTC)
I see through you 👀 iN008talk 23:56, 5 November 2019 (UTC)

Support - as fun as it is to wowee on every gazbot post, we can do that in #recent-changes-osrs even if not as many people will see all the wowees :( Crow653 (talk) 22:36, 5 November 2019 (UTC)

Oppose - GazBot finishing a GE run is not a recent-change. I'd much rather keep it in #wiki-osrs where it can be seen. --dDbvitC.png Scuzzy Beta hib8CAd.png 04:51, 6 November 2019 (UTC)

Conditonal Support - Only if in the event of an update failure that a notification is sent to #wiki-osrs, per fetus's suggestion. -dDbvitC.png Scuzzy Beta hib8CAd.png 05:00, 10 November 2019 (UTC)
Disagree, it directly alerts us that a batch of edits have started/completed. Keeping it where it can be "seen" is a non argument that doesn't make sense, unless you are implying that nobody ever looks in rc which simply isn't true. iN008talk 07:25, 6 November 2019 (UTC)
Okay, I'll entertain this push-back. Visibility is a valid argument - Sure, some dedicated editors look in recent-changes, but the quantity of messages that get sent through to that channel is notably larger than the average day in #wiki-osrs. That message is important to see in case someone reports our prices being outdated (which has happened a lot recently), so we can therefore take appropriate measures (like restarting the bot). In addition, *if* someone, say a new editor, has a question about the GE prices, we can easily redirect them to a message in the same channel they'd presumably be asking in. --dDbvitC.png Scuzzy Beta hib8CAd.png 23:36, 6 November 2019 (UTC)
The visibility argument is very much disputable. If the message is important for when an issue comes up: discord has a perfectly functional by user search option which can very quickly find the latest ge update or lack thereof (there should only ever be 4 messages in a cycle, 2osw 2rsw, this is all gaz bot posts). Messages can also be linked to whoever necessary, however one could just as easily link the chisel status page directly. iN008talk 05:29, 7 November 2019 (UTC)
"the quantity of messages that get sent through to that channel is notably larger than the average day in #wiki-osrs." This is easily shown to be incorrect -- there are more messages in wiki-osrs than in recent-changes-osrs, and the messages in wiki-osrs are generally larger and harder to sift through.
It's also hard to imagine why linking to a message in the same channel as wiki-osrs would be an important distinction. ʞooɔ 04:56, 10 November 2019 (UTC)
Regarding the possibility of having GazBot send a failure message to wiki-osrs: that doesn't really work -- most of the times GazBot fails to run, it's because there's a larger issue that would also prevent it from accessing the Discord webhook. ʞooɔ 05:05, 10 November 2019 (UTC)
Is there a possibility that this can be worked around? Perhaps having a much more visible indicator somewhere onsite, or even the status page on chisel? I realise chisel already has something like that but it's not exactly clear. -dDbvitC.png Scuzzy Beta hib8CAd.png 05:08, 10 November 2019 (UTC)
Comment - Visibility of GazBot's operational status is inherently useless to majority of the users and, I would assume, admins. Personally, I have never checked or bothered to check whether each update was completed successfully after seeing the automated message. I highly doubt any of the active participants on discord follow up with manually checking Gaz's bot status page after each update. Another issue the discovery of outdated GE prices is not-related whatsoever to public notifications from GazBot. Non-registered users are unable to edit the Exchange page. By extension hides and prevents the update price button function on the Exchange item pages. Users generally join discord to ask why a price was outdated or how to update the GE price. Regardless of how we discover the outdated price, the solution that is occurs most often is to ping Gaz to check on GazBot. In the last few occurrences, I believe Gaz added new item checks to the bot that is used to check for price updates. Shoyrukon (talk) 04:39, 10 November 2019 (UTC)

Support - The messages are large and automated, and serve no practical purpose to a vast majority of the users in #wiki-osrs. It makes sense to move these messages to #recent-changes-osrs because that channel is designated for automated messages relating to edits, and is monitored by a smaller set of people. Having some visibility on bot edits is still a plus, so I am not opposed to the messages appearing among other recent changes. Recent GE update messages can still be found easily using the Discord search tool. I imagine this is how you would want to locate these messages anyway, though I have never needed to do this a single time.

The large messages reduce visibility on relevant discussion, for example on a message like this. Though the bot messages aren't the only reason this conversation didn't continue, it is clearly distracting to surround a pure text message with two visually interesting blocks containing 8 individual images (6xWowee, 2xOSRS). We try to avoid actual discussion in the recent changes channel because the bot messages are generally irrelevant to the conversation. The same applies for automated messages outside of that channel. Riblet15 (talk) 21:29, 9 November 2019 (UTC)

Support per Scuzzy - I don't like seeing GazBot out and about. GazBot finishing a GE run IS a recent-change. ʞooɔ 04:20, 10 November 2019 (UTC)

Comment - Add GazBot notifications to #code-deployments as well, I like to see what is hammering the servers. - TehKittyCatTalk 00:21, 18 November 2019 (UTC)

Closed - There is consensus to move GazBot notifications to #recent-changes-osrs, with no opposition on also including these messages in #code-deployments for kitty. iN008talk 13:25, 21 November 2019 (UTC)