:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
@OffByOne said:
"constructive criticism" category
Isn't "Bugs" and "Features" for that?Bugs: Things you're doing wrong and CLOSED
Features: Things we may do different if you pay us, else CLOSED
-
I still don't understand the discoreasoning behind this discodesign 'decision', it discoliberately introduced disconsistency into the product.
-
@AlexMedia said:
I still don't understand the discoreasoning behind this discodesign 'decision', it discoliberately introduced disconsistency into the product.
Surely that should be (discoballs)
-
the discoabuse of Docker
Has anybody ever attempted to make a "sane" disco docker setup? Or is it just so badly fucked people shake their heads and walk away?
-
It's badly fucked. Someone should be able to separate Redis, Postgres, and nginx into their own containers, someone should be able to rebase the Discourse app container on, say a Rails container, rather than the bare OS, and someone should be able to make it not rebuild a bunch of things (like, I don't know, hosting their own PPA? Using Gifsicle 1.78 rather than 1.87?).
But with and claiming that it's completely unsupported and do-at-your-own-risk, why would anyone?
-
that it's completely unsupported and do-at-your-own-risk, why would anyone?
Yeah but so is using the Discodev docker on almost anything that isn't Digital Ocean. Or any other excuse that suits Jeff if you don't pay him for Discohosting.
-
I'm almost tempted to try it just to learn a little more about docker. I know it will be hellish, but getting it to a similar state to just about anything else where you have an actual freaking dockerfile that works could be interesting...
-
Or any other excuse that suits Jeff if you don't pay him for Discohosting.
I'm willing to bet Digital Ocean:
- Understands what ECC memory is.
- Understands the whens and whys to use it.
Discopope doesn't. Big surprise, I know.
-
-
He does use such outstanding logic as "Google didn't use it in 1999" and "this company that builds gaming PCs doesn't use it".
-
Which is really funny because not only do they use ECC RAM now, they studied it:
Conclusion 1: We found the incidence of memory errors
and the range of error rates across different DIMMs to be
much higher than previously reported.
About a third of machines and over 8% of DIMMs in
our fleet saw at least one correctable error per year
[....]
The annual incidence of uncorrectable errors was
1.3% per machine and 0.22% per DIMM.The conclusion we draw is that error correcting codes are
crucial for reducing the large number of memory errors to
a manageable number of uncorrectable errors.So choices are 33% of their servers fuck up per year (And usually multiple times), or pay slightly more for RAM and only 1.3% fuck up.
What a tough choice.
-
Much easier since they fired QA. Nobody will notice the reliability change.
-
Much easier since they fired QA. Nobody will notice the reliability change.
I'm pretty sure reliability will stay consistent.
#AT ZERO PERCENT!
BURN OF THE CENTURY!
-
Has anybody ever attempted to make a "sane" disco docker setup?
Didn't @ben_lubar try this? I can't immediately find it in his Github repositories though and I'd rather perform self-SRS with a rusty spoon than use .
Or is it just so badly fucked people shake their heads and walk away?
Also, yes.
-
Discopope doesn't. Big surprise, I know.
That's the second time I've tried reading that blog entry (my eyes glaze over and I start thinking it's a student report but with decent spelling), and again I get stuck on the bit where he says that ruby is only good for single-threading. Maybe it's naive of me, but I figured that in an environment like that, if you need better performance, it is up to you as the developer to make sane architectural choices that will enable application-level parallelism?
-
I figured that in an environment like that, if you need better performance, it is up to you as the developer to make sane architectural choices that will enable application-level parallelism?
Yes, but Jeff.
-
Maybe it's naive of me, but I figured that in an environment like that, if you need better performance, it is up to you as the developer to make sane architectural choices that will enable application-level parallelism?
The Ruby approach to parallelism is to launch multiple Ruby processes in parallel.
-
Preferably In multiple machines.
-
The Ruby approach to parallelism is to launch multiple Ruby processes in parallel.
Which should be fine. But this means you need to design your system differently, e.g. with background workers, thread/process pools, brokers, etc. It would also mean that you ought to limit the amount of work a single thread does for a single request (like "don't look up the id of every post in this thread just to show the latest unread plus or minus 20 posts"), and so on (y'all probably have a better idea of what to do or not do do than I have).
Going out of my way to find extra expensive hardware just to optimise for single-threading seems to be a long way down the list of things to do.
-
@loopback0 said:
Or any other excuse that suits Jeff if you don't pay him for Discohosting.
I'm willing to bet Digital Ocean:
- Understands what ECC memory is.
- Understands the whens and whys to use it.
Discopope doesn't. Big surprise, I know.
I don't expect ECC RAM to make Discourse more reliable, so why bother?
-
Going out of my way to find extra expensive hardware just to optimise for single-threading seems to be a long way down the list of things to do.
Well yeah. Especially given that stuff like database lookups should be I/O bound anyway.
Ruby is definitely not the only way that Discourse Does It Wrong, but it's sure a contributor. Though if we were going to list all the ways, I'd put Ember higher up the list, and TCDCK developers would be pinned to the top. With rusty nails.
-
I've been getting a lot of errors the last few days, 502's ,504's, timeouts, White screen of death and even a few 404's.
Am i the only one ? I'm obviously accustomed to this - but there's been a LOT theese past few days.
-
I've been getting a lot of errors the last few days, 502's ,504's, timeouts, White screen of death and even a few 404's.
Me too. I guess we're again.
-
-
and TCDCK developers would be pinned to the top. With rusty nails.
Doesn't this imply that the nails might break soon (since they are rusty) and the DiscoDevs would lose their top spot on your list?
I would suggest using something like titanium nails with spikes on the side that are also electrified because why not.Filed Under: Soo.... how well does titanium conduct electricity anyway.... off to google
Addendum: Fairly low conductivity but if we use the power that would otherwise be needed to host a Discourse instance, I think we will be fine!
-
Yup, it seems to be about 50% of the time when I go into a topic I have some unread in I see a 504 or similar. I thought at one point it was just the lounge, but it has done it since then in other places...
-
I don't expect ECC RAM to make Discourse more reliable, so why bother?
I was expecting someone had already brought this up. I mean...how could you tell if it was the software or the hardware making mistakes in this case?
-
https://meta.discourse.org/t/populating-a-test-database-with-large-number-of-posts-users/38600
I need something that I can mass-generate a large test forum, any pointers?
at one point, one of the guys had a script to generate ONE THOUSAND!!!!OMG posts in a single thread.##large number of posts
1000
-
the upgrade is broken
Did you try rebooting?
Did not work
Uninstall and reinstall Docker
Oh, yeah, great idea!
-
Somebody should point him at sockbot and suggest he hooks it up to something like this. Fire off a few instances of chat bots chatting for a week or so and he could have something with believable content as well...
-
Doesn't this imply that the nails might break soon (since they are rusty) and the DiscoDevs would lose their top spot on your list?
No. It implies a tetanus and a recurring task to hammer in some more nails (with an old shoe or milk bottle). I'm OK with this.
-
I need something that I can mass-generate a large test forum, any pointers?
"Yeah, toss an URL on that Daily WTF forum, they'll take care of it".
-
Apparently Jeff is testing a new "spam the shit out of our users" plugin:
Three "monthly" digests in 12 hours.
-
-
That idea just begs to be abused. And I am tempted to remind them of the "Delete" Edit History feature.
-
Yeah, but if you edit and then wipe history, the user still gets the notification, right? The point is to sneak the "DISREGARD THAT I LOVE COCKS" without the guy being any wiser.
-
Jeff should just send @accalia over to their forum. After they waste 10 hours a day cleaning up typos, they'll drop the idea of editing altogether.
-
Meanwhile, at C
ODCK HQ:: Someone leaked our super secret Discourse Civilizer hidden feature for 1.6. I'm gonna ban someone for it, and we're not leaving this
meeting roomforum thread until I find out who!
-
Yeah, but if you edit and then wipe history, the user still gets the notification, right?
Not if you impersonate him!
-
@Maciejasjmj said:
Yeah, but if you edit and then wipe history, the user still gets the notification, right?
Not if you impersonate him!
This sounds deliciously evil - especially if the user in question doesn't know that impersonation exists ...
-
However, we started to receive complains: people don't like when their grammar is fixed.
Yes. This person is the ideal candidate for fixing grammar and spelling.
-
Well, my grammer is nothing wrong with it's, so I don't see why would they needed those feature anyway?
-
super secret Discourse Civilizer hidden feature
Enquiring minds would like to know more...
-
: We could tell you, but then we would have to BAN you. As a matter of fact, let's just skip straight to the BANNING!
-
-
: We recommend running tests-passed, it's a very good branch.
-
: We recommend running tests-passed, it's a very good branch.
Both tests and passed are optional.
-
I see mentions got bikeshedded.
-
I guess it's bad enough you get a notification, why should you be forced to be able to read your name in the post?
-
1265 bugs got squashed
But how many got the Jeff treatment?
The most viewed topic of the year was The State of JavaScript on Android in 2015 is… poor. At 200+ replies and lots of first-time – and drive-by, but nothing wrong with that – posters, the single-threaded conversation stayed the course just fine
The most viewed topic was about how much your platform sucks on Android. Also you managed to keep a topic with 200 replies on topic? Way to go.
395 enhancements made Discourse even better!
I could also tell you how many UX tweaks we’ve gone through (204), but boasting such a number makes it sound like we’ve added a bunch of stuff, when the truth is we’ve been
slimming things down.bikesheddingFTFJ.