@CaspianXI@lemmy.world to Ask Lemmy@lemmy.world • 1 year agoWhat's a company secret you can share now that you no longer work there?message-square952fedilinkarrow-up11.36Karrow-down114
arrow-up11.34Karrow-down1message-squareWhat's a company secret you can share now that you no longer work there?@CaspianXI@lemmy.world to Ask Lemmy@lemmy.world • 1 year agomessage-square952fedilink
minus-square@esadatari@lemmy.worldlinkfedilink28•1 year agoeh DHCP isn’t really important right? obviously if it hasn’t changed since the 80’s why would you need to reboot your server. what are vulnerabilities?
minus-square@fuklu@lemmy.fmhy.mllinkfedilink21•1 year agoYou responded to the wrong comment, but i’ve been seeing that a lot so I wonder what causes it.
minus-square@bleistift2@feddit.delinkfedilink16•1 year agoBeing a frontend dev myself, I’d guess someone screwed up the indexing of comments :P
minus-squareJackbyDevlinkfedilink8•1 year agoSounds like a DHCP issue. (I mean, not really, but it rhymes I guess.)
minus-squareDark ArclinkfedilinkEnglish2•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 :) ).
eh DHCP isn’t really important right? obviously if it hasn’t changed since the 80’s why would you need to reboot your server.
what are vulnerabilities?
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 :) ).