« first day (2621 days earlier)      last day (1192 days later) » 

12:16 AM
Makyen/EC2-num02: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 63b113a (Makyen: This is the MS instance, so needs to post feedback) (running on Makyen/EC2-num02, Python 3.6.12)
 
12:35 AM
Restart: API quota is 7110.
[ SmokeDetector | MS ] Potentially bad keyword in username (1): Windows 10, sshd.exe missing by atahualpa on superuser.com
 
[ SmokeDetector | MS ] Manually reported question (93): Stack Overflow is really bad by auser on stackoverflow.com
 
tpu- feedback received
 
Once again, I would love site-specific watchlists. Any post on SO that contains "downvote" should be reported.
I'm wondering about watchlisting "go ahead and ban me". I've seen this more than once, and I can't think of any cases where it would be a FP.
Should also account for "go ahead, ban me" and "go ahead to ban me", but that should be easily accommodated.
Actually... I think I'm comfortable enough with 2 FPs for "ban me".
!!/watch ban\Wme
 
[ SmokeDetector ] Blacklists reloaded at rev 91d9e7d (SmokeDetector: Auto watch of ban\Wme by Cody Gray) (running on teward/Osiris)
 
12:52 AM
 
Actually, I think it's about 200, but still more than I think is reasonable.
 
1:06 AM
2 TP, no FP for go\W+ahead\b.+\bban\W+me
(probably want to limit that .+ a bit, though)
sdc watch go\W+ahead\b.{1,25}\bban\W+me
 
@RyanM That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; in addition, the regex contains an unescaped "."; in most cases, it should be "\."; append -force if you really want to do that.
 
How about go(?:[\W_]*+(?:ahead|and|to)?)*+ban[\W_]*+me It has 8 TP, no FP as far as I can tell.
 
interesting
 
Basically, what Cody said "account for "go ahead, ban me" and "go ahead to ban me","
 
1:12 AM
tpu- feedback received
 
doesn't look like anyone's used "to" in that way in MS, but doesn't hurt at least
hmmm, actually I don't think that's quite right
 
@Machavity You gotta put it in quotes!
 
@RyanM That would not surprise me in the least :)
What's the issue?
 
Oh
I just searched the MS posts, not the entire corpus.
My bad.
 
actually I think it does work because of the ?
I would have written it as go[\W_]*+(?:(?:ahead|and|to)[\W_]*+)*+ban[\W_]*+me but that might just be personal preference
either way I think that's a good watch, +1 to adding it
 
1:17 AM
Yeah, your version is equivalent I think.
 
!!/unwatch ban\Wme
 
Note that I have no clue as to the efficiency differences here.
 
I've put away the hacksaw. Let's try that again, with a bit more surgical precision, perhaps.
 
@RyanM Yeah, that checks out, it's equivalent.
@CodyGray We're working on it :) No need to rush these things, a little tweaking before we add a watch would probably be good.
 
1:19 AM
Your choice :-) that version was your idea, so I'll let you do the honors :-)
 
Ok, if there's no strong objections to it, I'll add it. You can remove your previous one I think. I'm pretty sure it would be rendered redundant with this one.
 
fp- feedback received
 
@cigien Yeah. I kind of have to do everything in a rush. During a meeting this morning, our "chief strategist" promised a client that we would be rolling out a new cloud-based data management platform by March or April. We have only just begun (within the last week) to discuss the architecture of such a platform.
It drives me crazy.
 
3 months? That's ... ambitious.
Are you sure it wasn't March or April 2022? ;)
 
1:23 AM
I'm positive.
I double-checked. :-(
 
Well, good luck with that. I'll miss you in SOCVR :'(
 
But yeah, that's the pace my life moves at. Dozens of projects, 3 or 4 engineers.
It spills over, unfortunately.
And it makes me a person I don't want to be: sloppy.
 
Oh, wait. Ryan's old version never went through, so nothing to unwatch.
 
No, just me. Already fixed.
 
K, let's see if mine needs to be forced. I don't think it will ...
sdc watch go(?:[\W_]*+(?:ahead|and|to)?)*+ban[\W_]*+me
 
Would be much funnier if it responded with
> @cigien You are now banned.
 
No bans here, Charcoal uses bricks instead :)
 
fixed it for you
 
Thanks :)
That's a scary image :(
 
