Petition To Move Off Latest
-
-
because i don't find short skitrs as sexy as dresses.
but not all skirts are short. My wife has skirts in a wide variety of lengths. All the way from mid-thigh to dragging-the-floor.
-
because i don't find short skitrs as sexy as dresses.
Not a legwomanfox?
Discoquoting broke *exactly* one `>`...
-
-
but not all skirts are short. My wife has skirts in a wide variety of lengths. All the way from mid-thigh to dragging-the-floor.
true, but the default length in these parts appears to be "mini"
-
interesting ...
wearing them traditional stile bumps kilts up to above regular pants. ;-)
-
-
wearing them traditional stile bumps kilts up to above regular pants.
Not sure I'm up for that much of a draft.
-
wearing them traditional stile bumps kilts up to above regular pants. ;-)
So long as they avoid dandruff on the shoes...
-
-
-
BeLgIuM
well that isn't case sensitive.....
belgium
html entity escaping works though.
-
Y'know, I've never actually tested the censoring; I've never had the need to type the word 'Belgium'...
Wait, a Discourse feature that actually works‽
-
i like to break things in a constructive manner. ;-)
-
I agree with what @PJH said... the bugs uncovered here would have been infeasible to find during testing, so we may as well get the bugs and bug fixes sooner.
-
Something that has been pointed out as well: Why do we have to be the only ones finding the bugs? Why are we giving free labor to Jeff & Co. Let other forums feel some of the pain that we've been getting. It's not like we're really getting anything for our trouble. If CDCK wants to push out untested software, let them. Personally, I am tired of being their safety net. There are numerous things we have suggested to improve their development team environment, mostly in civil tones, and all of them have been shot down. Most of those suggestions would reduce the rate of bug generation and regression.
-
Oddly my employer prefers that we wear leg coverings (for me, pants. My claymore is at the smithy for maintenance.)
I have a friend who would read that rule and come in the next day wearing chaps. His employer recently upgraded their dress code standards and due to some ambiguity in the way they were written, he wore a kilt to work for 2-3 days until they updated the rules.
Imagine that for a moment, he went to work wearing a button-up, long-sleeve dress shirt, dress socks, dress shoes...and a kilt.
And yes, he is in QA, so he spends his days finding edge cases and loopholes in business logic to exploit.
-
@Intercourse said:
And yes, he is in QA, so he spends his days finding edge cases and loopholes in business logic to exploit.
Sounds like he knows what he's doing
-
@Intercourse said:
Imagine that for a moment, he went to work wearing a button-up, long-sleeve dress shirt, dress socks, dress shoes...and a kilt.
As long as it's not a mini-kilt, I see no problem with that.
-
Sounds like he knows what he's doing
All kidding aside, he is the best QA person I have ever met. He thinks of things we never would. When I get to the point of needing a dedicated QA person, he is the only person on the list.
-
3. Test
4. This
5. Shit
6. AgainI'm starting to think I was insane. Maybe that bug was never fixed. Maybe I was just high on crack cocaine.
Discourse noticed you deleted "1. We" and "2. Won't", and fixed your list numbering for you. It always has, and was never "fixed". Hell, until very recently it was considered expected behavior.
I can post in what.tdwtf/bugs for you that "Discourse doesn't implement CommonMark", if you like. I can't post on meta.d due to lacking an account and problems with account creation.
Filed under: [insert insincere apologies for inconvenience and lackluster appreciation for patience here], we need a new tag cloud to attack
-
I can post in what.tdwtf/bugs for you that "Discourse doesn't implement CommonMark", if you like. I can't post on meta.d due to lacking an account and problems with account creation.
post it here and i'll duplicate it on meta.d for you .
-
post it here and i'll duplicate it on meta.d for you .
Why? They already know that they don't implement CommonMark. They already know about the issue with the numbering. They've already said they plan to fix it.
-
because...
yeah that's it really. because.
-
A link would be appreciated since DiscoSearch...
-
A link would be appreciated since DiscoSearch...
CBA because discosearch and work ...
-
-
They've already said they plan to fix it.
Am I crazy?
They did fix it. For a period of like 1 week. Then they instantly regressed back.
-
post it here and i'll duplicate it on meta.d for you .
Let me know how that works out for you.
https://meta.discourse.org/t/ordered-list-numbering-wrong/19619?u=boomzilla
-
Let me know how that works out for you.
yep. that's why i'm not writing the copy in the first place. i'll happy cut/paste though.
-
Am I crazy?
They did fix it. For a period of like 1 week. Then they instantly regressed back.
I'm not disputing that. I'm just saying that they have said they plan to adopt CommonMark, which would also fix the numbering issue that's driving a stick up your ass.
-
they plan to adopt CommonMark
do they plan to drop the htmlbbcodemarkdownlike mess they have in favour of common mark or just wedge it in there as commonhtmlbbcodemark?
-
I love the final post in that topic.
-
I still don't think you get it.
THEY FIXED THAT BUG. It stayed fixed for a week or two. Then it regressed and has been broken ever since.
That's separate from any "CommonMark" adoption plan or whatever. Yes CommonMark would fix it also, but the point is it's the most amazing regression I've ever come across.
-
do they plan
Not really.
THEY FIXED THAT BUG. It stayed fixed for a week or two. Then it regressed and has been broken ever since.
Yes, that's what I remember, too.
-
Not really.
yeah.
nice choice on where to snip my comment for that quote BTW. doesn't even affect accuracy!
-
do they plan to drop the htmlbbcodemarkdownlike mess they have in favour of common mark or just wedge it in there as commonhtmlbbcodemark?
Preferably the former. Probably the latter.
-
I still don't think you get it.
THEY FIXED THAT BUG. It stayed fixed for a week or two. Then it regressed and has been broken ever since.
*cough*
I'm not disputing that.
Yes they fixed it. Yes it regressed. That's why it needs to be fixed now.
-
Yes, that's what I remember, too.
Thank God, I thought I was going crazy and I was dreading trying to attempt to use search on this awful site to verify my memory.
Yes they fixed it. Yes it regressed. That's why it needs to be fixed now.
There's like 10 posts in here writing as if it were never fixed in the first place, those were throwing me.
-
Yes they fixed it. Yes it regressed. That's why it needs to be fixed now.
I'm just ignoring the fact that it was previously fixed because it is irrelevant to the fact that it is currently broken.
-
There's like 10 posts in here writing as if it were never fixed in the first place, those were throwing me.
Let's be honest. The "fix" was probably a side effect of some other bug that eventually got fixed.
-
Discourse: Where bugs fix other bugs.
-
-
-
jeans as a leg covering are a broad spectrum. ;-)
And jorts are a totally different thing...
-
And jorts are a totally different thing...
jorts deserver to be doused in napalm and then set afire.
after having been removed from their wearer. seriously. it's less embarrassing to wear your knickers in public than it is to wear jorts.
-
jorts deserver to be doused in napalm and then set afire.
after having been removed from their wearer. seriously. it's less embarrassing to wear your knickers in public than it is to wear jorts.
GIS for "fox jorts" was disappointing.
-
I wish there were some SQL query that @PJH could run that could classify posts on here based upon whether or not they are about Discourse bugs or just bitching about Discourse because it seems like the past week or so has been predominately just Discobashing.
Yes, I realize that such a thing is not really possible and if it were it would take until the heat death of the universe for it to run, but a man can dream.
-
@Intercourse said:
I wish there were some SQL query that @PJH could run that could classify posts on here based upon whether or not they are about Discourse bugs or just bitching about Discourse because it seems like the past week or so has been predominately just Discobashing.
Yes, I realize that such a thing is not really possible and if it were it would take until the heat death of the universe for it to run, but a man can dream.
Since the constant topic is Discobashing, it's no surprise that @error couldn't keep up with the new posts...
-
Since the constant topic is Discobashing, it's no surprise that @error couldn't keep up with the new posts...
His little backend was smoking from all the flogging due to the constant bugs. <just wanted to set someone up for a dirty joke>