@[email protected] to Ask [email protected] • 1 year agoWhat's a company secret you can share now that you no longer work there?message-square931fedilinkarrow-up11.12K
arrow-up11.11Kmessage-squareWhat's a company secret you can share now that you no longer work there?@[email protected] to Ask [email protected] • 1 year agomessage-square931fedilink
minus-square@[email protected]linkfedilink18•1 year agoYou responded to the wrong comment, but i’ve been seeing that a lot so I wonder what causes it.
minus-square@[email protected]linkfedilink13•1 year agoBeing a frontend dev myself, I’d guess someone screwed up the indexing of comments :P
minus-squareJackbyDevlinkfedilink7•1 year agoSounds like a DHCP issue. (I mean, not really, but it rhymes I guess.)
minus-squareDark ArclinkfedilinkEnglish1•edit-21 year agoI’d actually wager the comments are cached, sent to the front end wrong (because of the bad cache), and then the front end posts against the wrong comment ID (maybe that’s what you mean to be fair :) ).
You responded to the wrong comment, but i’ve been seeing that a lot so I wonder what causes it.
Being a frontend dev myself, I’d guess someone screwed up the indexing of comments :P
Sounds like a DHCP issue.
(I mean, not really, but it rhymes I guess.)
I’d actually wager the comments are cached, sent to the front end wrong (because of the bad cache), and then the front end posts against the wrong comment ID (maybe that’s what you mean to be fair :) ).