If you do that you have to double the used web space, and that can be expensive. I'm already almost at the upper limit for my site and will have to go to the next tier of hosting soon. As it is, only three of the well over a hundred pages on my site need a special mobile version, and I would imagine a lot of other folks are the same way.

Having it first look for m.sitename, falling back to mobile.html if it exists and m.sitename doesn't, then index.html if there are neither m.sitename or mobile.html might be a good idea, though.

The dirty little part left unsaid by many is that they think being truly objective IS being a bad person.

I'd be preaching what I don't practice; my favorite phone was the Razr. Tiny thing. Big phones are fine for those who carry purses, but mine stays in my pocket. The one I have now is about as big as I can stand.

I'm about to post a journal with a suggestion for the W3C and mobile browser makers.

It should work. I don't see how it would mess up the charging circuit unless that circuit was poorly designed. It's the same as a TV degausser.

My day was a lineman working around AC at 90,000 volts. If he wore an analog (wind up) watch to work the watch would get magnetized by those high strength magnetic fields and stop working. He probably could have fixed the watches the same way.

I also agree with you. I do think we need to make a couple more considerations though.

First "those unavoidably out of town" should not be an excuse unless the distance between postal zip codes is greater than say 200 miles, and if the post marks indicate otherwise your ballot is invalid. That is the only way to prevent abuse.

Second right now it is possible for your boss to intimidate you into not voting and certain companies probably have a pretty good idea of the voting blocks their employees fall into. We need to be fair and make election day a National Holiday! So that everyone has the day off. We probably need to make exceptions for the groups for which anti-strike laws already exist, Health, Safety and infrastructure folks who potentially have to work the holiday. There also needs to be some kind of penalty for employees who try to ignore election day like its just another MLK day have have nonessential personnel work anyway.

I agree the only way to ensure any sort of integrity is to have people GO to the polls, but we need to make sure everyone can.

Why because using something different gives you a sense of superiority. AOL was an ad laden mess once it go big. It really was foolish to use it if you did not have to do so.

GMAIL's only real issue is privacy concerns. Which *is* a huge issue, but other services are far from immune to that as well; short of running your own mail server you can't really know and it does matter really because chances are the person you are mailing is using Google anyway.

The reality is GMAIL works well and meets a lot of peoples needs. It also has good IMAP support if you like a local client. So I don't judge GMAIL users to harshly, because I don't know where they could go that would be demonstratively better for them, unlike AOL users back in the day where there usually was clearly superior and obvious choice for anyone's specific use cases.

Yes, but back in 1993 its not like you could just Google it. If you were not attacked to some organization with access, and your local public library did not offer shell accounts or something the big name BBS services (with internet gateways) AOL, CompuServe, and Prodigy were usually the way to go. At least until you could find a local ISP.

Keep in mind most folks were at the time using DOS and Windows. So you also needed to bring some software to the mix, to do PPP etc. That stuff was no on the shelf at your local shop and it was not simple to figure out without online reference materials. The AOL diskette solved both problems.

Once you got online and found an ISP with local access numbers, got the trumpet winsock installed or downloaded Slackware you switched to a real ISP with local dialup numbers. AOL was a first step to something more than a local BBS even for a lot of us techies though, because it as available AND accessible when nothing else way especially if you did not have friends who could help you.

You think policy don't have procedures governing the handling and questioning of persons under arrest?

Miranda is a "due process" case. Essentially the court decided the process of questioning people before apprising them of their rights was unconstitutional. There is no problem with the act of asking a question.

I am sure you are right. The criminals would adapt quickly there are plenty of inexpensive packaging materials that could be used which be sufficient to defeat detection by a dog. The biggest challenge for drug packers would probably be developing handling protocol to avoid contaminating the outer packaging with product.

That does not need to be perfect either just 'pretty good' assuming the postal service/government deployed a detective device more sensitive than a dog it would have to be tuned down otherwise the false positive rate would be insane.

Did the guy working packing at the Amazon roll a J before coming to work? Think that canabis oil from his skin won't transfer in some quantity to the absorbent porous cardboard he handles?

I doubt TSA style x-ray scanning would work well either, I don't know how you could distinguish drugs from many perfectly legal frequently shipped substances. Its a difficult problem unless you are willing to raise the costs of parcel shipping to insane levels to pay for manual inspections and all the abuse, theft, and fraud that will entail

While I realize VMware isn't effected by this vuln;

Fusion can't boot a VM off USB (why the fuck is that?) So if I want to test a USB boot stick on my MAC I have to use this to chain load the USB sticks boot loader: https://www.plop.at/en/bootman...

Its pretty convenient to just keep a VM defined with a floppy and the plop disk always attached. It would be better if it could/would boot a USB device, but the virtual floppy is my work around.

Nobody can just own anything any more can they, nor can they accept we live in an imperfect world where mistakes happen.

An app developer should do their best to provide users with concise, but complete, accurate, and timely information to the extent the technology allows. Perhaps developers/vendors have some responsibility to set realistic expectation about the quality of the information, but that is as far is can possibly go.

Beyond that people/users just have to make decisions and bear the responsibility. If your counter terrorism intelligence app does face recognition and determines Jim on camera is really Oliver Public Enemy No.1, and Mr.Policeman shoots Jim, its Mr.Police man who is at fault unless your application was deliberately misleading or you mislead Mr. Policeman about the accuracy and confidence possibly with your app.

So were the record companies. Now amazon sells mp3 files without DRM.

DVD ripping is childs play, yet they still release their stuff on that format.

Grandparent is correct eventually they will give up, probably because the competition will be beat them. The competition being indie (which lets face it the CGI that talented folks can do in their basement now is better than what the studios did in the 90s.) and their own older unencumbered stuff, and again there is so so so much of that there really is no need to watch a 'new' movie in our own life times.

Its a damn good way to get busted as well. IDS sensors and SEIM systems will pick up on a small number of hosts performing a large number of authentication attempts or a large number of hosts making attempts against the same account.

Either way you going to at least tip off the site operator. If your target is a free webmail host or something there might not be much they could/would do but a corporate security team will probably alert the account owner, and watch that account very carefully, will other folks contact the lawyers and the authorities to hunt your ass down.

Honestly this should be pretty simple. The default operating mode of a password manager should be generate a password from PRNG data.

Store the value encrypted with AES a key derived from a master password extended via PBKDF-2 or similar should be used for the cipher.

Next apply the necessary mixture bitwise rules applied bytewise to the 'clear text' to ensure the password will contain type-able characters and accommodate character restrictions. (Something like x = ((x % 126); x = x | 32 if x 32; for those of us using ascii and yes its not perfect and will produce some bias maybe a crypto expert could propose a better alternative ) Store which rules must be applied as well. That should not be an information leak as the attacker probably can research the target system and divine these requirements anyway.

That will mean most of your passwords are nearly random goblody gook. (Important). No matter what master password is used a key can be derived, the decipher operations and the rules can be applied the result will appear to be a legal password, but it will be incorrect. In the event you have stored a specific less random value it should 'decipher' as well but appear highly random given that is how all your other password appear to be it will not be a strong indicator the wrong key has been chosen either.