Too many things!
-
~4,500 people.
-
In my defense: I had no idea what dismissing posts would actually do. I thought it would just not creep up on unread/new anymore but we would still keep the bubbles / our posistion in the topic.
This was a case of getting sidetracked into crazy system behavior changes over something that was really a display performance issue.
-
Ohhhh, that's just beautiful.
-
-
-
-
And with inner counting you count by halves?
-
With Discourse counting you count by 2/5th and then subtract from 500....
Filed Under: But only if the Discotime%15 is 0
-
Or Arab, or Chinese, or any other RTL language user.
-
So was our reaction to this insanity what prompted the final discommunication? How dare we complain about destroying user data?
-
So was our reaction to this insanity what prompted the final discommunication?
It seems like it.
How dare we complain about destroying user data?
I know! What a bunch of Belgiuming assholes we must be.
-
one, two, many, lots…
-
400ms delay
Let it be known ladies and gentlemen, that the reason we are deleting your shit without your consent is that it will cost you an unfathomable HALF A SECOND
Never mind the fact that our stupid inner platform system where we abuse the browser's rendering engine and make it our bitch and reinvent the wheel in a javascript based "Rendering" "Engine" means you waste that much time even trying to get the next chunk of twenty posts to load in.
Fuck me sideways sam, is it difficult to remove the limit? Is it easier to delete everyone's stuff? Serious question here, is this work around (I guess you could call it that) because the real solution will take actual development effort or is this some ideology you are forcing on us?
-
-
So unread is no longer cleared on the user's behalf, but New is capped at the setting still.
-
So unread is no longer cleared on the user's behalf, but New is capped at the setting still.
....
and this wasn't the initial solution why?
okay so it's still not the nicest thing to do, but at least you're not destroying someone's read position just due to inactivity.
-
and this wasn't the initial solution why?
Because that required more than 0 seconds of thought. Or accepting that it's really just a work around for a different bit of shittiness that they're unprepared to sort.
The shitty thing doesn't need to mess with either New or Unread. At least it's configurable, I guess.
-
So unread is no longer cleared on the user's behalf, but New is capped at the setting still.
Great! Now they just need to push that out before they fuck-up the database with that retarded 1.4 rel-- oh they already fucked-up everybody's database? Oh.
What a piece of shit.
-
before they fuck-up the database with that retarded 1.4 rel-- oh they already fucked-up everybody's database?
How I wish I could tattoo this inside every developer's eyelids. Or directly on their lower intestine with a cattleprod.
Never destroy data
Never alter data by default
Always preserve existing behavior when introducing new code.
-
@Lorne_Kates said:
How I wish I could tattoo this inside every developer's eyelids. Or directly on their lower intestine with a cattleprod.
You could tattoo it to every inch of a Discodev but they'd still be too busy worshipping Jeff to notice.
-
You could tattoo it to every inch of a Discodev but they'd still be too busy worshipping Jeff to notice.
If I just tattoo it in the right shade of blue...
-
Fifty shades of blue?
-
Make sure to specify
border-radius: 100%
as well.