What's so bad about discourse?
-
Is that route still the top performance hog? Tracking read status for individual posts is a nice feature, but is it really that nice? Like, we've come to take this adhd pinging the server with our reading progress every couple of seconds for granted, but it actually takes a fuck load of effort tracking whether posts are in view or not. If a mobile-app developer were to skimp on that, e.g. mark posts as read as soon as their ui element got created, or store read statuses locally to send only when connected to wifi, the rough edges have the potential to be pretty god damn painful. Think about how many people complain about fucked up notifications after every jeffing, kuro bars, the incomprehensible second unread count on some threads — this is a massively over-engineered feature, right?
-
but I'd have a hard time even lifting that
there's no problem trhat applied rocketry cannot help solve*!
*applied rocketry may cause more problems than it solves. Applied rocketry will not be liable for any additional problems arising from the application of said rocketry.
-
I just got mysteriously logged out
-
Could be Discourse being Discourse, or it could be an admin impersonating you and ending it the only supported way.
You may never know.
-
I'll just point out actual rocket science is less complicated than Discourse. Thus any-and-all information pertaining to Discourse should be placed on a rocket that will land on the Sun.
-
Fixed, unfixed, closed.
Dear god, what an idiot. It's a core UI component that has no fallback text...
-
It's not exactly active.
Just because you don't see any new posts doesn't mean there weren't any .
-
-
Aaaand that's @cartman82's joke ruined
Which would be a shame, if this site wasn't where jokes go to die.
-
When the CDN returns a 5xx error and doesn't load the image, Discourse doesn't show a placeholder so users can't access their profile
The obvious solution is to set up an additional CDN to deliver default avatars for users whose letter avatars fail to load.
-
The obvious solution is to set up an additional CDN to deliver default avatars for users whose letter avatars fail to load.
The obvious solution is to book some flights and go kick all of the DiscoDevs in the testicles.
-
The obvious solution is 504 OK.
-
Discourse also has no error handling on its infiniscroll. If it fails to load posts because of a brief interruption (like on a moving train), it just dies completely and only a refresh will let you continue.
-
It's just a vocal minority that is angry because they were banned from meta.d, most users here love it.
-
@loopback0 said:
It's just Discourse
is writtenwas vomited by clowns.I must object strongly to this. I've known a number of clowns (my ex-wife was a professional clown for a while, and even my kids got paid for a couple of gigs), and all of them are nicer and more competent than Jeff & Co.
Better?
-
@loopback0 said:
Fixed, unfixed, closed.
You have to be fist-fucking me?
I can kind of understand why a purity nerd would do what they did. That doesn't mean I agree with it.
-
Is that route still the top performance hog?
It was number 3 in the latest report:
Top 100 routes by Server Load Route Duration Reqs Mobile ----- -------- ---- ------ topics/show 78835.66 67260 2557 (3.80)% posts/show 17276.29 23917 840 (3.51)% topics/timings (POST) 17100.71 44765 8485 (18.95)%
But the individual operations don't seem to be a major problem, I think. It's other weird things going on that cause discourse to stumble over itself, I think. Like hammering the DB counting stuff in profiles.
-
It's just a vocal minority that is angry because they were banned from meta.d, most users here love it.
You delete that right now!
-
@loopback0 said:
When the CDN returns a 5xx error and doesn't load the image, Discourse doesn't show a placeholder so users can't access their profile
The obvious solution is to set up an additional CDN to deliver default avatars for users whose letter avatars fail to load.
The obvious solution is to set up an additional CDN on top of that to deliver an "Avatar Failed To Load" placeholder image for users who backup letter avatar fails to load. The Avatar Failed to Load placeholder should be generated for each user on account creation, so each user has a unique "No Avatar" avatar (hence the need for CDN).
-
@loopback0 said:
Aaaand that's @cartman82's joke ruined
Which would be a shame, if this site wasn't where jokes go to die. and get beaten until they revive and die again
FTFY
-
@tar said:
The
obviousfunniersolution is to set up an additional CDN to deliver default avatars for users whose letter avatars fail to load.The obvious solution is to book some flights and go kick all of the DiscoDevs in the testicles.
-
@loopback0 said:
It's just Discourse is written by clowns.
I must object strongly to this. I've known a number of clowns (my ex-wife was a professional clown for a while, and even my kids got paid for a couple of gigs), and all of them are nicer and more competent than Jeff & Co.
Discourse is written by clowns. I assure you, you do not know any of those. Because you'd be dead right now if you did.
-
OK, right... So a shitty back-end and a reasonable front end. Developed by an arrogant dictator with a cult-like following of brainwashed clowns.
Almost exactly the same as the Linux kernel.
Guess i got my answer
-
Every time Facebook loads another batch of posts, the scrollbar resizes. Every time RES loads more posts, the scrollbar resizes.Seriously. Solved fucking problem.
That is exactly what Discourse does for me... Yeah, if you profile the thing it's a bit convoluted. But nothing that I'd say is stupidly bad design.
If loading someone's profile page causes the server to peg a core for 5 minutes, then someone should just fix that bug and move on.
I've never seen it give back moronic HTTP status codes, and the long-polling for live thread updates seems pretty standard.
Given it's the holidays, I'm tempted to attempt an install just to see if it is as bad as y'all say it is.
-
I'm tempted to attempt an install just to see if it is as bad as y'all say it is.
It's probably fine if you have less than 4 users making less than 10 posts a day.
-
It's probably fine if you have less than 4 users making less than 10 posts a day.
I'll give it a go on an AWS micro instance (i'm a cheap bastard) it honestly can't be that bad. Ruby isn't THAT slow.
-
Both server and client sides have 45 layers of abstraction, resulting in huge CPU and memory usage, resulting in sluggish behavior on the client side and timeouts on the server side. Software comes embedded inside a VM because reasons.
Code is hard to modify by design so inexperienced users won't go near it (see above point).Code is available on github. Don't know where u got this VM requirement.
Even though Ruby isn't my primary language, it really shouldn't be that hard to get running, and certainly doesn't look intentionally obfuscated.
After a cursory glance at the code, I don't see over-abstraction. For comparison, have you ever looked at the rails source - particularly ActiveRecord?
-
So what gives?
pjh@what:~$ uptime 04:15:14 up 21 days, 13:28, 1 user, load average: 0.96, 1.41, 1.46 pjh@what:~$ cat /proc/cpuinfo | grep processor processor : 0 processor : 1 pjh@what:~$
Thats with no-one using it. Load averages of 6 or 8 are not uncommon.
pjh@what:~$ df -h | head -n2 Filesystem Size Used Avail Use% Mounted on /dev/vda1 59G 35G 22G 63% / pjh@what:~$
Insufficient space to perform a backup.
DIscourse has:
Easy to use backup and restore (configurations included)<koff>
or it could be an admin impersonating you and ending it the only supported way.
Incognito windows aren't supported?
Don't know where u got this VM requirement.
Docker. Only supported environment.
-
Well, he doesn't want to know how the web works.
-
That is exactly what Discourse does for me...
Just wait a week or so until this thread is long enough.
-
Code is available on github. Don't know where u got this VM requirement.
Even though Ruby isn't my primary language, it really shouldn't be that hard to get running, and certainly doesn't look intentionally obfuscated.
-
@Sam said:
I do not want screen readers reading "avatar" or "username" or anything there.
Oh man, if only the Default Avatar showed a single letter or something. That way that letter could be used as an alt-tag. Sadly, Discourse makes very complicated avatars that are probably hack-proof!
The username has the same problem. There is NO way to put the username into the alt-tag. Urgh!
No, a static string describing something is the only option. Good thing they rolled back!Filed Under: Seriously?
-
The whole default avatar thing is typical of Discourse development.
It's a letter on a coloured square, and yet they massively over-complicated both the original implementation and the newer "improved" implementation.The root of most Discofailures is over-complication of things that should be simple.
-
At this rate, in a few years Discourse will just be a static page that says "Welcome to Discourse"
THIS IS DISCOURSECOM
YOU CAN DO ANYTHING AT DISCOURSECOM
ANYTHING AT ALL
THE ONLY LIMIT IS YOURSELF
-
-
@loopback0 said:
It's a letter on a coloured square,
.. CSS'd to be circular....
I'd forgotten about that
-
I'm still waiting for Jeff to announce that this whole Discourse thing was a joke to show people how software development can go completely off the rails so far that people start believing their pile of bull manure is a wonderful product.
-
software development can go completely off the rails
But isn't this thing written in Ruby on rails?
-
-
-
Almost exactly the same as the Linux kernel.
Almost, except Torvalds is actually competent.
-
Even though Ruby isn't my primary language, it really shouldn't be that hard to get running
EDIT: Bah, I see I'm late to the party as always .
-
I'll give it a go on an AWS micro instance (i'm a cheap bastard) it honestly can't be that bad. Ruby isn't THAT slow.
You're going to have a bad time.
-
-
Code is available on github. Don't know where u got this VM requirement.
From the developers. If you aren't running their Docker image, you can fuck off and they will not help you.
-
-
If you aren't running their Docker image, you can fuck off and they will not help you.
Even if you are running their Docker image, but not on Digital Ocean, you can fuck off and they will not help you.
-
You missed a word there: 'intentionally'.
Dicksores programmers don't need to intentionally obfuscate their code. It is pretty much unreadable already without.
-
<no problems here
-
Even if you are running their Docker image, but not
on Digital OceanHosted by them on their specially blessed platform, you can fuck off and they will not help you.FTFY