Another commonplace annoyance is sites of no consequence that ask for an email address and for some unknown reason require it to be entered twice.
Some site probably tested it and found that it reduces the number of registrations that fail to complete because the user mistyped his e-mail address and thus failed to receive the registration confirmation e-mail message. Then other sites copied it.
If you are writing software that takes in a password and you are hashing the password to compare it to a stored hash, there is no reason at all to restrict the maximum length of a password or prohibit certain characters from being used in it.
Other than that it's far harder to type a 60-character password on a mobile device whose only text input method is a flat sheet of glass. Allowing users to enter a long password discourages users from even trying the mobile site or mobile app.
If you are writing software that takes in a password and you are NOT hashing the password (but instead storing it in the clear or otherwise doing something with it), you shouldn't be writing software involving passwords in the first place
Unless you're storing the user's password in order to log on to a service on the user's behalf. A password manager is an example of such an application. With other applications, even if the service supports some form of OAuth, the application still has to somehow store the client ID, client secret, and user token securely.
Mozilla in all their wisdom decided to remove those options when they removed the settings to disable JavaScript all together. I'm not entirely sure what the rationale for that decision was
Possibly to reduce the cost of supporting users in case Firefox extensions and Firefox apps do not work correctly when JavaScript is turned off.
"You could have always not used the website for finding housing." Then you'd run afoul of the city's sit/lie law. My point is that governments forcing people to use a particular private-sector service can be less direct and more subtle than one might initially think.
non-repeating characters (in fact it reduces entropy by some security admins seems to think it is a good idea), numbers and so on.
If there are 64 choices for each character, a requirement for non-repeating characters reduces the number of choices for characters after the first to 63, for a total of -log[2]((63/64)^9) =
The password prompt on Frontier DSL router administration page blocks both the clipboard and usage without JavaScript.
Famiclones appeared prior to 1997 when NESticle became usable.
Whatever site powers the Share button.
the Chinese are great at pirating software. Hardware was the real hurdle.
If you know what a "Famiclone" is, you might see why it's not too much of a hurdle.
Let me spell it out: Intel probably is having a hard time figuring out how to release a Direct Rendering Manager module that upholds its Digital Restrictions Management obligations.
Intel has yet to release the inteldrm module for Broadwell chips.
Let me hazard a guess why:
"the inteldrm module"
"inteldrm"
"drm"
Digital restrictions management strokes again.
and then swap to it
the links GP provided are for RAM disk cards which can only be used as storage, not as system RAM.
I intended "and then swap to it" to mean that the external storage would be used to hold a page file, which in effect augments your system RAM. But because it's RAM, it wouldn't have quite as much slowdown as swapping to a hard disk.
"Attempts to download high traffic release files from this server will get a '550 Permission denied.' response." Yet you managed to download the ESR.
You hid a lot of the log with "(...)", including the part where you navigated within the pub directory. Did this "(...)" contain any "550 Permission denied." responses?
Perhaps downloading the ESR worked because apparently Mozilla doesn't consider ESRs to be "high traffic release files". So I guess you have to download the ESR (47 megs) and then use that to download the current version (another 47 megs or so).
or at the least, download firefox using ftp.exe
I thought Mozilla removed releases from ftp.mozilla.org and disabled the FTP protocol on releases.mozilla.org. From messages that I get while logging in to ftp.mozilla.org anonymously:
releases.mozilla.org now points to our CDN distribution network and no longer works for FTP traffic
[...]
Attempts to download high traffic release files from this server will get a "550 Permission denied." response.
Computers are useless. They can only give you answers. -- Pablo Picasso
