Vote of No Confidence
-
Ever since Discourse was updated, roughly 900 threads I was tracking have been lost
I went from ~100 new/400 unread to 5 new/900 unread on the first page load post-update, and the next time I noticed I had 5 new/400 unread. I don't know where those extra 500 unread topics came from or went.
-
ignore me, discourse won't track this topic
So yeah, i used the dismiss posts button a while ago and now a bunch of topics that i want to track are marked as being tracked but not actually being tracked.so i'm posting to get discourse to recognize that it should track this topic again because discourse?! i said dismiss post not dismiss topic!
-
Set it to normal and then set it back?
-
tried. doesn't work.
i can set to watching and it watches the topic, but setting it back to tracking acts as if it's on regular.
posting in the topic seems to fix.
-
regular
Is it just me or has that changed name? I'm sure it used to be regular but... not now.
-
I think you got trustholed, dude!
-
And not sending the ID of every new or unread tracked topic down when loading the numbers for the counters.
Hey, let's not get carried away here.
On an unrelated note, is quote reply broken for anyone else? It keeps failing for me, almost like it's trying to make a trip to the server. Oh. Belgium. Please tell me they didn't do that.
-
it used to be regular and the keyboard shortcut and API name still says regular, so regular it is.
i'm sdure it got bikesheded recently to be "normal" because it was confusing with TL3 or something...
-
On an unrelated note, is quote reply broken for anyone else? It keeps failing for me, almost like it's trying to make a trip to the server. Oh. ■■■■■■■. Please tell me they didn't do that.
what? the trip to the server?
AFAIK it;s done that for a while now...
-
almost like it's trying to make a trip to the server.
Didn't it always make a trip to the server at some point during quote reply?
-
@abarker said:
On an unrelated note, is quote reply broken for anyone else? It keeps failing for me, almost like it's trying to make a trip to the server. Oh. ■■■■■■■. Please tell me they didn't do that.
what? the trip to the server?
AFAIK it;s done that for a while now...
Didn't it always make a trip to the server at some point during quote reply?
For full quote, yeah. But quote reply? Pretty sure that's new.
-
it used to be regular and the keyboard shortcut and API name still says regular, so regular it is.
i'm sdure it got bikesheded recently to be "normal" because it was confusing with TL3 or something..
It's hard to get annoyed about what is probably a 30 second change to rename a word and commit it. But the 30 second bikeshed ventures add up in Discourse to LOTS OF FUCKING TIME DISCODEVS COULD MAKE SHIT LESS BROKEN.
-
-
On an unrelated note, is quote reply broken for anyone else? It keeps failing for me, almost like it's trying to make a trip to the server. Oh. ■■■■■■■. Please tell me they didn't do that.
Testing.
-
Seems to work for me.
-
For full quote, yeah. But quote reply? Pretty sure that's new.
Not for the reply button to show up, but for the editor / quote to show up...yeah. I've had it stall on me...give up...start typing...typing wiped out with quote. Or multiple quotes show up as cooties allowee.
-
It's hard to get annoyed about what is probably a 30 second change to rename a word and commit it. But the 30 second bikeshed ventures add up in Discourse to LOTS OF FUCKING TIME DISCODEVS COULD MAKE SHIT LESS BROKEN.
And the 30 seconds is just the labor time. It's not the shedding time.
-
True.
-
Quick, everybody, tell me how Sam is God among software developers!
I'm pretty sure nobody ever claimed Sam is God among software developers, just that he's significantly better than Jeff. Of course, that's a very low bar to overcome.
-
can set to watching and it watches the topic, but setting it back to tracking acts as if it's on regular.
It wouldn't surprise me at all to discover that it's actually working 100% as designed, but the design is so convoluted and insane that literally only one person in the whole world understands how it's supposed to work.
It probably needs some toasters added to jeffsplain to you how you done fucked up, in the most condescending manner possible.
-
i said dismiss post not dismiss topic!
If you don't want to read it now, you'll never ever want to read it.
-
On an unrelated note, is quote reply broken for anyone else? It keeps failing for me, almost like it's trying to make a trip to the server.
It is taking several seconds to open the editor for me. This one was only about 3 seconds, but the last one took long enough that I had highlighted the text to try again before it finally opened.
-
that appears to be the case, because i di
@accalia said:
i said dismiss post not dismiss topic!
If you don't want to read it now, you'll never ever want to read it.
d the same thing in the nodebb topic and it fixed it for a while, but now we're on teh latest beta it's unfixed again.
-
Nice quote insertion.
-
I've had issues with image uploads hanging at 100% without inserting the image, which sucks for cupcake reasons.
I also am still having the edit-reply issue on my other PC, or was before the update. It just never cleared up.
-
-
..... DISCOURSE!<a
-
I went from ~100 new/400 unread to 5 new/900 unread on the first page load post-update, and the next time I noticed I had 5 new/400 unread.
You had far more than 500 new+unread; for performance reasons, only 500 topics are pushed to the client, and the numbering is based off that. After the update, you still had more than 1000 (new limit thanks to our staff) new+unread, so it desperately started un-newing things to try to get you under the limit. Fifteen minutes after your next visit, it started un-unreading things for you too to get it back down. You now have room for up to 600 more unread topics.Don't worry, you obviously didn't care about those unread topics; otherwise, why would you have so many? And if people post you'll (theoretically, but not in this reality, as proved by @accalia) get them back again...@tar said:
It probably needs some toasters added to jeffsplain to you how you done fucked up, in the most condescending manner possible.
It did. It's called the Kuro-bar. It got removed because we bitched about it, and got this shitfest in its place.
-
Not for the reply button to show up, but for the editor / quote to show up...yeah. I've had it stall on me...give up...start typing...typing wiped out with quote. Or multiple quotes show up as cooties allowee.
Yeah, that's what I've been seeing. Annoying as hell.
-
I noticed more unexpected behavior that I think is new. If you have more than one tab open (INB4 "Why would anyone ever do that? You're Doing It Wrong™." — Jeff), the blue notification circles in the tabs don't stay in sync. If you view your notifications in one tab, the circle in that tab disappears, but not in the other one. If new notifications arrive, the circle reappears and is updated in the active tab, but not the other one.
-
You had far more than 500 new+unread; for performance reasons, only 500 topics are pushed to the client, and the numbering is based off that
The numbers before the update didn't seem to be cut off though. I think when the Kuro-bar appeared it was a bit over 500 and I got it to just under (103/392 as of this post, somewhere around the same last night) before the update. Of course, anything is possible with Discomath so I don't know how accurate any of those numbers were or are now.
-
I noticed more unexpected behavior that I think is new. If you have more than one tab open (INB4 "Why would anyone ever do that? You're Doing It Wrong™." — Jeff), the blue notification circles in the tabs don't stay in sync. If you view your notifications in one tab, the circle in that tab disappears, but not in the other one. If new notifications arrive, the circle reappears and is updated in the active tab, but not the other one.
Shit. I thought I was just going crazy.
-
You had far more than 500 new+unread; for performance reasons, only 500 topics are pushed to the client, and the numbering is based off that. After the update, you still had more than 1000 (new limit thanks to our staff) new+unread, so it desperately started un-newing things to try to get you under the limit. Fifteen minutes after your next visit, it started un-unreading things for you too to get it back down. You now have room for up to 600 more unread topics.
The 1000 setting was prior to the update.
Yeah, that's what I've been seeing. Annoying as hell.
Cootie related, I've always assumed. Not new.
Filed Under: The spoon holder should know
-
I thought I was just going crazy.
You are. ;) But this is not a symptom of your craziness. (It might be one of the causes, though.)
-
@HardwareGeek said:
I noticed more unexpected behavior that I think is new. If you have more than one tab open (INB4 "Why would anyone ever do that? You're Doing It Wrong™." — Jeff), the blue notification circles in the tabs don't stay in sync. If you view your notifications in one tab, the circle in that tab disappears, but not in the other one. If new notifications arrive, the circle reappears and is updated in the active tab, but not the other one.
Shit. I thought I was just going crazy.
Me too.
-
The update doesn't seem to helped performance:
-
FUCK.
Another tab-related bit of Discuntery.Before the update - if I had many tabs, the number in brackets (new/unread shit) always appeared on the first tab only.
Now I have different numbers on different tabs. Presumably related to the notifications number being broken on tabs.
-
can set to watching and it watches the topic, but setting it back to tracking acts as if it's on regular.
What, I just pressed Reply to thread. Why is there even a quote there?
So anyway, performance seems as bad as ever, and all blue numbers are now basically lies. What the Discourse!
-
What, I just pressed Reply to thread. Why is there even a quote there?
If you highlight anything, any reply becomes quote reply.
-
Not (usually) with the blue "Reply to thread in general" button... Hmmm... I'll have to see if I can repeo...
-
- highlight a word or phrase
- use black "reply to individual message" button
- observe quoted text
- cancel the reply
- click "yes, abandon" in the discodialog.
- start a new reply using the blue " reply" to thread button.
- observe quoted text from your abandoned reply still appears in the reply composition window.
- marvel at how atwood gets paid for this wretched software.
Edit: although I am on mobile, so that's different.
-
- Has anyone found out if we can actually move, and, for instance, finished importing the likes thread?
-
details>*, details .lightbox-wrapper { display: none; }
That rule is in Discourse Default. A fix for TDWTF Default:
details[open]>*, details.open>* { display: block; }
-
Well, if you can preserve your text selection, it happens on desktop as well.
-
- Well, it's better than it was, at least.
- I mean, it was pretty hilariously bad before.
-
Weird, I've seen that details thing work before, and I've always been on TDWTF default.
-
I assume it got broken in the update. I was suggesting a rule to put into our CSS to fix it.
-
Details worked earlier - @accalia used it in a post and it worked there.
-
Better rate limit messages, coming Discosoon™.
-
Ah, because of the use of a <summary> tag as well. They have rules to make it so anything inside an open details block that contains a summary shows:
details[open]>summary:first-of-type ~ *, details.open>summary:first-of-type ~ * { display: block; }
I'm still gonna because contents under a <details> tag without a <summary> tag should still just work.