Not safe for work, in the OSHA sense.
 
1:31 AM
Indeed. It looks like the bricks are about to start falling out of the bottom-right corner!
 
Those ropes are fraying for sure.
 
The ropes are missing altogether in the bottom-right corner! There's clearly a gap the width of a brick.
 
[ SmokeDetector | MS ] Offensive body detected, offensive title detected (97): Understanding the definition of fascism by user32099 on politics.SE
 
fp feedback received
 
2:17 AM
[ SmokeDetector | MS ] Misleading link, potentially bad ns for domain in answer (25): Calculating Ethereum Gas Fees by Undead8 on ethereum.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in body (1): DNS my A Record - getting Content from my Subdomain by B2B TECH Ltd. on superuser.com
 
fp feedback received
 
2:33 AM
[ SmokeDetector | MS ] Offensive body detected, offensive title detected (97): Did fascism abolish the welfare state? by user32099 on politics.SE
Makyen/EC2-linux: Executing automatic scheduled reboot.
 
2:59 AM
tpu- feedback received
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Did Carl actually get raped? by Anishica Brady on movies.SE
 
fp- feedback received on [MS] Did Carl actually get raped?
 
@SmokeDetector tpu- edited in grace period to just "gggggggggggggggggggggggggggggggggggg"
 
sdc bisect spinbackup.com
 
@RyanM Matched by spinbackup\.com on line 23094 of watched_keywords.txt
 
sdc blacklist-website spinbackup\.com
 
3:33 AM
 
fp feedback on autoflagged post: How to undo selection in optional select [MS]
Autoflagged FP: flagged by @SmokeDetector, @Rubiksmoose, @Rob
 
The watch on uxplanet.org is getting us very little, including now a bad autoflag: metasmoke.erwaysoftware.com/domains/41156
Annoyingly, it was clearly spammed once
I'm somewhat inclined to remove it after the 18 FP/NAA, but the spam post gives me pause. Any thoughts from others?
 
3:48 AM
[ SmokeDetector | MS ] Link at beginning of body (43): why the "operator=" here doesn't work in this c++ program? by 曾兆杰 on stackoverflow.com
 
fp- feedback received
 
@RyanM Why not just watch the specific domain? It's unique to the TP.
 
@cigien Perhaps I'm missing something, but aren't they all the same domain?
 
I meant specifically uxplanet.org/top-user-experience-ui-ux-design-agencies-3696f3daed4e If that pops up again we can catch it, but we don't have to catch all uxplanet.org links.
 
hmmm...not a bad idea
sdc watch 3696f3daed4e(?# uxplanet.org)
 
Why is that spam btw? I haven't followed the link, but it looks NAAish to me.
 
sdc unwatch uxplanet\.org
 
Hmm, no, I read the question. That's not NAA, it's promoting something.
 
@cigien between the almost complete irrelevance, the link on SEO keywords ("UX Agencies"), and generally a bunch of spam for agencies in general, it just looks so spammy that it lacks plausible deniability as not being spam, IMHO
yep :-)
 
4:00 AM
:)
 
I half expected it to not be spam given the other FP, or for the other FP to also be sketchy...but nope. Exactly one piece of clear spam, and the rest don't look too bad.
 
anyway, back to flooding the channel via metasmoke :-)
 
Yeah. I definitely haven't looked at all the others, but the few I looked at seem all right.
 
4:04 AM
Is there a chance that this pull request can be reviewed and merged? As far as I can tell, the only thing blocking it from implementation is that the code needs to be documented more.
Have there been any changes to the codebase that break any of the changes there?
 
There's no rush to doing so; I just want to know what its current status is.
 
Rob
@SmokeDetector That user's post was deleted 9 minutes after posting. Their prior post was also deleted. Despite being marked ❌ here (for both their posts) I feel that between being deleted and repeating their promotion of one site (with many links and offsite images) the post is certainly undesirable. I guess we'll leave it to an admin @Makyen to review, and determine if they support the Autoflag or will penalize Rubik's and my feedback.
 
Rob
4:09 AM
@RyanM I replied to the Autoflag.
 
