:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
-
Post can't be empty
Yeah this forum really is retardedAlso can't quote a post with only a picture via highlighting. QA really would of caught that faster...
Jeff 25/09/23 07:55hr Cunt Cunt Hi Sam, its Jeff. I won't be in today. Got an awful dose from the prossie after the party last night. I'm going to be spending most of the day at the clap clinc. I'll be ashen faced but I'll see you to tomorrow. Have a nice day!
-
What are you waiting for? We got bugs to report!
-
What are you waiting for? We got bugs to report!
-
Either their new invite setup gives a workaround to blocked emails and IPs, or they forgot to completely block me when they anonymized me. I don't know which to believe.
Also....do you have a static IP? I know I don't. Will be fun to see how long it takes for them to notice you.
-
Will be fun to see how long it takes for them to notice you.
I'm sure that Allan Bill Arker doesn't know what you're talking about.
-
Raise your hand if you didn't see this coming:
Called it:
-
I'm relatively sure they won't to it nilly-willy.
Not after seeing what the Sekret PM Club is up to, anyway ;)
-
Also....do you have a static IP?
At work, where I recreated the account from, yes.
Will be fun to see how long it takes for them to notice you.
Indeed.
-
Are you doing naughty things on our forum? ;)
-
-
So, I thought the Kuro-bar was only suppose to appear if you had more than 500 new and unread threads, but I clearly don't, yet here is still is... is this just another example of Discomath?
-
It's probably counting your muted categories or something equally Discosensible.
-
I don't think I have any muted categories. Is that possible to check? *shrug*
-
It's probably counting your muted categories
It specifically says tracked topics. A muted category is not tracked. Of course, that doesn't necessarily mean Discourse isn't doing something stupid and contrary to what it says on the tin.
-
I expect unread
PMs count?
-
Disregard, I misread.
-
2 posts were split to a new topic: Ban
-
How about @loopback0? He was TL4 at some point..?
-
I'd wager DiscoMath.
-
Yeah, Disco500.
-
Null 500 [500]
-
You grew a mustache?
-
@loopback0 said:
You grew a mustache?
Shhh! He's probably wearing a disguise! We should pretend that it's working and let some "secrets" slip. ;)
-
Or maybe it's covering a secret?
-
IIRC, Sam explained it before The Shunning. The bar appears when you hit 2/5 of the threshold (500). ... or something. Why you would not just set the threshold to the value where you want the bar to appear I don't know, but apparently the 500-limit is so dangerous that no-one must ever cross it.
-
After 500 posts, unread tracking behavior may become inconsistent, performance may be sporadically degraded, issues may occur in the text editor, and the site may go read-only for minutes at a time.
-
After 5
00posts, unread tracking behavior may become inconsistent, performance may be sporadically degraded, issues may occur in the text editor, and the site may go read-only for minutes at a time.FTFY
-
Indeed. Indeed you did.
-
IIRC, Sam explained it before The Shunning. The bar appears when you hit 2/5 of the threshold (500). ... or something. Why you would not just set the threshold to the value where you want the bar to appear I don't know, but apparently the 500-limit is so dangerous that no-one must ever cross it.
No, the bar appears at the threshold. In the latest - which I believe we don't have - the auto-dismissing works to keep new posts at 2/5 of the max and unread at 2/5 of the max. Which makes the max not much of a max since 20% of it goes unused on most forums.
-
After 500 posts, unread tracking behavior may become inconsistent
But it always says "500 OK" to me in those helpful pop-ups.
-
@Gribnit said:
After 500 posts, unread tracking behavior may become inconsistent
But it always says "500 OK" to me in those helpful pop-ups.
There's also 504 OK. I guess that's disco500. Or....discook or something.
-
No, the bar appears at the threshold. In the latest - which I believe we don't have - the auto-dismissing works to keep new posts at 2/5 of the max and unread at 2/5 of the max. Which makes the max not much of a max since 20% of it goes unused on most forums.
So, in order to spare you the indignity of having over 500 unread threads, Discourse will start arbitrarily marking unread threads as read, and this is somehow to be interpreted as an improvement in the affairs of Discourse?
Why not just only mark threads as read if you've actually read them?
-
So, in order to spare you the indignity of having over 500 unread threads, Discourse will start arbitrarily marking unread threads as read, and this is somehow to be interpreted as an improvement in the affairs of Discourse?
No, to spare you the indignity of having over
2/5 × y
[1] unread and over2/5 × y
[1] new threads for more than 15 minutes (IIRC, that's how often Dicksores does the auto-dismiss). Round these parts2/5 × y
is 200, but since we don't currently have that feature, it doesn't much matter.Why not just only mark threads as read if you've actually read them?
Because the @Kuro-bar was embarrassing @sam. This forum's vehement opposition to this hack (expressed on this forum) seems to have stressed @sam out a bit just before the mass banning at meta.d. It may have contributed to his willingness to go along with Sir Twatwood's plan.
[1] Where
y
is the maximum number of permitted new and unread posts. The default value fory
is 500
-
Whether or not it happens, who knows, but @sam did suggest he was going to just remove it and let people deal with their own shit taking a bit longer to load if they had "too many" things tracked.
-
@tar said:
Why not just only mark threads as read if you've actually read them?
Because the @Kuro-bar was embarrassing @sam.
OK, and with full awareness that I'm probably approaching this with entirely the wrong mindset—unless they're performing a single very expensive database query per unread thread on every page load, then it's hard to see why 501 unread threads is significantly worse than 499 unread threads. And in any case, why not just profile the damn thing to find out what the bottleneck actually is, and then fix that? I'm just trying to understand how they get from "too many unread threads" to "zOMG we need to start making the unread threads as read it's the only solution you guise!"
Maybe there is no satisfactory explanation. Maybe there is only Discosplanation.
-
The best explanation you'll get is in the Too Many Things topic.
-
unless they're performing a single very expensive database query per unread thread on every page load, then it's hard to see why 501 unread threads is significantly worse than 499 unread threads. And in any case, why not just profile the damn thing to find out what the bottleneck actually is, and then fix that?
Part of it was that the server sent a list of all unread/new topics to the client, so he more tracked topics, the bigger the list.Somehow they care about that, but not the list of EVERY SINGLE POST ID IN THE TOPIC which gets sent down when requesting a single post.
-
Somehow they care about that, but not the list of EVERY SINGLE POST ID IN THE TOPIC which gets sent down when requesting a single post.
Soon coming to a discourse near you:
- Topics over 1000 posts are locked automatically. Only admins can post.
- Topics over 1100 posts are locked automatically. Even admins cannot post.
-
@loopback0 said:
Somehow they care about that, but not the list of EVERY SINGLE POST ID IN THE TOPIC which gets sent down when requesting a single post.
Soon coming to a discourse near you:
- Topics over 1000 posts are locked automatically. Only admins can post.
- Topics over 1100 posts are locked automatically. Even admins cannot post.
More like when a topic is over 1000 posts the oldest posts get deleted as a new post comes in.
-
Or when it hits 1000 posts the oldest 500 are moved to an archive topic?
-
Or when it hits 1000 posts the oldest 500 are moved to an archive topic?
Deleting user's data without their permission seems the more Discourse way of doing it.
-
Or when it hits 1000 posts the oldest 500 are moved to an archive topic?
Like ... a new page in a notebook?!
-
Like ... a new page in a notebook?!
Nononononono, why would you even think that? Technophilic weirdos. You split something off and they immediately start calling it pages.
Ugh.
-
Technophilic weirdos.
Interesting, I didn't think I'd ever see something that acts as a 'you should go watch Serial Experiments Lain again' trigger.
-
I am quite sure I have no idea what you are talking about. I made up the word 'Technophilic' on the spot.
-
Well, it conjured up images of Lain wearing her thousand computer cables.
-
Somehow I envisage SHODAN at this point.
-
wearing her thousand computer cables
To each his own fetish, I suppose.
Filed under: cat5 cables now available at your nearest sex shop, strip it for me baby
-
There's also 504 OK. I guess that's disco500. Or....discook or something.
504: HTTP code used by the Discourse server to indicate that everything is OK and that the client JS should pop up a dialog box to tell you about this. Rumours that this is a gateway timeout are scurrilous devilry put about by the W3C, trying to deny the truth of Civilized Discourse!<feel free to discopedia this if you want>