Short of proofreaders at Vulture Towers? :D
297 posts • joined 11 Jun 2009
I guess they were using a short integer of some sort to store the cache ID, which was intended not to overlap when it loops... unless the request is very delayed by a shitty connection?
Just use a UUID or similar, FFS!
Oh, and probably close the security hole where I can presumably insert someone else's cache ID into an unauthorised request.
"Jagex accused McCambridge of not showing "remorse for your actions or consideration for the injured party, instead suggesting the blame is that of the party for leaving the information on the printer"."
Is it even possible to 'suggest' something that's already bleeding obvious to everyone involved?
If I say "people should breathe in as well as out" you'd have to try pretty fucking hard to classify it as a "suggestion".
I already got my full £200 refund when they discontinued them. By then I was on my fourth replacement because the straps had a fatal flaw — right where the battery wires ran through. Anyone who needed another replacement from then was given a refund instead.
It's a shame since I absolutely loved that device. What I wouldn't do for a fully functional replacement with no strap flaw... :'(
Biting the hand that feeds IT © 1998–2020