« first day (3819 days earlier)      last day (43 days later) » 

Rob
12:09 AM
@DavidPostill The Pun Misser, there's no truck with the steer it's a p ass engineer of the poo lease vehicle. It both gives one and rides for free.
 
Rob
12:21 AM
While conditions are not sanitary, it doesn't ride steerage.
 
 
2 hours later…
2:05 AM
578
Q: We're switching to CommonMark

Ham VockeI’m Ham and I’m a developer on the Teams team here at Stack Overflow. Over the past few months, I’ve been heads down working on the way we turn Markdown into HTML when writing and editing posts across the network. I’d love to share what I’ve come up with. In a nutshell: We're planning to use Comm...

In June of last year, SE changed from their proprietary Markdown dialect to CommonMark, and CommonMark requires a space after the # sign(s) for something to render as a header.
When they transitioned, they built a program that would convert posts to CommonMark, but that script was extremely basic and only accounted for the common differences (e.g. headings, quotes, etc.) and didn't account for more nuanced differences.
 
@SonictheCuriouserHedgehog So why were the headers working perfectly until I made an unrelated edit to my post (changing http to https)?
 
Let me explain:
So at that time, posts fell into three buckets, with the cached HTML from the time the post was last rendered, and the new HTML rendered using the original Markdown and the new CommonMark renderer, either: 1. matching perfectly (usually posts that had no formatting at all), 2. not matching perfectly but could be edited by said automatic script to match perfectly, or 3. not matching perfectly and the output from said automatic script didn't match perfectly either.
 
Posts in bucket 1 were retained as is, as there was nothing to do with them. Bucket 2 posts were edited by said script and re-rendered accordingly. Your post fell into bucket 3.
 
So my post was using HTML that was generated back in the Markdown era, and when I edited it, it was re-generated with CommonMark, which resulted in a slightly different unexpected output?
 
2:13 AM
Precisely.
 
As the script only accounted for the most common differences, posts that contained less common differences, no matter how minor, wouldn't be edited as the script output wouldn't be a perfect match with the original cached HTML.
Here's an answer where I explain this in more detail.
In my opinion, adopting CommonMark was a good thing, since it prevents ambiguities like this.
 
 
1 hour later…
3:35 AM
Ah, I see it was an actual bot that did it.
@SonictheCuriouserHedgehog It seems like the bot converted ##foo into ## foo but it did not convert #foo into # foo, which seems like a bug/oversight.
 
@TheforestofReinstateMonica No, the post that wasn't converted must have had something else mismatch the CommonMark rendering. The bot (script I mentioned above) only edited posts if its HTML output exactly matched the previous cached rendering; if it didn't in any way, it left it alone.
> This rule was common enough to be included in the migration script, though. But, as your post wasn't automatically edited, what happened here is that there must have been something else that wasn't compliant that caused the automated script to back out.
Typically, the most common thing I see in such posts is sub-bullet or sub-number formatting: previously, only one preceding space was required, now two are required, but this rule wasn't common enough to be included in the script.
So posts that formerly used a single space to produce sub-bullets, and also used headings without spaces wouldn't be edited at all, since all the script did was fix the heading, and even with just those fixed, the new HTML wouldn't be a perfect match with the cached rendering.
 
So it didn't just edit what it could and leave the rest alone?
And bailed totally if it couldn't edit it all?
 
 
3 hours later…
7:09 AM
@TheforestofReinstateMonica yes
 
7:25 AM
@rene right
 
 
4 hours later…
11:54 AM
20 messages moved to Chimney
 
12:46 PM
MODS, I just noticed I don't have a "positive question record" can someone please tell me how many deleted questions I have? (And how many of the deleted Q's were negative/closed)?
 
1:04 PM
@bad_coder I assume this is on MSE regarding your Curious badge? You might be able to see some of your deleted 60-days old questions on meta.stackexchange.com/users/recently-deleted-questions/665544
 
1:27 PM
@MetaAndrewT. thanks but it didn't work, if had a deleted questions that were only 60 days old I would likely remember. I don't like bothering the mods, but there's no other way to be certain other than asking or having 10k...
 