@Rob You might well be right...to me, it looked like they were just linking a bunch of resources they found on a random web search, especially give the large amount of FP on the domain. I know that "link a bunch of other stuff plus the site being spammed" is a common tactic, so it's possible that I was fooled. I thought it was, at least, not the sort of thing we should be autoflagging, though I agree that neither are particularly great.
 
fp- feedback received
 
4:23 AM
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (72): Automate the downloading of Data Export zip files by salesforceninja on salesforce.SE
 
Rob
✔️
 
API quota rolled over with 5655 requests remaining. Current quota: 19999.
stackoverflow: 1846
math: 1273
ru.stackoverflow: 747
es.stackoverflow: 511
physics: 496
superuser: 488
askubuntu: 410
pt.stackoverflow: 374
stats: 333
electronics: 329
unix: 328
tex: 291
gis: 268
blender: 258
serverfault: 253
mathoverflow.net: 226
salesforce: 219
english: 211
ell: 195
diy: 173
dba: 169
worldbuilding: 155
mathematica: 137
wordpress: 132
magento: 122
codegolf: 117
apple: 115
codereview: 108
softwareengineering: 103
cs: 101
security: 101
gaming: 97
rpg: 94
scifi: 93
academia: 88
chemistry: 84
[ SmokeDetector | MS ] Potentially bad keyword in body, blacklisted user (72): Text hiding when i apply data-aos="fade-left" by Lohith Y O on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Hardware for ML and DL by Joel Company on stackoverflow.com
 
[ SmokeDetector | MS ] Bad ns for domain in body, bad keyword in body, bad keyword in link text in body, bad keyword in title, potentially bad keyword in body, +1 more (360): best mba colleges in bangalore by abbsmba on stackoverflow.com
 
tpu- feedback received
 
fp- feedback received
 
!!/watch abbs\.edu\.in
 
4:47 AM
[ SmokeDetector ] Blacklists reloaded at rev bab3d72 (SmokeDetector: Auto watch of abbs\.edu\.in by tripleee) (running on teward/Osiris)
 
@Rob I'm tempted to say TP due to substantial plagiarism. However, the plagiarism aspect appears to be more an issue with not understanding how we quote things (i.e in a blockquote and very clear attribution). The portions which are copied do provide a link to where the text is from in one of the various semi-standard reference notations. It's just not clear in our format that what they are doing is copying.
So, basically, I'm OK with deletion in the state it was in, but I agree that red-flag deleting was probably not appropriate. A better solution would have been for it to be deleted by a moderator and the moderator leaving at least a link to the referencing page in the help center. Alternately, it would have been possible to edit it to put the copied sections into blockquotes. However, my problem with just doing that is that the copied portions are a quite large percentage of the post.
However, overall, I'd go with FP here.
 
5:05 AM
[ SmokeDetector | MS ] Bad keyword in body, potentially bad keyword in body (96): What are CBD products and how can they benefit your health? by dustinvernon on medicalsciences.SE
 
tpu- feedback received
 
Rob
@Makyen It was deleted by someone, along with their prior post; whomever (presumably the moderator) found the flag helpful. It certainly seems on the line, and a comment would prevent a third instance; rather than having one's posts mysteriously disappear. In giving the benefit of the doubt it could be found FP. --- If I'm ever asked why I have too many wrong feedbacks this will be one of several excuses. :)
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): How to create copy button in java script? by Ashika Kamath on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body (95): How you can find best Ledger software for Business? by GovReports on stackoverflow.com
 
tpu- feedback received
 
sdc watch govreports\.com\.au
 
5:14 AM
 
sdc watch-number + 1300 65 25 90
 
sdc watch-number + 61 2 8078 6146
 
5:16 AM
Can I just assume that cigien is handling all the spam?
Yes. Cool, cool, cool.
 
You're otherwise preoccupied at the moment I noticed, so I figured I'd cover for you.
 
Oh, you noticed that?
I think I've typed enough words, don't you?
 
That's not for me to say. I actually don't know how I would approach this situation at all, and I don't generally feel like I have no idea.
 
How do you feel about double-negatives?
 
They're fine when the meaning is clear. It depends on whom one is addressing of course.
 
5:20 AM
The meaning to that was clear?
"I ain't generally got no idea."
 
