Is this new?
-
Is this new?
-
I've seen this too, but it disappears eventually.
I assumed it to be caching related?
-
No, no, not that.
The fact that it actually has blurb there now instead of just the 'You have no unread topics' that I normally see due to the cache.
-
I no longer care, but adding a second post in the hope that this thread will be validated for post count purposes.
-
I approve of this.
-
we are now fulfilling one of Jeff's prophecies about post counts.
Does it make you feel sick and wrong and sexy too?
-
I don't feel sick, I feel wrong most of the time, that's nothing to do with Jeff.
Sexy? No. I don't feel sexy pretty much any of the time.
-
Is this new?
Yes. There was a complaint over at meta.d that the original text implied something different was happening compared to the preferences, when it's merely static text.
Edit: That wasn't quite what happened - replace 'complaint' with 'bug' and you'd probably be closer to the atmosphere of the topic...
-
I noticed it, and I thought the default for auto tracking was after "reading" for 2 minutes, not 4 (unless they changed it since and I can't be assed to make a sockpuppet account).
-
“We know that this watching/tracking system is confusing. Try to mess with your preferences to get something saner.”
-
Yes, that is pretty much what I read.
Though I find the tracking setup I have - track every fucking thing - is the least insane solution.
-
As far as the unread counter goes, there is this bug:
https://meta.discourse.org/t/incorrect-unread-count-on-topic-page-at-initial-load/19097
-
And the most amazing thing about that report is that Jeff gave orders to fix it.
-
Which is especially bizarre since he claims that Dicsourse isn't run by his sole decision.
Well, that and the fact that he said it needs to be fixed.
-
Which is especially bizarre since he claims that Dicsourse isn't run by his sole decision.
In evidence for that proposition, there's no sign that anyone is following the order.
-
And the most amazing thing about that report is that Jeff gave orders to hide the problem by refetching the unread number when the unread tab is clicked.
FTFY
-
Jeff's prophecies about post counts.
except we still don't have post counts by our names.
-
-
Only approximately so.
-
Depends on if you're talking about the 2^n titles or the @onyx userscript
-
I really need to try and optimize that thing. In my defence, I didn't expect Discourse to be that stupid to actually re-render the whole damned post when you're doing something like... dunno... clicking on the like button, or selecting text!
I know, I'm TRWTF...
-
I really need to try and optimize that thing. In my defence, I didn't expect Discourse to be that stupid to actually re-render the whole damned post when you're doing something like... dunno... clicking on the like button, or selecting text!
I know, I'm TRWTF...
Now, now. Don't go blaming yourself for Jeff's brainchild.
-
Now, now. Don't go blaming yourself for Jeff's brainchild.
That's the problem. I don't think it's necessarily Jeff. I think it might be either Ember or it's ungodly alliance with RoR. And in that case... yeah, might be unfixable, meaning that we're stuck with god-awful performance, forever.
-
That's the problem. I don't think it's necessarily Jeff. I think it might be either Ember or it's ungodly alliance with RoR. And in that case... yeah, might be unfixable, meaning that we're stuck with god-awful performance, forever.
If it's Ember -> still CDCK's fault for using Ember.
If it's Ember + RoR -> still CDCK's fault for using those two together.Yep, still Jeff's fault (at least partially).
-
-
THANKS ATWOOD
You know, maybe we should start throwing some blame at Sam too. It doesn't seem right that he gets a free pass just because he's more polite.
-
Presumably Dicsourse was waiting for one of Sam's ensure "consistency" jobs to run. That counter gets more broken every day.
-
They have a pretty aggressive bug release schedule.
