Reputation vs. Posts
-
@ben_lubar said in Reputation vs. Posts:
@accalia hey, if you want to write a NodeBB-to-Discourse importer, I won't stop you.
Or go anywhere near it.
How many cupcakes would that take?
-
@FrostCat said in Reputation vs. Posts:
someone like @ben_lubar could test something like sockbot against a copy of the DB, at least in theory.
he can if he wants to, but if he's gonna do that he can write the shadowmod plugin for sockbot and take the blame for it when it goes wrong.
-
@Lorne-Kates said in Reputation vs. Posts:
Hell, post count and reputation may already be pre-calced somewhere, making it even easier.
Psst.
Click on your avatar.
-
@FrostCat said in Reputation vs. Posts:
Well, but that's because it had shit indexing, wasn't it?
How does this myth persist? No, it was just shit.
-
@FrostCat said in Reputation vs. Posts:
I'm sure. I'm just saying, given a good schema and underlying RDBMS, I bet it wouldn't be.
And appropriate hardware.
-
-
@ben_lubar said in Reputation vs. Posts:
@Lorne-Kates said in Reputation vs. Posts:
Hell, post count and reputation may already be pre-calced somewhere, making it even easier.
Psst.
Click on your avatar.
Doesn't that turn it into a checkbox?
But you know what's even better than clicking on the front-end GUI for every single person? Running an SQL statement. Because I meant "precalculated in the database".
-
@Lorne-Kates notice how fast it loads? It's not like those 15 minute loading times for Discourse user badges.
-
@ben_lubar said in Reputation vs. Posts:
@Lorne-Kates notice how fast it loads? It's not like those 15 minute loading times for Discourse user badges.
Yes.
...
?
-
@Lorne-Kates what I'm saying is that you're probably right about it being precomputed.
-
@ben_lubar said in Reputation vs. Posts:
@Lorne-Kates what I'm saying is that you're probably right about it being precomputed.
Ah.
So is doing this ratio query still going to bring the "
professionaldatabase" sobbing to it's knees?
-
@Lorne-Kates nah. I'm just lazy.
-
@ben_lubar said in Reputation vs. Posts:
@Lorne-Kates nah. I'm just lazy.
Today, you are truly a developer.
-
@Lorne-Kates said in Reputation vs. Posts:
@ben_lubar said in Reputation vs. Posts:
@Lorne-Kates nah. I'm just lazy.
Today, you are truly a
developerTDWTF admin.
-
@boomzilla oh, I'll get around to it at some point. I think trying to learn Node gave me brain cancer.
-
@boomzilla said in Reputation vs. Posts:
How does this myth persist? No, it was just shit.
Doesn't the one imply the other?
-
@boomzilla said in Reputation vs. Posts:
And appropriate hardware.
Sure. But no forum should need SSDs (or whatever) just to get good reporting performance.
-
@FrostCat said in Reputation vs. Posts:
@boomzilla said in Reputation vs. Posts:
And appropriate hardware.
Sure. But no forum should need SSDs (or whatever) just to get good reporting performance.
:swamp:
-
@FrostCat said in Reputation vs. Posts:
Doesn't the one imply the other?
Doesn't mean the other implies the one.
-
@FrostCat said in Reputation vs. Posts:
Sure. But no forum should need SSDs (or whatever) just to get good reporting performance.
The prices on SSDs are so low, why wouldn't you put your database on there?
-
@boomzilla said in Reputation vs. Posts:
Doesn't mean the other implies the one.
Like Apple, I don't see how that's relevant.
-
@FrostCat said in Reputation vs. Posts:
@boomzilla said in Reputation vs. Posts:
Doesn't mean the other implies the one.
Like Apple, I don't see how that's relevant.
Because your only conception of problems when using a database is that the indices in the database are bad?
-
@boomzilla said in Reputation vs. Posts:
Because your only conception of problems when using a database is that the indices in the database are bad?
Truly, you have a dizzying intellect.
-
@FrostCat said in Reputation vs. Posts:
Truly, you have a dizzying intellect.
You'll take my word for it.
-
@Lorne-Kates said in Reputation vs. Posts:
Any status should include WHERE thread_id <> likes_thread_id
Well that's basically what the old queries were. More specifically threads including a post that had a particular UUID by an admin were excluded - see BZ's .sig since we moved over for example. (I'm assuming it's one of the exclusion UUIDs - I haven't bothered actually checking.)
@Lorne-Kates said in Reputation vs. Posts:
MongoDB is so fucking shitty that we can't do queries on it
I've not even looked at it yet - the implication I got was if it happened far too frequently 'shit' might happen.
As pointed out previously (and as basically what happened on DC):
- If we're after 'query random shit whenever' it will likely have to be against an 'off-site, delayed' copy of the DB
- live stuff will have to be on a 'as required, but not by user' schedule and will need to be an addon of some kind.
@Lorne-Kates said in Reputation vs. Posts:
Why are we using it?
Discourse told us to fuck off. We fucked off. Before doing so, we spent a while looking at the alternatives - this was the least worst in the general opinion of most who'd actually be using it. And who actually expressed an opinion before it happened. I was rather taken with Flarum, but they were certainly not ready for us, either then, now, or even in the near future.
@loopback0 said in Reputation vs. Posts:
They're pre-written queries - I'm not sure how a never ending query can be introduced?
The issue over on DC was how some heavy some of the queries were. ISTR the attendance one was particularly bad. Because of the hoops it needed to jump through to get the data.
Even the 2^n and 3^n badges couldn't be run on a "when a post was made/read" due to the load, so were relegated to "once a day."
@ben_lubar said in Reputation vs. Posts:
@accalia hey, if you want to write a NodeBB-to-Discourse importer, I won't stop you.
Or go anywhere near it.I LOL'd.
-
-
@PJH said in Reputation vs. Posts:
I was rather taken with Flarum, but they were certainly not ready for us, either then, now, or even in the near future.
What I liked was they had the decency to admit it to us
-
@PJH said in Reputation vs. Posts:
I'm assuming it's one of the exclusion UUIDs - I haven't bothered actually checking.
Nope.
-
@boomzilla said in Reputation vs. Posts:
@PJH said in Reputation vs. Posts:
I'm assuming it's one of the exclusion UUIDs - I haven't bothered actually checking.
Nope.
Well, knowing you, I was certain it was, at least, one of the ones used in the queries, rather than one from, say, https://www.uuidgenerator.net
I was just wrong on the category....
-
@RaceProUK said in Reputation vs. Posts:
@accalia How many sneezes does it require to take NodeBB down?
2
-
@PJH said in Reputation vs. Posts:
this was the least worst in the general opinion of most who'd actually be using it.
Most users didn't care enough to test it enough though.
It was a good learning experience, if I ever need to chose software, I'll take something popular, because you guys proved that a test instance or whatever is worthless. Take the popular, time tested option if you need to be safe.
-
@fbmac said in Reputation vs. Posts:
Take the popular, time tested option if you need to be safe.
Give over. People would have found things to bitch about with whatever we chose.
-
@loopback0 oh, they would, but at least it would be something useable when I'm in a area with weak signal, like where I spend most of my time, and any other website works perfectly fine.
Xenforo may have silly issues like the css stuff people complain here, but I doubt it has any serious issues that make it unusable for someone.
-
it was statsporn.
Does that make me a statspornographer?
EDIT: Argh, signature changes retrospectively; it isn't baked into the post.
--
18 USC 2257 notice: all data have 𝜒²≥18
-
@accalia said in Reputation vs. Posts:
oh we can query it. we just can't query live without risking performance impacts to the forum itself.
So, you're telling me that statspornography is a server health hazard?
-
@Greybeard said in Reputation vs. Posts:
So, you're telling me that statspornography is a server health hazard?
Together we can beat it!
-
@Vaire said in Reputation vs. Posts:
@ben_lubar said in Reputation vs. Posts:
https://what.thedailywtf.com/users/sort-reputation
https://what.thedailywtf.com/users/sort-posts1305:911 rep to posts ratio. Wow, I am lower than I thought.
you don't happen to post in the funny/cute stuff threads? Or were you even involved in the likes thread?
-
@Greybeard Jesus I'm behind @Bort on reputation. And I have almost twice as many posts.
-
As I'm going up the thread and comparing everyone's rep/posts ratio, I like how sometimes I'm thrown into a user's profile page when clicking his avatar instead of getting the usercard.
Happens about one in 10 times, with no pattern in sight.
-
@CreatedToDislikeThis said in Reputation vs. Posts:
As I'm going up the thread and comparing everyone's rep/posts ratio, I like how sometimes I'm thrown into a user's profile page when clicking his avatar instead of getting the usercard.
Happens about one in 10 times, with no pattern in sight.Clicking the user's avatar displays the usercard. Clicking their username takes you to their profile instead.
-
@anotherusername said in Reputation vs. Posts:
Clicking the user's avatar displays the usercard.
Unless you're on /unread where it causes checkmarks.
-
@aliceif said in Reputation vs. Posts:
Unless you're on /unread where it causes checkmarks.
Yeah, they still haven't fixed that bug. At least they already acknowledged that it's stupid.
-
@ben_lubar said in Reputation vs. Posts:
@boomzilla said in Reputation vs. Posts:
because supposedly there's no way to persist stuff to disk. I still don't think that can possibly be right, but who knows?
It can persist to disk
, but the entire DB has to be in memory at all timesby swapping RAM to disk.Filed under: an often-overlooked way of persisting data to disk
-
@anotherusername said in Reputation vs. Posts:
Clicking the user's avatar displays the usercard. Clicking their username takes you to their profile instead.
I never clicked on a username - clicking the user's avatar displays the usercard except when it takes you to their profile instead.
INB4: I don't double-click either. (Unless my mouse is faulty, which might be a possible explanation if nobody else beside me can reproduce - can you? (I know you didn't try yet))
It seems to happen more often when you don't close the previous usercard when clicking on another avatar.
-
@CreatedToDislikeThis said in Reputation vs. Posts:
It seems to happen more often when you don't close the previous usercard when clicking on another avatar.
I just tried exactly that, and managed to reproduce it on the 10th avatar.
On second try, it did it on the 14th.Chrome version 50.0.2661.75 (64-bit) on Debian Linux v.8.4
-
@CreatedToDislikeThis said in Reputation vs. Posts:
I never clicked on a username - clicking the user's avatar displays the usercard except when it takes you to their profile instead.
@TimeBandit said in Reputation vs. Posts:
I just tried exactly that, and managed to reproduce it on the 10th avatar.
On second try, it did it on the 14th.
Chrome version 50.0.2661.75 (64-bit) on Debian Linux v.8.4I just clicked all of the avatars on about 2 pages of posts (so, 45 or so posts) and it never happened. Latest Firefox on Windows 7 64-bit, if it matters. I have pagination turned on, also if it matters.
-
@Captain said in Reputation vs. Posts:
Jesus I'm behind @Bort on reputation. And I have almost twice as many posts.
So if no one likes me, then apparently it is possible for there to be a negative number of people.
Take that, math!
-
@anotherusername said in Reputation vs. Posts:
I just clicked all of the avatars on about 2 pages of posts (so, 45 or so posts) and it never happened. Latest Firefox on Windows 7 64-bit, if it matters. I have pagination turned on, also if it matters.
I guess pagination makes the difference.
-
I'm pretty sure it's based on whether the post was made while you were on the page.
-
@FrostCat said in Reputation vs. Posts:
How big is the database again? The idea that you just can't do real-time queries on something in the tens of gigs...well, I can't quite come up with the right insult. I'm sure everyone who's ever written an ERP or payroll package is shocked.
We have a MySQL database that's about 50 mb. Takes four seconds to search, but that's probably because I haven't put my hands on it.