[ SmokeDetector | MS ] Bad keyword with email in body (56): What should I do with this? by KU_021 on writing.SE
 
Apparently not. Sorry, I'll rephrase.
 
It took me several reads, but I think you probably mean that you aren't generally in a situation where you have no idea how to approach the situation.
 
I usually have some ideas for how to deal with a situation. This is not one of those situations.
Yes, exactly.
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): smart contract transaction error by Austin Gillam on ethereum.SE
iBug/Lily: Executing automatic scheduled reboot.
 
5:26 AM
@cigien I guess I won't get any advice, then. :-(
 
[ SmokeDetector | MS ] Bad keyword in link text in body (69): How to create a Live stream using Mux api? by Oiceotse on stackoverflow.com
 
fp feedback received
 
@CodyGray I'm afraid not. In fact, the situation is such that I can't even tell if it's better to continue trying at the moment. It might make the situation worse, but then so could disengaging. I'm sorry, it's a very tough one.
 
@cigien Yeah. I am struggling with that, too.
I definitely wanted to wait until I cooled off, but... I hadn't completely lost hope or flipped the bozo bit, so I thought I'd give it one more chance.
Like I said above, I think I've said everything I can possibly say.
At this point, it isn't going to do any more good, because it won't be a matter of a lack of clarity.
But it's easy for me to get sucked into an infinite regress of trying to explain and elaborate.
 
Ah, if you feel like you could cool down some more, then I can give some advice: do that, even if it means that disengaging might send the wrong message. I personally have found that interactions have always gone more poorly when I was hot under the collar, so to speak. I certainly don't think the situation is irreparable, and there is no urgency to try. Take a break, and you might get some ideas for how to tackle this at a later point.
 
5:36 AM
I don't actually think I could cool down much if any more than I already have.
What I meant was, that's why I stopped engaging earlier, but resumed now.
 
Oh, I see. That's what I thought you had done, so I was a little confused. Yeah, you've expressed yourself as clearly, and calmly, as I think is possible. At this point, I don't think making logical arguments is going to get you anywhere, if it hasn't already. Something different is required, and I don't really know what that is.
 
When logical arguments stop working, I'm out of tricks.
Well, not quite. I can always scream and yell and stubbornly repeat myself until the other person has been beaten into submission.
It's worked before with students. But not a great general-purpose strategy. :-)
 
Yes, I empathize. I tend to rely on logic myself for these things, and when that stops working, I'm basically at a loss. I can guarantee that kicking and screaming won't help in this case, but you know that already :)
 
Yup. All of that.
The fallback only works when you're in a position of authority.
This is another situation where I'm frustrated by my inability to just stop caring. :-)
 
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Why constant variables inside functions fail to compile in Solidity? by AriesCoder on ethereum.SE
[ SmokeDetector | MS ] Mostly punctuation marks in answer (36): C# ListView Column Width Auto by Nimesh Patel on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): ValueError: too many values to unpack (expected 3) when assigning rgb variables by Lavacat on stackoverflow.com
 
5:51 AM
fp feedback received
 
!!/bisect w+") else:
 
