« first day (3304 days earlier)      last day (1703 days later) » 
01:00 - 19:0019:00 - 00:00

7:15 PM
A flag of mine was declined with the reason "flags should not be used to indicate technical inaccuracies, or an altogether wrong answer", but that's not at all what I flagged it for.
Should I re-flag or is there some issue which causes the wrong template to be used?
 
@forest An issue called a misclick, maybe.
 
hm
 
But the decline was more than a click away so probably not a misclick
 
It was a flag for meta.stackexchange.com/questions/332229/… to add the featured tag, as it is an official response to a featured question that is getting hidden due to downvotes. Others have suggested that it get flagged for the featured flag for that reason. I'd understand if it was declined because staff want to hide it so less people are aware of what's happening, but I can't imagine why it would be declined for "pointing out inaccuracies".
 
I'm pretty sure that doesn't get featured so I won't bother. That was already tried in comments IIRC.
 
7:22 PM
sigh
It's so frustrating seeing two staff saying opposite things.
One saying that this tracking ad is absolutely not acceptable, and the other saying it's fine.
 
Nah
 
Yah. It is frustrating.
 
Nah
 
what two different things were said?
 
See my link in that answer.
 
7:24 PM
that's what i thought
and i wholly disagree that this is an example of two staff members saying two entirely different things
 
Juan M said that user tracking/fingerprinting is acceptable because [insert misunderstood terms of service from ad company here]. Nick Craver, on the other hand, said that it is a major problem and that they will work to fix this, and that it tracking is not OK. They are talking about the same things.
 
Clearly, nick was still in the investigative mode on this topic. Now that they know what's going on, their stance on it has changed. Nothing wrong with that?
 
@KevinB If you'd read the posts, you'd see that isn't the case.
 
I did read them.
 
So you know that they don't know what's going on then.
Good.
 
7:26 PM
They didn't, in the first post. They do now in the newer one.
 
So I see you didn't read them.
Please read Olivia's post.
 
@forest TBH from my shallow understanding they do know or assume what's going on but the legal headache is probably not worth it and the latter post is a dismissal.
I usually assume my opposite is an intelligent human being. s. Human beings.
 
@M.A.R. I think they assume they know what's going on, but I agree that most likely, someone higher up has overridden Nick's goal of removing malvertising.
Especially since I've noticed that they've started ignoring other malicious tactics like redirect hijacking.
 
Ok, i read olivia's post again. what about it?
 
@KevinB So you see where Juan M is incorrect then.
 
7:30 PM
incorrect?
how?
 
Do you need to re-read Olivia's post again?
She points it out very clearly.
 
All i see are assumptions
 
No, you see references to official corporate policies.
I don't see how reporting the text from a terms of service is an "assumption".
But it doesn't seem like you're trying to pursue this in good faith, so I'm not going to continue.
 
đź‘Ť
 
404
@forest Depends on their department. SREs or Marketing.
I count Juan M among the latter.
 
7:37 PM
I'm of the opinion that I simply dont care if i'm being tracked, what's being tracked, etc. it's of no interest to me.
 
404
Also, this happened before.
28
Q: Quantcast http://pixel.quantserve.com/pixel request 302 redirects to Facebook and other ad networks

Greg BrayI just spent a few hours investigating what I thought might be a malicious Chrome extension (using developer tool to audit them, highly recommended!), an ISP/DNS injection issue, or a malware infection, but best I can tell this is occurring as a legitimate response from Quancast's pixel servers. ...

Greg and/or Nick Craver posted a bunch of angry things on Twitter about this outrageous behavior.
Then they found out from legal/ads/etc that this is perfectly normal, for the current value of normal.
 
Don't want to be targeted by ads? don't be. :shrug:
 
7:57 PM
@forest if folks who work here want to feature something, they will
@KevinB adblock alllll the things
 
Now if only we could adblock billboards...
 
8:24 PM
@KevinB hmm. All you need is ai and lcd sunglasses ;p
 
404
Blog comments are great.
When a comment is written by a user "Jon Skeet", do we assume it's the Jon Skeet we think of, or an impersonator?
 
404
8:47 PM
How to survive 12 hours in an airport. Depending on an airport, it can be less of survival and more of fun.
> Consuming vodka and clam chowder at 6 a.m. on a Wednesday isn’t behavior normally condoned by the general public. But tell people that you’re having an early morning bloody mary and a snack at the airport, and no one bats an eye.
I'm still bitter about being refused beer at JFK around 9am on Sunday.
 
9:14 PM
@404 You can sometimes tell if the writing is too different from that of an uninterested history professor
He's at least like that on meta.SO
 
9:37 PM
tl;dr stylometry
 
9:48 PM
@404 When I was booking my trip to India, one of the options was a 15-hour layover in London Heathrow. It was annoying that the flight to Mumbai would leave 15 minutes before the one arriving from Austin...
I ended up booking via Frankfurt instead.
But yes, I have spent 7 hours in London Heathrow. It was fine.
And 5 hours inside the Austin airport.
 
> Thanks for voting<br>
Looks like the voting message is bugged.
I got that when voting for a mod election on Law.SE.
 
[earns 150 rep on Law to test]
 
This is how it is sent (according to a pcap):
> You have cast your third vote, thanks for voting!&lt;br/&gt;You can still change your votes until the election ends.
So it renders as a literal <br>
Probably because of a typo. It's <br/> for some reason instead of </br>.
 
@forest No, <br> is an empty element. It's either just <br> or <br />.
The latter form exists for overzealous validators that don't properly recognize the fact that a closing element isn't necessary for that.
 
ah
Well no one ever paid me for my knowledge of HTML. :P
 
404
10:05 PM
Self-closing XHTML nonsense is also responsible for this
1324
Q: RegEx match open tags except XHTML self-contained tags

JeffI need to match all of these opening tags: <p> <a href="foo"> But not these: <br /> <hr class="foo" /> I came up with this and wanted to make sure I've got it right. I am only capturing the a-z. <([a-z]+) *[^/]*?> I believe it says: Find a less-than, then Find (and capture) a-z one or ...

The answer looks a bit... unwelcoming?
 
@404 That's a famous answer here.
> This post is locked to prevent inappropriate edits to its content. The post looks exactly as it is supposed to look - there are no problems with its content. Please do not flag it for our attention.
See that.
 
404
Maybe the "thanks for voting" popup is also parsed with regex.
 
11:06 PM
NullPointerException meta.stackexchange.com/questions/332525/… @Bart @rene @Glorfindel
 
That code is horrifying.
 
Meh didn't bother to look
 
01:00 - 19:0019:00 - 00:00

« first day (3304 days earlier)      last day (1703 days later) »