In which Apple destroys my daughter’s iPad forever

151–152 of 152 posts

Re: In which Apple destroys my daughter’s iPad forever

#151

Post by madaxe_again » Wed, May 23, 2018, 11:04 PM UTC

pdkl95 wrote: post #88

cannam wrote: post #22

Oh, this is a painful topic. A couple of years ago my son forgot the (3-digit!) PIN for his iPod touch. He tried various possibilities, with the device responding with increasingly long lockouts between attempts, until it locked him out permanently. I'm not an iOS user and I had no idea it would do that. I am still angry that it did. It wasn't associated with a Mac, so we couldn't unlock it that way. He eventually sh…

> forgot the ... PIN Schneier on passwords[1]: >> Simply, people can no longer remember passwords good enough to reliably defend against dictionary attacks, and are much more secure if they choose a password too complicated to remember and then write it down. We're all good at securing small pieces of paper. I recommend that people write their passwords down on a small piece of paper, and keep it with their other val…

I keep a few critical passwords in my wallet - but they’re encrypted - simple OTP type cipher I can hand crank in a few minutes - but useless to anyone who finds the scrap of paper covered in cryptic utterances.

Re: In which Apple destroys my daughter’s iPad forever

#152

Post by askmike » Fri, May 25, 2018, 11:42 AM UTC

nailer wrote: post #78

askmike wrote: post #75

Earlier quoted context omitted.

I'm not saying to hammer down the refresh button. And yes there is a very good reason for it too work: in most scenarios the amount of concurrent connections to the DB is at the limit. If you refresh once a minute later you're really not that much of an impact while the PHP instance might get the handle to the database needed to fetch the content. As a matter of fact, it worked for me with this exact article.

> Try refreshing, eventually that worked > I'm not saying to hammer down the refresh button. OK. > If you refresh once a minute later you're really not that much of an impact If every user does this, the site now has 2x the amount of incoming requests.

Yep but twice the amount of incoming requests spread out over time.

When the site doesn't load I think it's fair to do either 1 of 2 things:

1. Accept that you can't read the article.

2. Have some kind of retry mechanism ( for example: https://aws.amazon.com/blogs/architecture/exponential-backof... )

But I don't think trying once and complaining about it in a comment is making anything better for anyone.

Post reply on HN