:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
Wow. What the fuck did I do to piss you off?
Sorry, was my post that insulting?
Edit: I've re-read your post and may have over-reacted. Let me know if you were just taking the piss and I'll apologise!
Um ... Yeah, it was really just supposed to be a joke. I immediately had this association when reading your post and wrote a reply without thinking. Sorry, I can be an asshole sometimes although I don't mean to be one.
-
-
Humblest apologies - I thought it was a "you're a crybaby" thing but the error was 100% my part not yours.
To answer your question (sheepishly), my first name is Scott and a thousand years ago I used a system called BOS (Business Operating System, from TIS) that had logins limited to 4 letters, hence "SKOT".
I then started using that name on forums and was surprised that on a number of them, this was already taken, so went with "SKOTL" (L is the first letter of my surname).
-
Yeah yeah I know I'm probably still in blakeyrat-outing-angry-mode.
I'm apologising all over the place, though!
-
You mean you aren't SCOTT/TIGER of Oracle fame. I am (not really) dissapoint.
-
Phew. For a minute I thought that was an actual second name in some Slavic country and I just insulted you in the worst way possible. I'm still scared...
-
-
Actually - I could have played that and looked 1% less of an ass-hat.
SKOTL is god of warmongering large-dong fear in the country of my forefathers, and all that.Unfortunately the truthful answer is that I'm a dick. I'm probably done with the apologies now so hope that's enough!
-
Unfortunately the truthful answer is that I'm a dick. I'm probably done with the apologies now so hope that's enough!
You wouldn't have had to apologize at all after the clarification in the edit above, but I still gladly accept your apologies. :)
-
-
Absolved!
-
No,Jeff, you're absolutely right - totally my fault (oops, force of recent habit) please accept my apologies for my shitty network connection peeing all over the might dischorse.
(I fucking hope nodebb is a disaster otherwise we'll have nobody left to blame)
-
We loved it so hard it broke and then he
banned usshowed us what an incredible cunt he isFTFY
-
You should have moused-over to see the link to undefined, too! Discourse Like-bug golf!
But it's built for the next ten years. You clearly need a browser from 10 years in the future. Browsers will be so good by then, they'll magically make this shit just work.
-
But it's built for the next ten years. You clearly need a desktop browser from 10 years in the future. Desktop Browsers will be so good by then, they'll magically make this shit just work.
Mobile is just a fad and will have been replaced by Desktop browsers by thenFTFY
-
So true, because in 10 years, mobile will still be "different"
-
Meh...what is all this blubbering? BACK TO DISCOSHAMING:
https://meta.discourse.org/t/my-hosted-instance-is-corrupt-urgent-help-required-please/36443
https://meta.discourse.org/t/my-hosted-instance-is-corrupt-urgent-help-required-please/36443/6Then it was Fixed. Or was it?
-
-
Whaaa...
The bug was caused by a recent performance commit related to our message bus infrastructure. It looks like messages were being sent across instances on the same container, which is why we didn't see it until we deployed it to customers on the same containers.
What the fuck is the POINT of using containers if you put multiple sites in each one!? Do I fundamentally misunderstand this technology?
-
If it's your money paying for the servers, resource usage suddenly matters.
-
Well at least their sharp-as-knifes QA team caught the bug before it affected any customers.
-
Twice!
-
I hope in my heart that while Sam was fixing this for the SECOND time he at least felt a whinge of shame.
But I know that he did not.
-
Oh no! Blakey, shush! You'll make him cry on twitter again!
-
Well at least their sharp-as-knifes QA team caught the bug before it affected any customers.
I wasn't aware they made any distinction between customers and QA...
-
LIAR. They ban the QA from their bug tracker, of course.
-
That situation clearly never happened:
-
Discourse has always been at war with Eastasia.
-
-
What the actual fuck?
The bug was caused by a recent performance commit related to our message bus infrastructure. It looks like messages were being sent across instances on the same container, which is why we didn't see it until we deployed it to customers on the same containers.
THAT'S NOT HOW CONTAINERS ARE SUPPOSED TO WORK.
-
They don't use it for security, they use containers to make deployment easier in a reproducible environment or something.
-
One's unlisted and the other's been moved somewhere hidden. Of course.
Sweep it under the rug guys. Didn't happen.
-
They don't use anything for security except sheer luck.
-
One's unlisted and the other's been moved somewhere hidden. Of course.
Sweep it under the rug guys. Didn't happen.
Complaint-driven development!
-
THAT'S NOT HOW CONTAINERS ARE SUPPOSED TO WORK.
Yeah, I find it interesting, but not terribly surprising that they're putting multiple instances in a single container. I guess they all use the same DB and everything? Just some routing or whatever to keep everything separate? Shocking that they'd get some wires crossed in there.
-
Yeah, I find it interesting, but not terribly surprising that they're putting multiple instances in a single container. I guess they all use the same DB and everything? Just some routing or whatever to keep everything separate? Shocking that they'd
get some wires crossed in therehaven't pulled the same shit off at least three times before.Or did they? After all, Jeff just Jeffs those things into oblivion. No issues!
-
-
Of course, because some people linked to it from other threads, those will probably get Jeffed into oblivion too...
-
Discourse is showing me the desktop view on Chrome on iPhone for unknown reasons. It's annoying. More annoying than desktop on desktop or even mobile on mobile.
-
Found the link for mobile view. Sorted.
-
I find it "interesting but not terribly surprising" that they gone done fucked up once again because they basically still refuse to take testing seriously. If I was a paying customer, then I'd be publicly questioning what exactly I was paying for at this point.
-
-
Whooooooooops.
-
Not importing the tests was a feature, man!
-
We could have been posting to Meta.d this whole time
-
Well, at least for the subset of "We" that didn't get starholed. Jeffholed? Whatever.
-
Also, last one for the day, I promise...
Regression ahoy!
-
Does everyone else's usercard take 30+ seconds to load, or is it just my crappy network?
Accessing a usercard is a to discussion. So the ShitshowDevs never bothered using indexes on their tables. So visiting a usercard compiles all that user's stats-- from scratch-- and will take 13-30 seconds to load on a good day. On most other days it'll crash Discourse.
And I accidentally lost my 4965 notifications bubble because I visited my profile
Don't worry. That 4965 number was inaccurate anyways. And Discourse would have cleared it for you anyways because you're reading wrong.
-
Newest annoying as piss feature - if you expand the likes to show you who liked something
Oh yeah-- well, if you go to the Notifications tab, it won't even tell you how many people liked a post. It'll just show a ton of 4x4 pixel avatars that you can't make out. If you want to know how many likes, count them up.
And then, of course, realize that Disourse splits up groups of likes-- so you still don't know how many likes a post has unless you click through to a post-- and then you have to deal with all the dumb-as-shit bugs on the post itself. Assuming the thread doesn't 502:OK.
-
We should get like 15 people to likespam the same comment continuously until Discurses crashes.
while(true) { $(".like").click(); }