Matched by the following regexes:
(?:\\_?/\W*|w)+[\.\W]*(?:[eé3]+\W*(?:[s5]\W*[l1]\W*|[l1]\W*[s5]\W*)+[eé3]\W*.?|.*[a@]t?(?:\\_?/\W*|w)*\W*[0oøuüôöõ]{2}\W*d)+ on line 25389 of watched_keywords.txt
(?:it\W*(?:'?s|is))?\W*(?:\\_?/\W*|w)+[\.\W]*(?:[eé3_ëêẽ]+\W*(?:[s5]\W*[l1]\W*|[l1]\W*[s5]\W*)+[eé3_ëêẽ]\W*.?)\W*(?:.*[a@]t?(?:\\_?/\W*|w)*\W*[0oøuüôöõ]{2}\W*d)? on line 421 of blacklisted_usernames.txt
 
Huh. OK. That's over my head.
 
Are you on Teams? They'll explain it over there. You're not going to get an explanation here.
 
Yes, I am, but I wasn't really looking for an explanation.
It was more of a, "Well, if this needs to be looked at, I'll let someone else do the looking."
Like y'all did earlier with the "ban me" regex. :-)
@cigien Oh. Never mind. I get what you're saying.
 
5:54 AM
Cool.
 
Another case where we need to filter out code blocks.
 
[ SmokeDetector | MS ] Potentially bad keyword in body (1): AOS animate on scroll not working with FullpageJS by kishan on stackoverflow.com
 
fp- feedback received
 
Deja vu... that post looks very familiar after reading the SOCVR transcript.
And, another case where it would be very cool to have a "watched by SO moderators for moderation reasons" reason.
All of these questions should have been caught and handled by one of us slackers.
Yet, from SOCVR's perspective, evaluated in the abstract, they're all innocent-looking questions.
There's no obvious way to tell unless you're a moderator that they're part of a ring of question-ban evasion accounts.
 
6:10 AM
Who's the us here? Users who are active members of both SOCVR and Charcoal HQ?
 
tpu- feedback received
Makyen/EC2-num02: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev 63b113a (Makyen: This is the MS instance, so needs to post feedback) (running on Makyen/EC2-num02, Python 3.6.12)
 
tpu- feedback received
 
[ SmokeDetector | MS ] Bad keyword in answer (86): Windows Remote Control? by jhonjhoni on softwarerecs.SE
[ SmokeDetector | MS ] Url-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +5 more (829): jocosa-cbd-oil-25.webself.net/ by Jamaradams018 on askubuntu.com
 
6:23 AM
tpu- feedback received on [MS] Windows Remote Control?
tpu- feedback received
 
@CodyGray so should we change all of those to TP and blacklist the domain?
 
[ SmokeDetector | MS ] Potentially bad ns for domain in answer, potentially bad keyword in answer, username similar to website in answer (66): Modal width (increase) by infyseo on stackoverflow.com
 
tpu- feedback received
 
!!/watch infyseo\.com
 
6:26 AM
sdc watch-force jocosa[\W_]*+cbd[\W_]*+oil(?:[\W_]*+(?:\d++|[\da-f]{5,}+)s?)*
 
[ SmokeDetector ] Blacklists reloaded at rev 1664bde (SmokeDetector: Auto watch of infyseo\.com by tripleee) (running on teward/Osiris)
@cigien That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body; append -force if you really want to do that.
 
@cigien No, "us" == "SO mods"
 
@tripleee I'm not sure. Seems wrong. How would Charcoal members know this?
 
We can write a comment on each one
 
6:27 AM
Ack! More comments!
 
@CodyGray it's not a matter of "how could we know"; now that we do, should this content be blocked if we see more of it?
 
@tripleee Yes, I suppose so.
 
all of lamppost, or specifically arklan-dev?
 
That, I don't know.
Probably best to be surgically precise, if we're going to blacklist.
 
the oldest two have different user names; are they part of the same ring?
 
6:29 AM
All of those in this list are the same. All accounts have been removed.
 
[ SmokeDetector | MS ] Url in title, blacklisted website in body, body starts with title and ends in url, pattern-matching website in body, potentially bad ns for domain in body, +2 more (390): www.facebook.com/Aurora-Cream-Canada-103353781754546 by Atarczwershjd on puzzling.SE
 
tpu- feedback received
 
!!/blacklist-website lamppostmedia\.in
 
@CodyGray Then it's all TP. There's also no FP on SE, so we can blacklist it.
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title (193): What are some of the best colleges in India, apart from IIMs, offering an MBA/PGDM? by Cyriac Kurian on stackoverflow.com
 
@cigien I have added TP to all of the posts (looks like Makyen did too) but I have not cleared old feedbacks
I guess I can clear your FP @Cody?
 
tp feedback received
 
teward/Osiris: Executing automatic scheduled reboot.
 
@tripleee Yup, on it.
 
6:34 AM
@tripleee Was trying to figure out why I can't clear/change it from FIRE.
 
[ SmokeDetector ] SmokeDetector started at rev 787e921 (SmokeDetector: Auto blacklist of lamppostmedia\.in by tripleee) (running on teward/Osiris, Python 3.6.9)
 
@tripleee Cody gave new feedback, which auto-clears the old feedback.
 
all good then
 
Restart: API quota is 19156.
 
I hadn't at the time triplee pinged me.
 
6:35 AM
eee*
 
Eeeeeeek!
 
@CodyGray Nope, but you did later, which I waited for and saw come over the MS WebSocket. I'd seen the others you'd recently given, so I expected that one too. Once I saw that you'd given feedback, I posted a reply to @tripleee.
 
Am I missing something, or is it not possible to change your feedback using FIRE?
 
@CodyGray The stock version doesn't allow it. Yes, it should change. Yes, it's another change I need to push.
 
@Makyen There's still 2 FP on this one. Could you clear them please?
 
6:39 AM
@Makyen OK. You understand my confusion, though, right? Normally, I find that you've thought of everything, so I assumed I must just be missing it.
 
 
ouch!
 
Lol
 
you've suffered an eectomy
3
 
The debouncing circuitry built into my fingers is perhaps a bit aggressive.
 
6:42 AM
[ SmokeDetector | MS ] Link at beginning of answer (34): API for sun radiation / illuminance data? by Lockman on opendata.SE
 
@cigien No, no, I can't. :;
 
We will continue to probe the limits of your capabilities.
 
@Makyen Ah, must be a Ghost in MS then ;)
BTW, Would you actually prefer would instead? I'm happy to change that :)
 
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, pattern-matching product name in body, pattern-matching product name in title, potentially bad keyword in body, +1 more (393): MF Doom CBD Oil This CBD oil will empower the customer to dispose of constant sicknesses by TiaraHames on apple.SE
 
tpu- feedback received
 
6:50 AM
@cigien What is this? An open invitation to grammar pedants? Beware!
 
@CodyGray Beware? Of what? I'm very much a grammar pedant. Don't worry, I'll only do it on demand ;)
 
There's demand?
 
@CodyGray I understand, and agree. It was something which I found frustrating, so I just changed it. Unfortunately, when I wasn't permitted to merge the flagging via SE API code into FIRE, the version I use and the stock version ended up progressively diverging ... slightly :; (white is unchanged) over time. I've done some work to reintegrate the two versions, and need to release an update for the stock version, which will move them closer together.
There will likely be multiple releases progressively getting them closer together.
Unfortunately, there are also significant other changes to the overall repository that also need to happen part way through the process. Largely that's updating the versions of all the support/build software. However, that includes updating eslint, which results in needing to change some code formatting (primarily in FIRE and a bit in AIM, with the rest handled by changing build settings). So, overall, just a pain in the rear.
 
@Makyen Why would you not have been permitted to merge this?
 
6:53 AM
tpu- feedback received
 
sdc watch herlihyfamilylaw\.com
 
sdc watch-number- 2514327909
 
PR#5705 ("Yatin: Watch 2514327909") opened by SmokeDetector
PR#5706 ("Yatin: Watch 2514327909") opened by SmokeDetector
 
Ah
sdc watch-number- 2515897849
 
6:55 AM
PR#5707 ("Yatin: Watch 2515897849") opened by SmokeDetector
 
sdc reject 5705 "not watched as number"
 
@cigien Closed pull request #5705.
 
sdc approve 5706
 
sdc approve 5707
 
@Makyen Yes, I recently saw this question and could easily relate.
 
@Yatin You don't have to normalize the numbers yourself. Just paste whatever's in the markdown, and watch-number will handle it.
 
Oh cool
 
(also helps figure out why the number was watched in the first place via searches if left in the original format)
 
@CodyGray Ah that is so true
 
6:58 AM
@CodyGray The person who wrote the original version of FIRE doesn't like that in order to determine which ID number to use to raise a particular type of flag via the SE API you have to get the ID number, which might be different each and every time you flag, by matching a description of the flag in English, or the localized language for the site. They did not feel they wanted FIRE to take the responsibility for matching that text (which is invariant).
They wanted the SE API to be changed to just use invariant IDs for the various types of flags. My view was that an invariant ID would be good, but that's not the way it is, and it's not going to change any time soon.
 
@Makyen That's a reasonable position, except that, unless my understanding is incorrect, that decision is not up to the maintainer of FIRE or any other userscript, but rather foisted upon them by the SE developers.
 

« first day (2621 days earlier)      last day (1192 days later) »