« first day (3673 days earlier)      last day (442 days later) » 

10:10
[ SmokeDetector | MS ] Potentially bad ns for domain in body, potentially bad keyword in body (2): best google maps scraper‭ by AIMLEAP Outsource Bigdata‭ on superuser.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Image in article‭ by Md Omar Faruk‭ on english.SE
[ SmokeDetector | MS ] Link at end of answer (62): JMeter and optional SSL client certificate‭ by Fukasi‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): Error logging in to store with Shopify CLI ✏️‭ by Shourya‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, bad keyword in title, pattern-matching website in body, potentially bad keyword in body, +1 more (360): How can professional assignment writing services assist with programming assignments?‭ by rebel‭ on stackoverflow.com
10:40
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Accepted postdoc offer retracted last minute‭ by Oluwafemi Odunsi‭ on academia.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): Yii2 yii\data\ActiveDataFilter and pagination false‭ by user23064208‭ on stackoverflow.com
[ SmokeDetector | MS ] Offensive answer detected, potentially bad keyword in answer, toxic answer detected (159): Transparent proxy for SSH connection with VS Code in use‭ by Jury Schon‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer, username similar to website in answer (73): Teenage girl finds clothes that make her travel back in time‭ by Amoredo‭ on scifi.SE
[ SmokeDetector | MS ] Few unique characters in answer, repeating characters in answer (166): regular expression for Indian mobile numbers‭ by Abhishek‭ on stackoverflow.com
10:56
!!/watch- amoredo\.in
PR#9201 ("VLAZ: Watch amoredo\.in") opened by SmokeDetector
@VLAZ Thanks - I didn't check the links. I've changed my feedback to tp
sigh... 14 invalidated feedbacks now... :(
I didn't either...which might have made the check faster. I googled for parts of the answer. And found them that way. Then realised it's the link that was shared...
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer (1): What do you call the standing ads outside of a store?‭ by Jon Tabner‭ on ell.SE
[ SmokeDetector | MS ] Potentially bad asn for hostname in answer, potentially bad ns for domain in answer (2): What do you call the standing ads outside of a store?‭ by Evolution Print And Design Ltd‭ on ell.SE
@VLAZ I should have paid more attention given the user was blacklisted. ah well...
!!/watch- evolutionprintmanagement\.com
PR#9202 ("Nick: Watch evolutionprintmanagement\.com") opened by SmokeDetector
[ SmokeDetector | MS ] Bad keyword with email in body, potentially bad asn for hostname in body (57): Software App naming - Hackers‭ by GimmeGimme‭ on superuser.com
I was almost ready to click FP myself. I googled a couple of parts of the answer and got no hits. I tried a third one for a final check and got a hit.
11:04
!!/watch- printinlondon\.co\.uk
PR#9203 ("Nick: Watch printinlondon\.co\.uk") opened by SmokeDetector
@VLAZ third time's a charm! :)
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev ee0f84fecd (Makyen: Log as debug MS WebSocket messages) (running on Makyen/MS-Relay, Python 3.11.3)
11:14
!!/watch- coingabbar\.com
PR#9204 ("VLAZ: Watch coingabbar\.com") opened by SmokeDetector
[ SmokeDetector | MS ] Potentially bad ip for hostname in answer (1): How to get current queries to max_concurrent_queries ✏️‭ by Fehmi Can Aksakal‭ on stackoverflow.com
[ SmokeDetector | MS ] Few unique characters in answer, repeating words in answer (176): Verifying signed git commits?‭ by tyler rice‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, potentially bad keyword in body, potentially bad keyword in username (96): DevOps Course is the Key of Modern IT Professional‭ by WebAsha Technologies‭ on superuser.com
tp feedback received on [MS] test Selenium for labs‭
tp feedback received on [MS] Female Escorts near Wadsworth‭
11:49
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in username, blacklisted website in body, potentially bad ip for hostname in body, potentially bad keyword in body (282): What are the popular car hire options available in Bareilly?‭ by Chiku Cab‭ on superuser.com
[ SmokeDetector | MS ] Misleading link, potentially bad keyword in body (25): Burger's equation (PDE) does not work with downwind difference?‭ by blov‭ on scicomp.SE
[ SmokeDetector | MS ] Blacklisted website in body, link at beginning of body (141): Can Blockchain technology product gets more value compare to other Technology‭ by Suryanm‭ on ethereum.SE
[ SmokeDetector | MS ] Link at end of answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer, potentially bad keyword in answer, repeated url at end of long post, +1 more (235): How do I connect to Windows Virtual Server on the IBM Cloud‭ by Server LT‭ on superuser.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): How do I register NGRX provideEffects with Angular 17 standalone?‭ by Oleksii Yurchenko‭ on stackoverflow.com
[ SmokeDetector | MS ] Few unique characters in body, repeating words in body (135): Strange kind of talaq, please help and guide ✏️‭ by Islam Question‭ on islam.SE
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Visual Studio Code: The .NET Core SDK cannot be located‭ by Red Monkey‭ on stackoverflow.com
[ SmokeDetector | MS ] Blacklisted website in body, potentially bad ns for domain in body (99): IDK why my plugin css files showing in GSC as crawl currently no index?‭ by Rebecca Michael‭ on meta.SE (@Ollie @Ethan)
!!/watch akconsultants\.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): how to bypass cloudflare with python ✏️‭ by tommy.toolman‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, potentially bad keyword in body, potentially problematic ns configuration in body (294): How To Recover Your Lost And Stolen Bitcoin With The Help Of Muyern Trust Hacker‭ by walter natale‭ on scifi.SE
13:10
I think this is a spam campaign: stackoverflow.com/…
I first stumbled on one of the answers because it looked like ChatGPT, so yeah
@Laurel it's early, so ... are you suggesting that we watch Crawlbase? I don't yet see a URL in the first few posts.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in link text in body, potentially bad keyword in body (166): "Rent Pickup Dubai: Affordable and Reliable Pickup Truck Rentals"‭ by Trailorrental indubae‭ on stackoverflow.com
!!/watch rentpickupdubai\.com
@JeffSchaller It seems like a good idea to watch it. I think all the posts should be deleted as spam tho. You don't need a link to be spamming a product. Until 4 hours ago nobody ever mentioned this product and now there are some users who've mentioned it in all their answers
@Laurel I can add the watch; thanks!
!!/watch Crawlbase
!!/approve 9204
And how should I flag them? It's just kinda subtle spam
13:28
My first thought is a custom flag. My first ideas aren't always the best. How about a comment in each, asking about affiliation and/or applicability to the question? I haven't read the posts in detail to see, myself.
These posts can't be fixed because they're ChatGPT created with the intent to spam this product
Also one of them gave a "revised Lua script" to a question about scrapy (which is Python)
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (72): Scraping dynamic amazon page with scrolling‭ by Febona‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Golang Colly Scraping - Website Captcha Catches My Scrape‭ by Anna Breacher‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer, blacklisted user (72): Amazon URL scraping with XMLHTTP - Amazon blocking?‭ by Anna Breacher‭ on stackoverflow.com
13:44
FYI, Those "Crawlbase" posts were also brought to the attention of the vigilantes good folks of SOCVR.
I agree with others - they all looked like AI-generated fluff with much the same spam appendix.
@Laurel despite dealing with a lot of SO posts, and being a moderator elsewhere, I don't have a lot of opinions (particularly up-to-date ones) on handling spammy SO posts like that. Maybe Meta.SO? Or if you feel strongly enough that they're spam, simply spam-flag? (These opinions do not represent the CHQ project) :)
@AdrianMole ahhhh, I thought there was a room for things like that, but couldn't remember it.
Well, normally, when that sort of issue is raised in SOCVR, I gently direct the user to here. :)
At least one of the answers already got spam deleted. So I think spam flagging will work
There were 11 or so when first reported in SOCVR. Now only one left.
Note that there were several accounts that had multiple such posts.
@Laurel Feel free to swing the last hit of the hammer: stackoverflow.com/a/77626703/10871073
All gone!
!!/approve 9203
!!/approve 9202
!!/approve 9201
[ SmokeDetector | MS ] Repeating characters in body (57): SQL Sever query to add prefix along with identity feature‭ by Vijay Kandpal‭ on stackoverflow.com
!!/approve 9200
!!/approve 9199
!!/watch anticybercrimemoneyrecovery
@JeffSchaller That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer Append -force to the command word(s) if you really want to add the pattern you provided.
!!/approve 9154
14:11
@SmokeDetector whistles wow, ok! :)
!!/reject 9151 "based on my interpretation of the Guidance, this doesn't yet qualify for blacklisting"
@JeffSchaller Closed pull request #9151.
!!/approve 9150
!!/reject 9149 "based on my interpretation of the Guidance, this doesn't yet qualify for blacklisting; cc @Jesse"
!!/watch angulartool\.de
!!/reject 9149 "based on my interpretation of the Guidance, this doesn't yet qualify for blacklisting; cc @Jesse"
doesn't like it when I chat-ping within the message, huh?
!!/reject 9149 "based on my interpretation of the Guidance, this doesn't yet qualify for blacklisting"
@JeffSchaller Closed pull request #9149.
!!/reject 9148 "based on my interpretation of the Guidance, this doesn't yet qualify for blacklisting"
@JeffSchaller Closed pull request #9148.
!!/reject 9147 "based on my interpretation of the Guidance, this doesn't yet qualify for blacklisting"
!!/watch rokokbetlink\.tumblr\.com
14:25
@JeffSchaller Closed pull request #9147.
@Jesse I'm conflicted on PR 9145; the matching posts are FP in my opinion. I'm going to bypass it for now (leaving it open for someone else to decide on).
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, bad phone number in body, potentially bad keyword in body, potentially bad keyword in title (294): How To Hire A Professional Hacker/Daniel Meuli Web Recovery‭ by David Jakabovic‭ on academia.SE
!!/reject 9140 "a good watch, but fell victim to recency; matching PR 9155 was approved before I saw this one"
@JeffSchaller Closed pull request #9140.
Holy moly we're all caught up. Thanks, Jeff :D
!!/close 9145 "I agree with Jeff here, these posts all have disclosure (one of them is a bit dubious but this user has a bunch of posts and with only 4 of them having such a link, I think this is fine) thus there's no need for this watch IMO"
@Spevacus Closed pull request #9145.
[ SmokeDetector | MS ] Potentially bad keyword in body (1): how fo find How do I ask a good question?‭ by Offer ForTest‭ on stackoverflow.com
[ SmokeDetector | MS ] Bad phone number in body, potentially bad keyword in body, potentially bad keyword in title (102): HOW CAN I RECOVER MY MISSING CRYPTO/BITCOIN? OMEGA CRYPTO RECOVERY SPECIALIST‭ by Tom Bellingham‭ on english.SE
[ SmokeDetector | MS ] Link at beginning of body (43): Operating system network control data blocks‭ by Zelena‭ on unix.SE
Makyen/EC2-linux: Executing automatic scheduled reboot.
[ SmokeDetector | MS ] Potentially bad ns for domain in body, potentially bad keyword in body, potentially problematic ns configuration in body (3): How to remove image from starting of wordpress blog post?‭ by user78025‭ on wordpress.SE
!!/watch- hit1club\.win
15:25
PR#9205 ("Jesse: Watch hit1club\.win") opened by SmokeDetector
[ SmokeDetector | MS ] Bad keyword in answer, potentially bad keyword in answer, username similar to website in answer (160): Using Query Loop with Custom Post Type‭ by MY INFOTECH GROUP‭ on wordpress.SE
!!/approve 9205
!!/test 8615515395529
15:27
> Numbers-only title
----------
Numbers-only title - Position 0-13: 8615515395529
!!/watch-number- 8615515395529
@Jesse The pattern starts with whitespace. In order for a "number" to make an exact match, the pattern must begin with a digit or up to two of +,(,[, or { immediately followed by a digit. Append -force to the command word(s) if you really want to add the pattern you provided.
!!/watch-number- +8615515395529
PR#9206 ("Jesse: Watch +8615515395529") opened by SmokeDetector
!!/watch- bentengmachine\.com
15:28
PR#9207 ("Jesse: Watch bentengmachine\.com") opened by SmokeDetector
!!/watch- oilpresssite\.com
@SmokeDetector the leading space before the 8 tripped it up
PR#9208 ("Jesse: Watch oilpresssite\.com") opened by SmokeDetector
All of the above is from the image in this MS post.
@JeffSchaller Interesting. So it expected the number to come directly after the -?
I should have included the + sign to begin with anyway so it doesn't matter too much.
@Jesse I think so; I haven't looked at the code, but it must be pretty strict about parsing the commands
!!/approve 9206
!!/approve 9207
!!/approve 9208
!!/watch- unigap\.io
PR#9209 ("Jesse: Watch unigap\.io") opened by SmokeDetector
!!/approve 9209
!!/watch-force- toolhubquickbooks\.com
@Jesse That pattern looks like it's already caught by Blacklisted username Append -force to the command word(s) if you really want to add the pattern you provided.
[ SmokeDetector | MS ] Bad pattern in url answer, pattern-matching website in answer, potentially bad asn for hostname in answer, potentially bad ns for domain in answer (133): Are OneDrive preferences stored per PC or per account?‭ by Najmul602‭ on superuser.com
PR#9210 ("Jesse: Watch toolhubquickbooks\.com") opened by SmokeDetector
teward/Thoth: Executing automatic scheduled reboot.
Restart: API quota is 69828.
15:41
!!/watch- bestassingnments\.com
PR#9211 ("Jesse: Watch bestassingnments\.com") opened by SmokeDetector
!!/watch- muyerntrusthack\.solutions
@Jesse That pattern looks like it's already caught by Bad keyword in answer and Bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
!!/bisect muyerntrusthack.solutions
@Jesse Matched by muyern[\W_]*+trust\w*(?:[\W_]*+hack\w*)?(?:[\W_]*+(?:at[\W_]*+)?(?:mail-me|gmail)(?:[\W_]*+(?:dot[\W_]*+)?com)?)? on line 2902 of bad_keywords.txt
[ SmokeDetector | MS ] Link at beginning of answer (36): Is there any PDF Viewer in .NET MAUI App? ✏️‭ by Igor Risis‭ on stackoverflow.com
15:47
Would we watch-force here or just leave it at that do you think?
Can the user Vega (SO user ID 5468463) please be added as a privileged user for SOCVR (SO room ID 41570)?
I think another "watch" doesn't do a whole lot -- since they're already getting caught. More useful (IMHO) is waiting for or finding a pattern that gets enough hits for blacklisting; then there's more weight and potentially autoflags.
!!/approve 9210
Yeah true. I was just thinking we might want to promote the domain to the blacklist without promoting the pattern currently catching the domain, but I don't think that applies in this case.
15:50
@TylerH cc @Makyen
!!/approve 9211
@SmokeDetector What do you guys think of this one? It does disclose affiliation, but it still feels really spammy to me, maybe because of the "contact us" part.
!!/watch- najmulreview\.com
PR#9212 ("Jesse: Watch najmulreview\.com") opened by SmokeDetector
@cocomac Ah sweet! Nice to see some instance justice ;)
16:01
@cocomac From my understanding, it's completely fine for regular users to discuss suspensions, and I don't think Charcoal HQ has a standing policy against it. I think the common-sense addendum to that is "Don't be a jerk about it", as in, don't go wild making fun of the suspended person (not something I'd expect you to do, just mentioning).
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Unable to obtain driver for chrome using selenium manager‭ by johnv929‭ on stackoverflow.com
[ SmokeDetector | MS ] Linked punctuation in answer, potentially bad keyword in answer (77): multiplayer games using php empty file name? ✏️‭ by John Wick‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Leaving bike outside in -20 degrees‭ by Friendly Antitrαnny Bro‭ on bicycles.SE
16:59
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Ubuntu 22.04 HP laptop Irisxe graphics no HDMI signal‭ by chambeishon‭ on askubuntu.com
@SmokeDetector why
@ThomasWard Potentially bad keyword in body - Position 4578-4586: Innotech
@SmokeDetector f
Makyen/MS-Relay: Executing automatic scheduled reboot.
[ SmokeDetector ] SmokeDetector started at rev ee0f84fecd (Makyen: Log as debug MS WebSocket messages) (running on Makyen/MS-Relay, Python 3.11.3)
17:06
@ThomasWard Because this happened 3 months ago.
@Mast ack, but it's a false positive on that post so :P
!!/location
It is.
@cocomac User is not blacklisted (23064778 on stackoverflow.com).
@cocomac User blacklisted (23064778 on stackoverflow.com).
[ SmokeDetector | MS ] Potentially bad keyword in answer (1): Ethereum Contract auditing(solidity)‭ by John Patrick Oldfield‭ on ethereum.SE
!!/watch careerbuilderr\.com
> Would not be caught as a post, title or username.
@Jesse You don't have blacklist manager privileges, but I've created PR#9213 for you.
17:54
PR#9213 ("Jesse: Watch careerbuilderr\.com") opened by SmokeDetector
naa- feedback received on [MS] Ethereum Contract auditing(solidity)‭
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Equivalent Card Combinations for n-Cards ✏️‭ by fasutron‭ on math.SE
18:08
@SmokeDetector Would that be considered plagiarism, as the author did quote the website, but didn't add any other info?
@Fastnlight Probably not. I think it just needs a quote block. Plagiarism is when you take something someone else wrote and try to pass it off as your own. Considering they included the link, I don't think that's their intention here.
👍🏻
I have no idea whether we can report a collective...
@Mast Post 1: That does not look like a valid post URL.
Well, now we know.
This looks like spam (note that the one question link redirects for anon users; I think it's a question marked as a duplicate): stackexchange.com/search?q=Url%3Awebtoolapps.com
Here's a noredirect link for that, not sure it's quite so bad as the answers, which look to be AI: networkengineering.stackexchange.com/questions/84380/…
Feature request to red flag discussions (by me):
0
Q: Can we please red flag discussions?

FastnlightCurrently, we can flag discussions, which (I assume) brings it up to the moderators. However, with other posts, we can spam and r/a flag posts to automatically bring them down. Why can't we do that with discussions. Now, spammers are realizing that discussions is a way to keep spam up for longer ...

18:58
[ SmokeDetector | MS ] Link at beginning of answer (36): Netbeans: C/C++ file-template variables documentation needed‭ by Dâmaso‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body, potentially bad ip for hostname in body (2): New Custom Error element in Record Triggered Flows Does Not Stop Processing and Does Not Show Error Message‭ by dan alden‭ on salesforce.SE
[ SmokeDetector | MS ] Potentially bad ns for domain in answer (1): No serenity report in gradle multi module project‭ by Thiago Nascimento Figueiredo‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad keyword in body (1): Visual Studio Code: The .NET Core SDK cannot be located ✏️‭ by Red Monkey‭ on stackoverflow.com
[ SmokeDetector | MS ] Potentially bad asn for hostname in body (1): Is it possible (and how) to extract highlighted text from a PDF (via API)?‭ by Tim‭ on stackoverflow.com
19:18
@Fastnlight This comment isn't exactly incorrect in that SD monitors posts, but we also don't need to advertise the existence of the bot, especially if that user isn't posting in good faith.
I'll remove the comments as they aren't needed
[ SmokeDetector | MS ] Potentially bad keyword in username (1): i need a recursive programm that finds the sum from 1 to N=10‭ by nikola KYS‭ on stackoverflow.com
@Fastnlight Sounds good, thanks!
19:33
@Fastnlight Thanks for posting that.
@Fastnlight Moderating those is in the hands of the CMs. I don't know if CMs are notified of the flags in some manner or if it's entirely polled (i.e., that they have to go to each discussion to check). Flags on them are not handled very quickly. It's not possible for more than one flag to be raised on a discussion and they can't be deleted via flags, so telling other users about their existence isn't effective. Feel free to use the Contact Us link to report them (personal opinion, not policy).
Moderators can delete them, but we don't know about those flags unless we go to each discussion. Given the current state of the system (i.e., that SE chose to design it as obviously broken from a moderation standpoint, leaving an very clear path for spam and R/A content, without the system-normal methods for basic user-level moderation), I am not enthusiastic about having users telling moderators about cases where there is spam or R/A content there.
I would much rather that you create a ticket for each such post in discussions via "Contact Us", so there's a record in SE's tracking system showing how much work is having to be done due to their choice to not minimally flesh out the moderation of that feature.
In other words, reporting them here is near-useless, because only SO moderators and CMs can do anything about those discussions. You're welcome to create watches for SD for the contents of such discussions, in case the spammer posts something similar in a post on SE.
Is there an outstanding request for an API endpoint (and websocket?) for Collectives Articles & Discussions? I know the old Articles endpoint doesn't work anymore by design. If not, I'll post one later today, either on MSE, MSO, or StackApps
I don't recall seeing one, other than in the responses to the initial announcement of the Discussions feature.
Ok, I'll post one later today or tomorrow then.
@Makyen Given the fact that there are SO moderators in this chat room (you for example), I don't see it hurting to post in in here. In addition, it allows members to blacklist the user, and extract content to watch/blacklist
19:38
@Fastnlight It hurts because then there's less incentive for them to actually fix their (!@&#.
I doubt they'll fix it either way...
But it's good to have an FR on it, pointing out (again) how broken it is.
If we'll just ignore it as a project, everyone else is going to see how bad it is soon enough.
After all, people noticed what happened during the strike.
@Makyen I realize posting them in hopes of deletion is questionable, and I won't if you don't want me too. Still, when I blacklist someone for posting Discussions spam, I have been leaving a chat message here noting that my rationale for the blacklist is the spam post, and that typically includes a link to said Discussions post. Is that OK, or would you rather we not do that too? I lean toward doing it, but I don't have a strong opinion either way.
@cocomac I'd say that's good for having the paper trail on the watch.
Making a watch is not the same as pinging a mod about it.
@cocomac That's fine, although I'd prefer if you also reported each via the "Contact Us" link, given that flagging a discussion really isn't effective.
19:43
@Makyen So post a link in here, flag, and contact the team (via contact us)?
Ok, I'd still like to flag regardless, but I can blacklist them, note the post leading to the blacklist, raise a flag, and then use Contact Us so staff can remove it.
@Fastnlight Contact Us contacts the Team, not the mods.
Team is staff, mods are volunteers.
@Fastnlight Yes.
If someone (preferably a SO mod) wants to post it on my meta post, we can make sure others know how to report those in the current condition of discussions
19:46
@cocomac Yes, please flag, but don't ask others to do so, because they can't, as only one flag on each discussion is permitted (in total across all users, or at least at a time).
Every time I'm reminded of that tidbit, I'm reminded of how ridiculous it is.
flips table
@Spevacus (╯°□°)╯︵ ┻━┻
(╯°□°)╯︵ ┻━┻
Dang, you beat me
┬─┬ノ( º _ ºノ) lets put it back now
19:51
@Makyen What?! I see why we don't like that functionality…
Just found a user that pretty accurately describes the CM team after adding discussions: stackoverflow.com/users/23067953/stackoverwhelmed
@cocomac On, wait. I'm wrong. It looks like they fixed that issue last month: "Some discussions don't have a flag link". So, other users can flag, but it doesn't actually do anything.

« first day (3673 days earlier)      last day (442 days later) »