Is the New counter broken again?!
-
So the New counter showed 399 a bit earlier... it's been creeping up despite there being no new topics that I have access to?
I'm sure this used to work correctly? Is this some weird Discobehaviour that's happened because I no longer have access to categories I used to?!
-
It's the unread counter creeping up that I have issues with
-
That one's at least working as expected
-
Now it says 415.
There are no additional topics that I have visibility of.STUPID DISCHORSE!
-
I filed bugs about it on meta.d (6 months ago) and even got it to a "high priority"-tag (a few weeks ago).
@Sam says he wants to fix it. I am kind of hoping it becomes somewhat of a complete rewrite because the new counter is wrong on so many levels but I am not counting on it.https://meta.discourse.org/t/new-indicator-is-showing-wrong-numbers-again/25860/8
(the initial post was about a slightly different bug)
So far nothing else noteworthy happened BUT meta.d had a dark theme for a while, so thats probably a start!Filed Under: So it will be fixed eventually... hopefully
It could be that Paula is adding new topics and the hiding them. But I did not get that many new topics, so... yeah
-
It could be that Paula is adding new topics and the hiding them. But I did not get that many new topics, so... yeah
I thought about that, but it's a lot created in a short period of time, and if they're hidden then it's still broken. Article is also muted.
and even got it to a "high priority"-tag (a few weeks ago).
Did they finally realise that prioritising bugs by likes was... well... stupid?
Also it's still not even fixed over there after 11 days so it's presumably priority-discohigh.
-
Is this some weird Discobehaviour that's happened because I no longer have access to categories I used to?!
No, there haven't been that many new categories recently. At least not enough to show an increase of 16 topics in about an hour. I only gained 6 new topics in the last 12 hours, and I can see all .
-
Right, so it's (unsurprisingly) just broken.
-
423 without a single New topic showing that's less than 2 days old.
Even for Discocounting this is
-
IIRC, you have stuff muted. Maybe that's contributing? Possibly also stuff in categories to which you lost access?
-
IIRC, you have stuff muted.
Articles is the only muted category.
Possibly also stuff in categories to which you lost access?
I've read at least 20 'New' topics today. Maybe more. The number went down as I opened each, so that's at least 44 new topics across The Lounge and Turn Left? Unless I've forgotten something else only available at TL3+?
I'm still voting that the counting is
-
I'm still voting that the counting is
Most likely. FYI:
8 new topics today, 5 yesterday, 61 total in the last week. At least a couple of those are where you can't see them. that doesn't count PM traffic.
-
Where did you take those numbers from? If it is a public facing page, it would be interesting to see if I as a TL3 and @loopback0 get different results.
Filed Under: Science
-
You can get last 7 (and 30) days from here: https://what.thedailywtf.com/about
Where we still have lots of admins
-
Why would the about-page show statistics on hidden topics? Do PMs also get counted?
Filed Under: just asking
-
Why would the about-page show statistics on hidden topics? Do PMs also get counted?
Probably not, but the number fitted (at the time) the number @boomzilla quoted.
-
-
huh..... @Yamikuronue's Sekret PM Club sure makes a blip on that User to User msgs numbers....
Paging @RaceProUK too
-
is Time to first response?
-
Drilling in on it, the number is hours. I'm assuming it's how long before someone writes a reply to the OP (as opposed to just a Like). I've never noticed that before, but then I rarely look at the dashboard these days, so I'm not sure how long it's been there.
-
-
Eh...looks like someone asked for it:
https://meta.discourse.org/t/time-to-first-response-definition-please/30957/5?u=boomzilla
-
Also, after drilling down it can be filtered by category and date.
-
Ah, fair enough then I guess.
-
IIRC, you have stuff muted. Maybe that's contributing?
Nope; I have a lot of categories muted, including this one, and I don't see that behaviour.I'm only here because I was summoned.
-
I have a lot of categories muted
As do I, and the only time I see a wrong "New" count is when I end up viewing the category list for one or more of those Muted categories before returning to the main Latest list.
Or when someone makes a topic in a category I have Tracking, then the topic is "moved" into a category I have Muted.
-
It's just completely fucked.
It's been stuck at 433 New, 67 Unread for about an hour but I've read every unread post in at least 25 unread topics, and a few new topics too.Loaded the whole of both lists and counted (in Notepad++) and there are actually 521 New and 135 Unread.
-
is it still stuck "right this second" ? I am quickly impersonating you to have a look
-
Correct, still 433/67.
-
Given the sheer number of varying blue numbers all over the place-- all of them different and with different meanings-- I just assume that none of them actual work. Or are learnable. Or even if you learn them, their meaning will randomly change in a Dimple-Update. Or will break for the same reason (or for no reason at all).
I just assume they're white noise and ignore them. The Dreckshow equivalent of space.gif
-
OH my I just tried on your account and was able to reproduce the very nasty bug. You basically visit a topic to read it, then hit back and the counter jumps up by 100, hopefully this also happens on latest with the backup I have and then I can sort this out at last.
-
I know why it is so messed up for you loopback, we limit the query that checks for new/unread to 500 items, this protects us "somewhat" against flooding the client with data.
You have hit this limit hard, I can look at making the "limit" a site setting, if tracking 1000 new items is really a need, though I doubt there is huge value in a "new" item from 3 years ago.
Simplest workaround in your case is either to "clear new" OR change your user prefs to treat new only topics that are 2 weeks old.
Also, so much less work to do catching up on "new".
Honestly I am thinking of junking "I have not viewed them yet" as a proper fix here:
This setting is just trouble and is way better serviced using an advanced search filter.
-
This setting is just trouble and is way better serviced using an advanced search filter.
Actually, it's a bit useless to me now that we have the proper server-side
.visited
display...
-
@Kuro you are at 3619 "unread" items, I will add a site setting now for the cap, but there is a performance cost at allowing this to go unbound.
Any reason you do not clear your unread, or is this more of an inbox infinity kind of stretch goal :) ?
-
Actually, it's a bit useless to me now that we have the proper server-side .visited display...
not following ... something like
order:oldest state:never-viewed
as a search filter if you want to dig up very old crap you never looked at.
-
New is already wrecked for that use-case because you implicitly dismiss new (for haven't viewed them yet only) when you register.
So the search filter was needed anyways.
-
I know why it is so messed up for you loopback, we limit the query that checks for new/unread to 500 items, this protects us "somewhat" against flooding the client with data.
I'd not noticed they added up to 500. Surely all that needs passing back to the client is the number of topics though?
Also, so much less work to do catching up on "new".
I'll be ditching a lot of them at some point. Not immediately.
-
There is a site setting (in latest) that admins control the backlog size, I bumped it up to 1000, really we should not be carrying more stuff than that around cause there are perf implications to sending yet another array of 1000 things down to the client.
If you hit the threshold a warning pops up (in latest)
-
I'd not noticed they added up to 500. Surely all that needs passing back to the client is the number of topics though?
Not really, I need an array with information, that way I can reuse the info as you click around and go to a category or read a topic and so on. (this means that when you go to latest.json I don't need to re-count these numbers and that "live updates" work)
I keep track of which topics you have in an "unread" state, which are in a "new" state and your position for "unread" ones.
-
You mean "Unread" as in
Unread (502)
because
a) for me that always meant I had 502 topics with unread content
b) I never even look at the Unread tab. I have litterally not clicked that tab for about a year. It is not useful in this forum since topics derail at some point. So I have not dismissed them because I never even got close to the button.You mean "Unread" as in
New (1)
(even though it should be 0 but I didn't refresh, yet), because
a) I had a bug report withstanding for half a year so I didn't even want to mess with anything
b) The highest number I saw was 60 when scrolling down on the New page. I didn't even bother checking how many more would come because I assumed Discourse would ignore them anyway.
c) pretty sure the import added a number to those!
Maybe I just like big numbers!I can probably also set that one setting to something sensible like "things are only new for a few days" now that you mentioned it. I don't know what was the default here and how much I played around with the settings on the first day but to me, TDWTF-Discourse has always functioned this way.
Filed Under: Do I at least have the record with my 3619 unread items? @Sam / @PJH
since you guys over at meta.d INSTANTLY close all bug reports let me just add here, that you could probably make "Dismiss New" and "Dismiss Posts" in your blue banner clickable links! That would help people like me who never even look at those buttons and don't immediatly know where they are.
-
I think you hold the record for "unread" items not only for this site but pretty much every Discourse site I have ever seen.
People with more than 500 (new+unread) is probably less that 50 across the thousands of installs.
I reopened the topic for you and set it to autoclose in 48 hours so you have some time for extra feedback if you wish.
Keep in mind you can just flag stuff if you want it reopened, we respond to our flags real quick.
-
-
I think you hold the record for "unread" items not only for this site but pretty much every Discourse site I have ever seen.
#SoProud!
Just wondering: Am I actively generating cooties with this or is it just dumb?I reopened the topic for you and set it to autoclose in 48 hours so you have some time for extra feedback if you wish.
Keep in mind you can just flag stuff if you want it reopened, we respond to our flags real quick.
I kinda didn't want to bother you in two places at once so I figured since I already post a reply here, I might as well just append it with the useful stuff.
Did you already activate this update here, btw? Because Meta.d tells me I have too much stuff but TDWTF doesn't. (because apparently having 988 New over there is somehow frowned upon :D ) And the screenshot you showed over there was displaying Programmers-Testing!
Yeah that ... just click this...
To be fair, I knew where that was. It's just, since I never even go there, I never saw the need to click that.
Oh one more question, will clicking that also delete the numbers inside the little bubbles I see on the frontpage? Because I sometimes visit topics when the I see a number within a certain range, I think.
Filed Under: Still proud
-
Am I actively generating cookies with this or is it just dumb?
I think its just a bit of an odd usage pattern, it feels like you are tracking a big pile of stuff you don't really care to track. Especially now that we have the visited styling working right it seems unneeded.
Did you already activate this update here, btw?
Yeah meta is auto deployed each time the build passes, so the update is there. I do not update TDWTF though unless there is an emergency, we need to sort out all the customizations here prior to next upgrade.
-
we respond to our flags real quick.
(evil) Train of thought:
- the words "red" and "bull" arrive at platform 1, unannounced
- the fat controller sees "red" as "read"
- "bull is also bluster" meme arrives at platform 2, on schedule shortly after
- "read (pronounced 'red') an bluster" doesn't work says the guard.
- Ahh, but "read (pronounced 'reed') and bluster" does counters the fat controller
- "that'll do troll" says farmer Hoggett
-
Wha...