@WELZ If you compare the total views on the question responses page to the total number of votes, it's usually significantly lower - and it's worth noting that the views aren't unique to users, so if the question responses has 1200 views, that's likely going to include a lot of views from the same people. I've seen candidates who don't answer questions win and candidates who answer them poorly... most of the time, people vote based on candidate score or reputation.
I just went to check out the Top Users Page and was greeted by a nearly empty (of profile pics) page (nearly becasue a few do show up - and it's always the same few)
I just tried this on Chrome, Firefox and Microsoft Edge.
Why is this happening?
In the Stack Exchange - Top Users tab, for most of the sites there is no top user displayed.
I didn't see any error or warning in the browser's console and network tabs.
GIF for the same:
Configuration:
OS: Windows 7
Mozilla Firefox : 59.0b5 (64-bit)
Google Chrome: Version 63.0.3239.132...
@AJ Still? Again? I haven't been seeing timeouts. OTOH, I haven't been loading a lot of reports. However, I do see that AIM has failed to load on a couple/few SD reports.
[ SmokeDetector | MS ] URL-only title, blacklisted website in body, blacklisted website in title, link at end of body: musicpleer.zone/ by gyandevil on askubuntu.com
[ SmokeDetector | MS ] Bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, +2 more: supplementschoice.com/proflexoral/ by user275243 on apple.SE
@iBug @AJ It appears to be on the metasmoke side. I'm (now) seeing timeouts on the AJAX requests to the metasmoke API on multiple attempts to load FIRE popups.
@AJ If the image is being shown, then you can hide the images: Go to the FIRE configuration page and select "Hide images in reported messages." @iBug However, given how it's coded in FIRE, I would expect that your browser does actually download the image, even when it's not displayed. I'd already been looking at re-coding that portion of FIRE to address both a display corruption issue (with maybe also a potential security issue) and the the image loading issue.
However, unless you've actually been looking at the network performance graph/tab in DevTools, that's probably not what is causing the delays which you are likely experiencing with the FIRE popup displaying. Those are caused by the requests to the metasmoke APIs taking a long time, and in multiple cases, timing-out.
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, pattern-matching website in body: Booty Pop -Review by herbemayn on meta.SE (@iBug @TetsuyaYamamoto)
@iBug I'd kind-of assumed that we get there eventually. But does it really make sense to send that notice once for every domain? Does it make sense to send it (with that wording) after having received a (moderately) significant quantity of feedback from the user? [NOTE: This is, obviously, a low priority. I'm mostly just playing this up for effect.]
[ SmokeDetector | MS ] URL in title, blacklisted website in body, blacklisted website in title, pattern-matching website in body, pattern-matching website in title: alphajackedhelp.com/lyaxtin/ by Reshmai on graphicdesign.SE
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +3 more: lumalifteye.com/verona-serum/ by tlmlxykvap on meta.SE (@iBug @TetsuyaYamamoto)
@iBug I didn't mean to drive you to drink :-). Frankly, it seems to be just a (very) minor misfeature/bug. I'd rather developers spend time on other things. An extra message in chat from time to time isn't a big deal.
@Makyen Looks to me like chat_user_id is only populated if the feedback actually comes from chat. So the message prints if Metasmoke has never received feedback from this user and chat server
@iBug It fits what I was meaning by from time to time (i.e. only once each time a user first uses a different room or domain). Which, from a certain point of view, is from time to time :-).
@NobodyNada That sounds like it matches what we've observed. Someday, someone might want to to change it. But, meh. I wouldn't put out a lot of effort to resolve it. I do appreciate your tracking it down (and @iBug working on explaining it). I'm sorry if my exercise in hyperbole has resulted in either of you feeling it needs to change.
@Makyen No worries, it's not a big deal at all. (I think the only thing that needs to change is for this to query by Metasmoke ID and fallback to chat user ID, though).
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, link at end of body, pattern-matching website in body: Nutralu garcinia by careisewe on meta.SE (@iBug @TetsuyaYamamoto)
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, bad keyword in title, +5 more: healthflyup.com/tryvexan-za/ by zswu on askubuntu.com
@Cerbrus What you quoted was very close to what is seen when FIRE sends "deleted" messages to metasmoke, which are only sent if AIM is also installed. @ArtOfCode and I discussed it a while back. Basically, the timing on the reports from FIRE was too inaccurate, and the receipt of them disabled by not trusting that API key for those reports. There is no desire for FIRE to send them, unless, for some other reason, FIRE starts listening to the SE websocket for each post.
[ SmokeDetector | MS ] URL in title, bad keyword in body, potentially bad keyword in body, potentially bad keyword in title, repeated URL at end of long post: mp3converter.zone by Bjtzsloi on graphicdesign.SE
[ SmokeDetector | MS ] Bad NS for domain in body, bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, +1 more: This fixing is viable against by Kated19 Virk on superuser.com (@TetsuyaYamamoto)