@[email protected] to Ask [email protected] • 2 years agoWhat's a company secret you can share now that you no longer work there?message-square929fedilinkarrow-up11.14K
arrow-up11.12Kmessage-squareWhat's a company secret you can share now that you no longer work there?@[email protected] to Ask [email protected] • 2 years agomessage-square929fedilink
minus-square@[email protected]linkfedilink19•2 years agoYou responded to the wrong comment, but i’ve been seeing that a lot so I wonder what causes it.
minus-square@[email protected]linkfedilink14•2 years agoBeing a frontend dev myself, I’d guess someone screwed up the indexing of comments :P
minus-squareJackbyDevlinkfedilink8•2 years agoSounds like a DHCP issue. (I mean, not really, but it rhymes I guess.)
minus-squareDark ArclinkfedilinkEnglish1•edit-22 years 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.)
It’s definitely DNS.
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 :) ).