Stack Apps

« first day (3189 days earlier) ← previous day next day → last day (1830 days later) »

3:02 AM

@BrockAdams One hour left...pinging early to take care of any ping glitches. By the way, thanks for helping out!

3:19 AM

@gparyani Have the script. Just need to handle some states (reopen, prev close vote, etc.), do a final round of sanity checks, and publish. Should have it up within 3 hours, but no promises. If not, it will be tomorrow morning.

gparyani

Thank you very much!

3 hours later…

Brock Adams

6:24 AM

@gparyani Okay try this script.

It's not as finished/polished/tested as I like, but the SE devs may end up bug-fixing the mechanism it uses.

gparyani

@BrockAdams That's the point. Composing bug report...

@BrockAdams Also, reason 2 ("off topic") is a general close reason, with no options for sub-reasons. It just works on its own, unlike reason 102 which requires a sub-reason.

Feeds

Q: Restore missing and/or obsolete Close-Vote Reasons

About: This userscript restores missing/obsolete close-vote reasons to the close-vote dialog. This script is in response to: A Chat request where the poster pledged to use it in conjunction with a bug report. Requests, like this one, to restore/add the customary close reasons to Teams si...

Brock Adams

@gparyani Noted, thanks. Dev on the script is now halted pending the outcome of the bug reports and on demand for the idea (if any).

gparyani

@BrockAdams Would be nice to have it in the script, though, since I personally find the old "off topic" close reason to be more explanatory on the blatantly off-topic posts we get on MSE rather than the current one.

Brock Adams

@gparyani Yes, but I'm not going to spend time on it unless (1) SE says they're fine with it and (2) more than one person wants it (unless that person is me).

@gparyani, I see your suggested edit (1) I'm not sure it's true and (2) are there any sites where the duplicate reason is not already naturally available? It looks like that's the one reason that's always present...

gparyani

6:41 AM

@BrockAdams The "duplicate" option currently shown in the dialog is reason 101. "exact duplicate" in my edit refers to the old reason 1, which can't be voted for anymore.

The difference between the two is that reason 1 causes the target to be edited into the body by the Community user, while 101 causes it to be shown as an automatic box. (The notices were otherwise changed so that they're identical, but in the revision history you'll notice the difference.)

I could not figure out how to pass in a target to reason 1, and my tests just using it raw resulted in a plain vote for that reason with no target. So it's preferable to leave it out.

Brock Adams

@gparyani Okay. Why would we need reason 1 when reason 101 seems to be a good replacement?

gparyani

You wouldn't. "So it's preferable to leave it out [of the script]".

The explanation there is, you can't vote to close for reason 1 in the script, because there's no way to pass a target into it and it essentially duplicates (pun intended) reason 101.

Brock Adams

It's already left out by the current script logic. If reason 101 is present (it always is), reason 1 is not added.

gparyani

@BrockAdams Okay. One last question as I'm composing the bug report: do you want to be credited as "Brock Adams" or "Awesome Poodles" (your MSE username)?

Brock Adams

@gparyani Doesn't matter. But link to the Stack Apps post.

gparyani

6:59 AM

-1

Q: Possible to vote to close for old, decommissioned close reasons

After doing some twiddling with Stack Exchange JavaScript, I discovered it's possible to vote to close for old, now-decommissioned close reasons such as "not constructive", "not a real question", and "too localized". Basically, it involves making a POST request to the flags endpoint, like so: $...

bug vote-to-close close-reasons security

The bug report.

8 hours later…

Feeds

3:38 PM

Q: What determines whether or not tags are returned when querying answers?

I'm querying the api for answers, and I want the tags set on the associated questions. I seems to be seeing intermittent results: sometimes the tags attribute of the response includes the tags, and sometimes it's an empty list. Is the availability of the tags attribute influenced by any other a...