Plugins generally are heavy weight and slow. A few still retain much goodness. After the terrific plugin YouTube Options shot themselves in the head by charging a ridiculous monthly fee a new one emerged called Magic Actions for YouTube. It is a super useful plugin and I like it except for one thing. They decided upon the super-idiotic route that flash control panel took; you change options from a live web site. They do this for several reasons. It allows them to advertise more easily and they can more obnoxiously beg for money. Fortunately I only have to go there a once or twice a month to change things. The other annoyance is they add a toolbar beneath the youtube window which I never ever have had a reason to use and they refuse to let you disable it. Like I can’t remember I am using your plugin? Oh that’s right you put it there for more subscriptions to your YouTube channel. Shameless.
These are my must have plugins:
Youtube switched from Flash video as default to HTML5 as default. This is one more welcome nail in the Flash coffin. However, we lost video larger than 2k (1080p) and WebM container format via the VP9 codec does not look as good. It looks good but the difference is noticeable. Sorensen Spark is superior. This is coming from a tried and true Flash hater. I can rant about browser plugins forever.
But I digress … Chrome consumes gobs of memory. This is a screen shot of the memory usage after running Chrome for five minutes.
As you can see Chrome is using a ton of memory. This is absurd. I also see millions of there error messages in my logs:
kernel: Google Chrome He (map: 0xffffff80bb8b21e0) triggered DYLD shared region unnest for map: 0xffffff80bb8b21e0, region 0x7fff94e00000->0x7fff95000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.
I had to finally resort to disable the error reporting as my logs became useless:
$ sudo sysctl -w vm.shared_region_unnest_logging=0
Google, please fix this crap. Your features deployment have overtaken your stability. I really don’t want to have to switch back to Firefox. I really don’t.
In less than a week after creating a Disney account these are the domains I have received email from:
I’m looking forward to even more email.
This has been happening for days.
I’m so sick of it. I’ve stumbled across tons of 404s on their site as well. Page render times are terrible as well. Sometimes 20 to 30 seconds to render a page. Trying to plan your trip using their tools is pretty painful. Their pages are in no way optimized. Look at this one stat:
3578 rules (87%) of CSS not used by the current page
There are other horrific examples.
I had to call tech support for My Disney Experience to get our accounts to be able to access a single itinerary. The CSR told me that most people just share a login.
What is with go.com for all their sites. Seriously how does it help SEO, no one remembers you use go.com for anything, give it up already. It is a horrible idea that should be long retired at this point.
In terms of password security, they don’t allow non alpha-numeric characters to be used. They allow four character passwords of all lower case numbers or letters. They allow 1234 as a password. Yikes. The password recovery tool sends email and it comes from a twdc.com domain which is not immediately recognizable although they do a domain forward to thewaltdisneycompany.com if you investigate a little. They really should have an immediately recognizable domain for email. The best part is in the footer they say the following:
Copy and paste firstname.lastname@example.org into your address book to ensure optimal receipt of these communications.
Talk about a mess for people who like to have some semblance of email security. The worst security is probably over the phone. The only thing they verify a caller against is the name and address on the account. They then tell you the current email address and ask if you if that email address is correct.
They also still have SSLv3 enabled which makes them vulnerable to POODLE attacks. The certificate uses a weak signature, SHA1. Perhaps upgrade to at least SHA2. This server accepts the RC4 cipher, which is also weak. The server does not support Forward Secrecy with the any browsers i tried. Disney … get it together.