@bad_coder mods are asleep after long week. ;)
 
 
1 hour later…
3:00 PM
!!/thank me
 
@TechExpertWizard No such command 'thank'.
 
3:40 PM
@bad_coder Your only deleted question is meta.stackexchange.com/questions/347179/… ... The one blocking your 'positive record' is probably the one closed as a duplicate: meta.stackexchange.com/questions/355270/…
 
Rob
3:54 PM
This search query should show: Newest sort order, deleted, with a Score between -100 and 0 - I can see well past 60 days, you should be able to see your own deleted Q&As too (regardless of your reputation).
Add is:question to see only questions.
 
4:08 PM
@Rob that's 10k-rep privilege though.
 
Rob
5:05 PM
Yes, 60 day limit otherwise; they also wanted to filter by score.
-100 should be enough, a couple more zeros for mods and staff.
 
6:05 PM
@Tinkeringbell yes that is it, 2 more questions for the badge (this isn't easy...) Thank you.
 
@bad_coder In my experience, those kinds of things go best/fastest when you're not even trying.
 
 
1 hour later…
7:20 PM
@Tinkeringbell that was the case for me on SO, got Unsung Hero out of the blue without even understanding what those badges are. Getting gold badge without even trying felt good.
Same in early winter bashes, I didn't hunt for hats too much (just some basics) and got several secret hats that turned out to be quite hard to get. :D
I think the hardest was Red Baron.
But meh, times change.
Coffee doesn't. That's a solid rock of stability in a world of changes. ;)
!!/coffee The
 
@ShadowWizardisVaccinating brews a cup of Latte for @The
 
XD Even coffee changes... whenever people get new machines ;)
 
@Tinkeringbell nah, maybe just the taste... but idea is the same: magic liquid that keeps you awake. :P
 
@ShadowWizardisVaccinating The caffeine is what keeps people awake... not magic or liquid :P
 
@Tech why you not lurking here anymore?
 
7:25 PM
Ah come on, I was enjoying the peace and quiet!
 
Noise.
 
@Tinkeringbell well, in other drinks e.g. Cola there isn't enough, and if taken in pills or pure form it's just not tasty, to say the least.... ;)
 
@Alex Your noise is tolerable, it only comes... what, once a month these days? :D
@ShadowWizardisVaccinating That's because you've built up a tolerance already.
 
@Tinkeringbell once a month.... noise.... hmm....
I prefer @M.A.R.'s nose.
 
@Tinkeringbell Not even. It's been a few months at least, I think.
 
7:26 PM
That's bad. Shame on you :P
 
Our ninja is nearly done.
 
My previous comment in this room was in August.
 
Aug 23 '20 at 19:04, by Alex
Most sites don't even get 22.8 questions per day.
Tru.e.
@Alex so what caused you to break the long silence? ;)
 
I guess need to get out more often.
@ShadowWizardisVaccinating Fear of losing my vocal chords entirely.
 
7:28 PM
lol
Shamla! Going to watch.
 
@Alex But not right now :P Going out is dangerous these days ;)
 
Dang, it's not now, only in Saturday. :(
 
@Tinkeringbell Back into my cave, then.
Did I at least miss anything exciting?
 
Not really, I think.... Winter bash?
You have your own cave? That's nice!
 
Yeah, I got some hats on a few sites.
 
7:32 PM
I don't think there was much else exciting things on here since August.
At least not stuff that wasn't also featured networkwide
 
Oh well.
 
7:45 PM
@ShadowWizardisVaccinating 'Cause there's no use in lurking around here if I've got nothing to talk here.
@ShadowWizardisVaccinating But I'm gonna lurk around here in case you need me to lurk around here 😉
 
8:40 PM
Interesting: question closed notifications don't appear in the app, and when you view your notifications in the app it clears the notifications from the website as well, in which case you won't see the question closed notification at all.
 
 
3 hours later…
Rob
11:16 PM
😈🔨
 

« first day (3819 days earlier)      last day (43 days later) »