Petition To Move Off Latest
-
after having been removed from their wearer.
Not so sure this step is necessary. Anyone willing to wear jorts has something wrong with them and should probably be removed from the gene pool.
-
Jorts (I assume jean shorts) - never seen them, never want to. Sounds like the worst idea for clothing since the mankini.
-
Sounds like the worst idea for clothing since the mankini.
Uggh! I was a lifeguard in highschool. There were a few times I'd see an overweight gentleman and think he wasn't wearing anything, so I'd go to let him know he needed to leave since we didn't allow skinny-dipping. Then he'd turn around and I'd realize he was wearing a speedo. Happened with at least 3 different guys.
Rule of thumb: If your swimsuit cannot be seen from front, back, and sides, pick a different swimsuit!
-
It’s not that we’re not the only ones finding bugs, but our use case is probably atypical, and we’re one of the only ones using the software in this manner / to this extent.
I sure as hell am not gonna test Discourse before deploying a new version, so this seems a decent tradeoff to get faster fixes.
Otherwise, we’d need to wait until the fix got promoted to a stable branch, or whatever.
-
@cpradio, please elaborate on, "Since we aren't on latest, you probably won't get much help on this."
Sure, what do you want to know specifically?
We use a fork of Discourse, so we can really utilize a lot of changes we've made to Discourse (the tagging plugin, some custom UI work, etc). So we are not running the latest beta release, latest commit, etc. We are usually 4-6 versions behind what is on Meta.
As such, we get a lot of throw back from the Discourse team that we should upgrade first to see if "our bug" is fixed, even though, I verify the bug still exists on my Development machine, which is always in sync with "master"
Did that answer your question?
-
It’s not that we’re not the only ones finding bugs, but our use case is probably atypical, and we’re one of the only ones using the software in this manner / to this extent.
I sure as hell am not gonna test Discourse before deploying a new version, so this seems a decent tradeoff to get faster fixes.
Otherwise, we’d need to wait until the fix got promoted to a stable branch, or whatever.
<img src='/uploads/default/169/9b733b9f44bdae87.jpg' width='1' height='1'>So we have to live with breaking changes (the font size issue) just so we have to deal with minor issue (escaping the asterisk with twelve conditions) for a shorter period of time?
-
just so we have to deal with minor issue (escaping the asterisk with twelve conditions) for a shorter period of time?
That one still isn't fixed, BTW.
*******bet you can't read this!
So much for a "shorter period of time".
Still, I couldn't have put it better.
-
That one still isn't fixed, BTW.
*******bet you can't read this!
So much for a "shorter period of time".
Still, I couldn't have put it better.
It will take 8 years to reach Stable
Is anyone else getting the read-only post entry box?
-
Did that answer your question?
I think so. It's about what I figured. In particular, a big concern here is typically how long it takes to fix a bug. When we find something new in one of the less frequent branches, I was wondering how interested they were in verifying and fixing, even if it takes a while to get them into the later branches.
-
I guess? I mean, it’s not like there’s too many crazy breaking changes, right? And those breaking changes are fixed right away, yah?
Sure, maybe it’s a little WTF-y …. but I upgraded CS 3 times over the what, 8 years or something, and that’s a whole different class of WTF. So arguably we’re still in WTF territory, just on a different side of the island.
-
I guess? I mean, it’s not like there’s too many crazy breaking changes, right?
White pages? Infinniscroller? Small text? Impossible to use on mobile? Random page jumps?
There are so many topics in the Bug category that I just ignore it.
And those breaking changes are fixed right away, yah?
Not usually.
-
-
-
I was wondering how interested they were in verifying and fixing, even if it takes a while to get them into the later branches.
From my experience, it depends on the impact of the bug. If the impact is large, they get to it quickly. If the impact is -- you can't do X without resulting to using HTML markup, then it ends up on the bottom of the stack. If it is doing the following ... hides random characters, then a dart is thrown every hour until the optimal wait time is determined.
-
And those breaking changes are fixed right away, yah?
White pages?
Been going on for months, still not fixed.
Small text?
Don't use Firefox, so it didn't affect me. But it looks like this should be fixed. By introducing a new line-height issue which makes the site harder to read. So we're back to "Fix a bug, create a bug." Also, took 3 or four days. If they'd looked at what we figured out here, they could have put together a better fix in the same time.
Impossible to use on mobile?
Still waiting on something other than "It's Android's fault" for this one.
Edit: This has actually been getting worse.
Random page jumps?
No progress on that in months.
-
Don't use Firefox, so it didn't affect me. But it looks like this should be fixed. By introducing a new line-height issue which makes the site harder to read. So we're back to "Fix a bug, create a bug." Also, took 3 or four days. If they'd looked at what we figured out here, they could have put together a better fix in the same time.
Also shows the lack of testing on their end. It would have taken 5 minutes for someone to load a topic in each of the major browsers and find that it wasn't ready for production. I'd say it was the equivalent of selling a car that didn't have a gas tank installed. There's no excuse for not noticing such things.
-
There's no excuse for not noticing such things.
Agreed. They seem to have no process in place whatsoever.
-
Agreed. They seem to have no process in place whatsoever.
- ship!
- let WTDWTF find bugs
- hack until it looks workable
- repeat
-
I guess? I mean, it’s not like there’s too many crazy breaking changes, right? And those breaking changes are fixed right away, yah?
No. That "2 9's" chart Atwood crammed in here was vastly inaccurate, because it only counted the site being up and running and accessible to a web browser. It didn't count all the times people couldn't post because their postings instantly disappeared, or people can't read a topic because some topics mysteriously don't work on some phones for no good reason, or ... all the hundreds of things that prevents people from using this software as a forum.
Fixed right away? Sometimes-- but they're never FIXED fixed. They're "fixed but now something else is wrong", or "fixed by just removing it because 1 person said they didn't use it very often", or "fixed but then regressed less than a week later." I'd accuse you of not paying attention, but I know for sure you aren't.
EDIT: and as abarker mentioned, mobile support has been getting worse month-over-month. When we first adopted this shitpile, it worked pretty well on my Windows Phone. Now it usually loads to the wrong post at best (loads to the top of the "block" of downloaded posts instead of the one I wanted to view). And that's after literally a solid minute of grinding away at God knows what.
Which wouldn't even bother me that much-- I mean it's usable, if barely-- if Atwood and cronies showed even the slightest interest in finding or fixing the bugs. He's even come in here and posted that they own Lumia phones for testing, they just don't give a shit about actually testing them.
And of course none of this is even getting into the philosophical arguments about Discourse, even after months of development, having fewer feature and significantly more bugs (although admittedly fewer security-related ones) than Community Server, a product that hadn't been significantly updated since 2008. Even when Discourse worked on Windows Mobile, CS worked better. Generally, software is supposed to get better with time, not worse. But I guess that's just silly old fashioned thinking, not the new Atwood/Papadimoulis mindscape.:
I'd take the "download the huge list of tags twice each page load" bug over "typing '3.' in the text box results in '1.' on the post" any day. ANY FUCKING DAY OF THE WEEK.
-
>Monarch:
Yes the model does use free crowd sourcing for both free QA and R&D, which you refer to as "tricking idiots into helping us for free".Right; because that's what it is.
At this late date, if you consider it still to be tricking, then you are TRWTF, but I think you know that. (That goes for the rest of us too, of course.)
For the T1000, every time you scroll and new posts are loaded an array with ~31K items is being sent over and over.
Not that I'm trying to justify it but probably hardly any threads anywhere will have that kind of post count.
lso if we stop providing our services and other people get to hit these problems
It might be entertaining for people to go to other forums running Discurse and create accounts and trigger those bugs. But I wouldn't advocate that because it's probably not nice.
skirts< pants < dress < no pants
Where do kilts come in? (edit: hanzoed)
@Intercourse said:
I have a friend who would read that rule and come in the next day wearing chaps.
How has his employer not yet come up with a "please no rules lawyering" rule?
-
-
why does everyone ask about kilts?
I actually know someone who wears them. And a blogger I used to read before he closed up shop used to wear them too.
-
i know people who wear them too. that wasn't my question.
;-)
my question was why do people always ask about kilts?
also when are you going to take your spoon back? i'm getting tired holding it.
-
my question was why do people always ask about kilts?
Because they're a thing that people wear. I can't believe I had to write that.
Aside: browser bug? Possibly not, per se, but I don't know how to prevent it from doing that.
also when are you going to take your spoon back?
When you stop posting more than me! I've been too busy this week.
-
Because they're a thing that people wear
we're going in circles on this one aren't we?
yes people wear, but why does everyone, including people who have never seen a kilt ask about kilts?
-
yes people wear, but why does everyone, including people who have never seen a kilt ask about kilts?
No, you're missing my point. Ten years ago, nobody would have. But now, because a few strange people wear 'em, enough people have heard about them being worn by real people and not just bagpipers in parades, when someone lists a bunch of bottom-half clothing types and don't list kilts, because traditionally why would you because nobody is wearing them, they think "well, what about kilts?"
It's like that goofy Yogi Berra quote, "nobody goes there, it's too crowded."
IOW I'm answering the question on the regular and meta levels.
-
-
Kilts are huge in Seattle.
Actually that's a bit of a surprise. I would have figured all the hipsters had moved on to something else by now, like bib overalls or...hmm...togas or something.
-
Kilts are huge in Seattle.
Well, I can add that to my reasons to not go to Seattle.
Although, for anyone who has not been for a few years, I would suggest a trip to Austin. You have not experienced all that life has to offer until you have drank at a bar full of Mexican hipsters. I felt like I was in a Twilight Zone episode or something.
-
Actually that's a bit of a surprise. I would have figured all the hipsters had moved on to something else by now, like bib overalls or...hmm...togas or something.
You just reminded me of the Mission Hill episode where the super-hipster roommate went to Japan and came back with super-tight shorts with cartoon faces on the ass.
-
For some reason, kilts are insanely popular with my running group.
-
@Intercourse said:
I am fine with that. Let someone else do their alpha bug testing for a bit. I vote for at least trying the stable branch for a while. At the very least, we can all have a good laugh about all of the bugs we find in that, with it supposedly being the most bug-free.
That might backfire... You assume others would actually do alpha testing. Without our deep (and unique) testing, there probably wouldn't be many bugreports and Discourse would look stable on the surface.
At least now there is a slim chance the bugs we report get fixed and @PJH can update our instance of DS soon after the bugfix is committed.@Intercourse said:
Question: If we were on stable, would I be able to browse this POS on my Android phone? If so, then my vote is a resounding yes. The bleeding edge is getting pretty tiring around here.
Try a stable DS deployment? ICBA to check, but it would surprise me if there isn't a list of clients using DS on http://www.dicsource.org somewhere.
-
-
yes people wear, but why does everyone, including people who have never seen a kilt ask about kilts?
Because they're a skirt that heteronormative men feel they can wear without being called cross-dressers.
</
>Kilts are huge in Seattle.
Because the people who wear them are huge?
</ .. you get the idea.
-
yes people wear, but why does everyone, including people who have never seen a kilt ask about kilts?
Because potato
-
accalia:
yes people wear, but why does everyone, including people who have never seen a kilt ask about kilts?Because you got all pendantic when I mentioned pants so I got all inclusive and stuff.
Maybe.
Also, hipster-curiosity.
Hipster-curious WM seeks same for weekend caber tossing, axe throwing and kilt wearing.
-
"The following is a public service announcement"
Gentlefolk, we do need to keep this in mind:
I upgraded CS 3 times ... and that’s a whole different class of WTF.
Alex is generously hosting this FREE site. Thank you. We are not worthy.
RETURNING TO OUR REGULAR PROGRAMMING:
I guess? I mean, it’s not like there’s too many crazy breaking changes, right? And those breaking changes are fixed right away, yah?
It's at version 1.1, how many breaking changes should leave the (notional, web-connected world-wide) building?
Zero.
EDIT: fine, 1.1, not 1.2.
-
-
EDIT: fine, 1.1, not 1.2.
Crap, that's what I get for releasing before my testers have gotten a chance to check my work.
-
Well...
-
AHA!
As it always seems to get to...
Who is checking the checkers?
Filed under: "while I was watching the checkers, the dog ate the chess pieces."
-
If I google "jorts" I get pictures of men wearing short jeans.
But I see women wearing short jeans all the time and they don't seem to be embarrassed. Are those not "jorts" too?
Stupid double standards. Society will not be free until men wear miniskirts
-
-
No, because society.
If I didn't have to follow social rules... I'd probably wear only a sleeved blanket. And crocs.
-
-
Someone has to take the first step. That someone won't be me. Sorry. I posted about it online, that's better than nothing.
Hey, I'm not saying I don't want to make the world better, this is just not my area of expertise.
(Remember when women couldn't wear pants, btw?)
-
But I see women wearing short jeans all the time and they don't seem to be embarrassed. Are those not "jorts" too?
Yes, but I think they're more commonly called 'Daisy Dukes' when women wear them. And women, as a rule, tend to have nicer legs than men.
-
And women, as a rule, tend to have nicer legs than men.
this is not a thing i can agree with.
but then i'm not much of a leg fox to begin with. ;-)
-
@ijij said:
It's at version 1.2
Nope!
@PJH: What version are we on?
Edit: Nevermind, Boomzilla already answered.
-
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.
Sorry but I just don't think the Stable edition can actually have more bugs than Latest. And if it does, they will be minor ones.
