CaspianXI@lemmy.world to Ask Lemmy@lemmy.world · 2 years agoWhat's a company secret you can share now that you no longer work there?message-squaremessage-square957fedilinkarrow-up11.36Karrow-down114
arrow-up11.35Karrow-down1message-squareWhat's a company secret you can share now that you no longer work there?CaspianXI@lemmy.world to Ask Lemmy@lemmy.world · 2 years agomessage-square957fedilink
minus-squarefuklu@lemmy.fmhy.mllinkfedilinkarrow-up22·2 years agoYou responded to the wrong comment, but i’ve been seeing that a lot so I wonder what causes it.
minus-squarebleistift2@feddit.delinkfedilinkarrow-up17·2 years agoBeing a frontend dev myself, I’d guess someone screwed up the indexing of comments :P
minus-squareJackbyDev@programming.devlinkfedilinkarrow-up10arrow-down1·2 years agoSounds like a DHCP issue. (I mean, not really, but it rhymes I guess.)
minus-squareDark Arc@lemmy.worldlinkfedilinkEnglisharrow-up2·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 :) ).