Hyundai – Never Again

Posted on April 13, 2018 by bluedepth

This tale of woe begins in October of 2015. I take my 2007 Hyundai Santa Fe into Maple Hill Hyundai for an oil change, and I learn about a service campaign, there is a recall on the Valve Cover Gasket for all Santa Fe’s like mine. Maple Hill performs the operation; I get a new gasket and a new alternator and the oil change. I drive away happy; everything is back to normal.

At the end of 2017, I start noticing some odd lights in my car, and generally odd behavior starting to crop up. I’ve got 130000 miles on the vehicle, so I figure that it’s cold weather and old age. The gas tank needle gets daffy, not registering full tanks of gas, so I use the trip-o-meter to measure out 200 miles and then fill up from there. I can adapt. Then on really cold mornings, I notice the battery light flickers for a little bit, alternating with the seatbelt light, but after a few minutes both go out. I drive it around, and everything is normal.

Then we went to Chicago, Illinois to C2E2. The Santa Fe loaded with suitcases and comic books, I drive it into the parking structure, and that’s that. We have a wonderful time in Chicago, and then we pull it out of the parking structure. I notice that the battery light and seatbelt light have started to blink, but then it goes away and I figure that it’s business as usual. I drop off my niece and her boyfriend at their car and then drive off. As I approach the highway, the battery light and seatbelt light continue to flicker. We get on I-94, headed back to Michigan, and right after we cross from Illinois to Indiana, the battery light is on. Then TPMS, BRAKE, ABS, AIRBAG, all the lights turn on and Check Engine comes on. Then the lights get dimmer and dimmer, and we roll into a Walmart parking lot.

I’m panicking. My car is dying, I’m 125 miles from home, and it’s late Sunday night. After I chill out in the Walmart, we get back to the car, and I turn it on. Check Engine is still on, but everything else is off, and the car is behaving like everything is fine. So we tool around the parking lot a few times, and everything remains fine. So I get on the highway again. We get 25 miles down the road, and then the battery light starts to blink. Then again, everything goes downhill. The car gradually slows down, until I’m pretty much just crawling along on idle speed, the gas pedal is hilariously worthless. We turn a few times and get right up to the parking lot of an Econolodge. All that is left is one tiny little lamp in the instrument cluster, and it’s half-lit anyhow. The car is fully dead. Transmission is stuck in everything but park, and so I get out, and with Scott’s help, we try to push the Santa Fe up the little incline to the parking lot of the Econolodge Hotel. A stranger appears out of nowhere and runs over and asks if he can help, and all three of us push the Santa Fe to the middle of the empty parking lot. I turn the car off, but the panic sets in again because I can’t put the transmission in park. I wait a few minutes and try to turn the car on, I get accessories to come on, and the transmission goes to park. I turn everything off and get a room at that Econolodge.

Now, here is where we place a mental pin in the tale, keep this spot in mind because what happens next is full of consequence.

I wake up the next morning, I don’t know what is wrong with my car, and my first idea is to see if I can find a repair shop. There are lots of auto dealers around, there’s a Kia, there is a Chevy, and a Toyota, but no Hyundai. So I figure I need some sort of shop, so I search Yelp for “auto repair,” and I find Adam’s Towing and Service of Porter, Indiana. I call them, reach Adam, and tell him what happened to my car. He suggests that it’s the alternator and I ask for a tow so he can work on it. The tow guy comes, super amazing fellow, and they get my Santa Fe on the skid and tow it away. I follow after in a rental car I picked up from an Enterprise location in Burns Harbor. We get to Adam’s shop, and they start working on it. I take the rental back to Kalamazoo and drop off everything; we get a call from Adam, my car is ready. He replaced the Serpentine Belt, and the Alternator and everything is back to normal. We get back, drop the rental car and pick up the Santa Fe and drive it back to Kalamazoo. Everything is back to normal. While talking to Adam, he asks if there was anything about motor oil with my car, because the alternator was soaked with oil and that’s why it died. I remember back to the service campaign that Hyundai performed and immediately do a Google Search, and many other people have had the gasket go out on them and struggle with Hyundai about repairs. So I’m thinking that’s what is going on with my Santa Fe. I go to Maple Hill Hyundai, and I learn that the job cannot be cleared because the leak is coming from the Timing Cover Gasket and that repairing that is a $1200 to $1600 process. For me, that totals the Santa Fe.

So then I start talking with Hyundai Corporate, talk to many people about my problem, and I believe that the problem is still the valve cover gasket. That motor oil that was inside my engine got outside and killed the alternator. I’d like my money back from the repair job, and I’d like someone to fix the gasket, just like Hyundai did in October 2015. Just like all those other Santa Fe owners who had this EXACT SAME PROBLEM.

So then, after being told that it wasn’t covered by Maple Hill, I reached out to another shop where I had my brakes done previously and brought it to them. The owner said “How do they know where the leak is, did they clean the side of the engine and run a dye test?” and the answer is no. While we had the hood open, he also pointed out that the plastic cowl that covers the engine was missing nuts, and one was cross-threaded and abused badly by a torque driver. But I don’t know who did it, so who is to blame? Haven’t a clue, but there are only three shops in this tale, Maple Hill, Adam’s, and the place where it sits now.

So then this morning I call Hyundai and I relate the tale to the rep, updating with my misgivings about which gasket really is the problem, and that I want proof that it is either the valve cover gasket or the timing cover gasket, and that I don’t want my money back from the alternator fix, but I really want to prevent this from happening again because I want my car to work for me for a while longer if I can manage it. I relate the tale, and then when I mention Adam’s Towing and Service and the shop that will wash the engine block and run the dye test, the Hyundai rep stops me and tells me that I can stop right there. Hyundai refuses to honor any warranty, expressly or implicitly formed because I took my vehicle to an Independent Repair Facility. So, go back to the pin I mentioned about the momentous choice I made. I was stranded on the highway, no warranty from Hyundai, no clue it was the gasket, and so because I didn’t push the vehicle to a Hyundai dealership, I’m quite shit out of luck.

So that’s the end of it. Hyundai walks away, from a service campaign that they botched, maybe, how can anyone tell? Nobody but the IRF even mentioned cleaning the engine and running a dye test! And what burns the most is that while I was regaling the Hyundai Corporate Rep with my tale of suffering, she searches for a Hyundai dealer in Chesterton, Indiana. Norris Hyundai. She then proceeds to waggle this Hyundai dealers location in my face, over the phone. If only I had pushed my dead 2000 pound Santa Fe to Norris Hyundai, then maybe Hyundai would talk to me. But because I was in the middle of the dark, with a dead car, work on Monday, and all the other stress, that I didn’t search for Norris and I didn’t PUSH MY CAR THERE, that there is nothing left to talk about and that I should have a nice day.

So I am done with Hyundai. I am done with the brand; I’m done with Maple Hill. There is no point in calling Fox Hyundai or Norris Hyundai, or anyone else. Hyundai only has one thought, and that is to hide in their fine print and treat me with such disrespect that it takes my breath away. They have no interest in their customers, no interest in repairing what is their fault. So I’m going to find out since it doesn’t matter now, I’m throwing in all the way with my new repair shop. This fellow will wash the side of the engine block, add the dye, and give me an authoritative answer as to which gasket is leaking. And then I’ll face the question of what to do from that point forward. It will answer the question, is it the timing cover gasket or the valve cover gasket? And if it is the valve cover, I might pay to have this new fellow do the work.

It is clear to me that Hyundai is uninterested in being human to me. They want to be a company, and that is their prerogative. It is my choice to associate with humans or companies, and I make my choices based on what I perceive to be the humanity of whom I am dealing with. Hyundai hides behind their fine print and their rules. That’s perfectly fine. I don’t want anything to do with a company like that. And if that means that I burn all the bridges to all the automakers in my life, then so be it. I have to make a stand, and I will live with the consequences. I will fucking walk if I have to. This deep violation of the Golden Rule is so upsetting to me that I cannot even see straight, so that’s fine Hyundai, hide behind your fine print and your rules and utterly fail to treat others as you would have them treat you.

There is a place in hell for you, and the punishment for a company is expressed regarding karma. You deserve what you get.

Assert The Win

Posted on June 10, 2016 by bluedepth

Sometimes it’s the best thing to assert you win and walk away from a toxic problem. So far today I’ve done that quite a bit. What have I abandoned?

I’ve walked away from Facebook. It’s been four days since I even logged into Facebook and since then I haven’t missed it. I’ve been catching up on my news; the Spiceworks Community board consumes a lot of time. Then after that, I turned my attention to my Pocket list. There just isn’t enough time anymore to deal with Facebook. When I logged into it, I had eighteen notifications, and I frowned and realized that I didn’t care that much. I’m writing a lot of my thoughts into my journal after coming to the realization that sharing with others isn’t going to be a positive experience. Now nearly everything on Facebook is an unpleasant experience. So, abandoning toxic things seems to be a good thing for me.

Another toxic system is Office365. Microsoft and I go back for a long while, right along with my almost palpable hate for that company and their products. Going into just how Office365 lets me down is very dull. Nearly every interaction has me wishing I could just close my laptop, put it in my backpack and run away from my life. Everything that has some Microsoft technology associated with it has me frowning in deep disappointment. Alas, there is no way to escape the Great Beast of Redmond, so we gnash our teeth and endure the horrors.

The final horror is WordPress itself. I use a stock theme, Twenty-Twelve. It’s not a custom theme. It’s not slick or responsive. It’s just a dumb theme. So while reading my blog, I realized just how much I wanted to change the line-spacing for my post entries. This is where my expectations fork, there is an Apple fork and an “Everything Else” fork. The Apple fork has been proven time and time again, that the answer is simple and shallow and easy to get to, understand what the change will do, and make it work. Then there is everything else. Here we have WordPress itself. I wanted to change the line-spacing on my theme. So I go to the Dashboard, and I spend ten minutes blindly stabbing at possible places where this option might be hiding to no effect. Then I do a Google search, which is the first and last place that most possible solutions are born and die. A good Google search almost always results in the answer you are after. So, “WordPress vertical line spacing” led to a place that eventually had the solution in it, but the theme didn’t match what I was expecting. This is the core of frustration, so I modified the search to include the themes name itself, and that helped. I found the setting, and it was in a CSS stylesheet file. I left the WWW when it was still HTML only. CSS irritates me. But anyways, hack CSS, that’s the answer. It’s a dumb answer, but that’s it. So I find about 130 places where line-height is an option. I laugh bitterly at the number. Which section to edit? Are you sure? So I gave it a shot. I set the line-height to 2.0 and then looked at my site. I can’t tell if it improved or not. But the most adaptive solution is to assert it did what I wanted. Mark the win as a notch and move on. Do I care? Well, I wanted to do something. I did something. Did it work? Probably not.

But then we get back to that first fork. That’s why I love Apple so much. Nearly everything they touch MAKES SENSE. I don’t have to struggle with some labyrinthine mystery. Maybe my edits will work, maybe they will break whatever it is, maybe it won’t matter. Maybe any setting I change will be overridden somewhere else, by something that was never documented. That’s the core design principle of both WordPress and Microsoft. I suppose we should just be happy that the most basic functions work. Much like the Internet itself, the fact that any of this works is a daily miracle.

So instead of writing a huge rant, one that nobody wants to read and nobody cares about I will assert that I won, psychologically move forward and be able to forget the conditions that led me to those particular experiences. The blog doesn’t work like you want? Don’t go there. Facebook a cesspool of ugly humanity? Skip it. Microsoft? Ah, if only it would burn to the ground. But we can’t have what we wish, even if we’d do anything for our dreams to come true.

So! Hooray! A Win! Facebook, WordPress, Office365! Just stop worrying about the bomb. It’s “Someone Else’s Problem®”

FreeBSD Crater

Posted on April 1, 2016 by bluedepth

I started out looking at FreeBSD based on a draw from FreeNAS, which then led to ZFS, the primary file system that FreeNAS and FreeBSD use. At work, I am looking at the regular handling of enormous archival files and the further along I went the more I realized that I would also need storage for a long time. There are a lot of ways to ensure that archival files remain viable, error correcting codes, using the cloud, rotating media. So all of this has led me to learn more about ZFS.

I have to admit that at first, ZFS was very strange to me. I’m used to HFS and EXT3 and EXT4 type file systems with their usual vocabularies. You can mount it, unmount it, and check it with an option to repair it. ZFS adds a whole new universe of vocabulary to file systems. There are two parts, the zpool creates the definition of the devices and files you want to use for your file system, and the zfs command allows you to manipulate it, in terms of mounting and unmounting. When it comes to error-checking and repair, that is the feature called scrub. The commands themselves aren’t difficult to grasp but the nature of this new file system is very different. It enables the administrator to perform actions that other file systems just don’t have. You can create snapshots, manipulate them, and even draw older snapshots – even out of order – forward as clones. So let us say that you have a file system, and you’ve been making regular snapshots every 15 minutes. If you need something from that filesystem at snapshot 5 out of 30, you don’t have to roll back the file system manually; you can just pluck snapshot 5 and create a clone. The cloning procedure feels a lot like “mounting” a snapshot so you can access it directly. If you destroy a clone, the snapshot is undamaged, it just goes back into the pile from whence it came. The big claim to fame for ZFS is that it is regarded by many as the safest file system, if one of the parts of it, in the zpool should fail the file system can heal itself. You can tear out that bad part, put in a new part, and the file system will rebuild and recover. In a lot of ways, ZFS is a lot like RAID 1, 5, or 6. Apparently there is a flaw with RAID 5 when you get to big data volumes and from what I can gather, ZFS is the answer to those problems.

So I have ZFS ported over to my Macbook Pro, and I’ve been playing around with it for a little while. It works as advertised so I’ve been enjoying that. One of the biggest stumbling blocks I had to deal with was the concepts of zfs mounting, unmounting and how they relate to zpool’s export and import commands. I started with a fully functional ZFS file system, created the zpool, then mounted it to the operating system. Then the next step is to unmount the file system and export the zpool. Exploring the way you can fully disconnect a ZFS file system from a host machine and then reverse the process. While doing this, I was reticent on using actual physical devices, so I instead used blank files as members in my zpool. I was able to create, mount, and then unmount the entire production, and then export the zpool. When I looked over how to reverse that, import the zpool I just had the system told me that there weren’t any pools in existence to import. This had me thinking that ZFS was a crock. What is the point of exporting a zpool if there is no hope on importing it afterwards? It turns out, there is a switch, -d, which you have to use – and that’s the trick of it. So once I got that, I became much more comfortable using ZFS, or at least exploring it.

So then today I thought I would explore the source of FreeNAS, which is FreeBSD. BSD is a kind of Unix/Linux operating system, and so I thought I would download an installation image and try it out in my VirtualBox on my Macbook Pro. So, I started with the image FreeBSD-10.2-RELEASE-amd64-dvd1.iso and got VirtualBox up and running. The installation was very familiar and I didn’t run into any issues. I got the FreeBSD OS up and running and thought I should add the VirtualBox Guest Additions. I thought I could just have VirtualBox add the additions as an optical drive and that the OS would notice and mount it for me in /mnt or /media. No. So that was a no-go. I then looked online and searched for VirtualBox Guest Additions. I found references to procedures to follow in the “ports” section of the FreeBSD OS. I tried it, and it told me that it couldn’t proceed without the kernel sources. So then I searched for that. This turned into a fork/branch mess and I knew that familiar sinking feeling all too well. You try and fix something and that leads to a failure, so you look for help on Google and follow a fix, which leads to another failure, and then you keep on going. This branching/forking leads you on a day-wasting misadventure. The notion that you couldn’t get what you wanted from the start just sits there on your shoulder, reminding you that everything you do from this point forward is absurd. There is a lot of bullshit you are wading through, and the smart move would be to give up. You can’t give up because of the time investment, and you want to fight it out, to justify the waste of time. The battle with FreeBSD begins. At the start we need the kernel sources, okay, use svn. Not there, okay, how to fix that? Get svn. Sorry, can’t do it as a regular user. Try sudo, command doesn’t exist, look for su, nope, not that either. Try to fix that, can’t. Login as root and try, nope. So I pretty much just reached my limit on FreeBSD and gave up. I couldn’t get VirtualBox Additions added, svn is impossible to load, sudo is impossible to load. Fine. So then I thought about just screwing around with ZFS on FreeBSD, to rescue some semblance of usefulness out of this experience. No, you aren’t root, piss off. I even tried SSH, but you can’t get in as root and without sudo there is no point to go forward.

So, that’s that for FreeBSD. We’re up to version 10 here, but it is still firmly bullshit. There are people who are massively invested in BSD and they no doubt are grumpy when I call out their OS for its obnoxiousness. Is it ready for prime time use? Of course not. No kernel sources included, no svn, no sudo, no su, no X for that matter, but honestly, I wasn’t expecting X.

It points to the same issues that dog Linux. If you don’t accept the basic spot where you land post-install then you are either trapped with Google for a long while or you just give up.

My next task will be to shut down the FreeBSD system and dump all the files. At least I only wasted two hours of my life screwing around with the bullshit crater of FreeBSD. What have I learned? Quite a lot. BSD I’m sure is good, but to use it and support it?

Thank god it’s free. I got exactly what I paid for. Hah.

Killing SpotifyWebHelper

Posted on June 12, 2015 by bluedepth

I’ve had a problem with Spotify for a while now on my Mac. The damn program opens up spontaneously all by itself unbidden. What’s really annoying is that it also frequently auto-starts and auto-plays tracks I didn’t want to play.

I found out that when I start my Mac, or start Spotify itself, there is another application which is automatically started called SpotifyWebHelper.

I’ve noticed that when I go into Activity Monitor and kill this app, the unwanted automatic start and play problem goes away. That’s good, but it’s not really the answer. The answer is to murder SpotifyWebHelper.

So I turned to the CLI, you can issue the command killall spotifywebhelper and press enter. That does kill it, but what I want is to prevent it from ever being run. So I unloaded it from launchctl and deleted it’s LaunchAgent .plist file. When Spotify starts, it puts it all back.

Then I went where SpotifyWebHelper is located and renamed it. Spotify repairs this as well. Then I tried to set the SpotifyWebHelper application in ~/Library/Application Support/Spotify so that it had no posix rights whatsoever by chmod a-rwx SpotifyWebHelper. The next time you run Spotify, it fixes it all by itself.

This is less of a feature and more of a virus. A zombie virus, you just can’t kill it.

But I have killed it for good, and here is how to be free of SpotifyWebHelper:

Quit Spotify
Open Terminal, killall SpotifyWebHelper
cd ~/Library/Application Support/Spotify
rm SpotifyWebHelper
cd ..
chmod a-w Spotify
Close Terminal, done!

After that, you will be free of the horrible SpotifyWebHelper bullshit and Spotify won’t automatically run and play things you don’t want it to.

Forked Lightning

Posted on September 23, 2014 by bluedepth

My day has walked into the deep pitch of the Microsoft tar-pit. I’ll dispense with the usual protestations that this technology is horrendous and anti-human and deserves to be loaded into an airlock and blown out into space, en route to the sun for ultimate destruction.

My god this is awful.

It all started very innocently enough with an iPhone for an ex-coworker that was asking for a new password. I had backed up the ex-coworkers email from Office 365 and to get access to do that I needed to change the password. That was easily done as I am the admin on our Office 365 email system. I changed the password, I then went to my “backup” computer account and started Outlook 2013, set up the ex-coworkers account on that machine and then went to backup the email using Outlook 2013’s PST file backup routine – that all worked just fine. Once I was done, I copied the PST file to a NAS drive, and that was that. Then another coworker who had the ex-coworkers phone came in because the device was complaining about a bad password, I had changed it and I didn’t know there was a device in play that needed this password update. Hooray for never throwing away 3M sticky notes! So I put the password in and I got into a conversation with the coworker who had the device. I offered to delete the account of the ex-coworker and assign him the alias for the ex-coworker thereby ensuring that mail flows unimpeded to where it ought to go. Everything was all right and proper. So I went into Office 365 admin control and deleted the old user. Then I went to assign the alias to the other account so the mail would flow properly. Office 365 complained that the old account was still around and couldn’t establish the alias. Turns out the account lives in a 30-day penalty box and won’t actually be deleted until we all wait 30 days.

So how do you purge this account from this 30-day limbo? You can do so with a handy-dandy Powershell command called “Remove-MsolUser”. So I open up Powershell and start entering all the bullshit commands to get it connected to Office 365. Arcane and labyrinthine has nothing on this crap, I can’t even begin to estimate just how awful this really is. So I get the Powershell up and connected and waiting at the prompt. Then I enter the command as I see it on this website and I get an error from Powershell that it doesn’t recognize the cmdlet. Okay. So then I look into how to solve this issue, turns out I need to upgrade to Powershell 3.0. I find another website that helps me find the version of Powershell that I have installed, it’s a registry hack, so in I go, HKLM blah blah blah. Turns out I have Powershell Verison 2. I need 3. So I download Powershell 3.0 for 64-bit like I should, and it refuses to load saying I have a later version installed. I find another website and figure out how to get the version of Powershell from Powershell itself, turns out I have version 4.0. Fuckity-Ok! So then I move on, and find that I need two more downloads from Microsoft, the first is “Microsoft Online Services Sign-In Assistant for IT Professionals” and so I download it. I install it, everything is just fine. Next stop is to install the Microsoft Azure Active Directory Module for Windows Powershell. I’ve got all my ducks in a row and then this last install fails – “In order to install Windows Azure Active Directory Module for Windows PowerShell, you must have Microsoft Online Services Sign-In Assistant version 7.0 or greater installed on this computer. So then I looked at the Programs list in Control Panel and found the exact application that I had installed earlier, version 7.25! So what the hell is wrong?!? So I then rebooted, and repaired the Microsoft Online Services Sign-In Assistant and then rebooted again, then retried the installer and the same error. I then copied this error into Google and found an article that pointed me to “Microsoft Online Services Sign-In Assistant for IT Professionals BETA”. It installs and forces another reboot, of course. Once that bit was installed, which worked properly, gah, it was back to the Land of Eternal Stench, also known as PowerShell.

And only then, at the end are we finally successful. All of this for the simple little effort to dump an unwanted email account from our Office 365 system quickly!

I can’t believe it took this much to get through to this solution. I don’t really understand how Microsoft is still in business. This awful lack of quality in any other situation would spell certain disaster for a company. Microsoft is apparently charmed. Actually, it isn’t charm as much as monopoly. Microsoft has a lock on business computing beyond all rational logic and just like IBM in the 70’s and 80’s, once you are locked in, you are stuck and have to smile and thank your masters for dropping crumbs that they allow you to feast on. Even if their products are complete crap, they’ve got the lock and they are using it. Hello again, IBM.

Whither Water

Posted on January 18, 2014 by bluedepth

I read this article about restaurants and their corkage fees. Mostly out of dull curiosity I found myself satisfied that I don't agree and there are delightful ways to avoid this entire argument.

But to the vex, paying a corkage fee is a custom where diners who supply their own wine pay the establishment money for the privilege. You have a choice, either pay the insane markup (feels a lot like a mugging) on restaurant wine or pay to bring your own. Either way you'll pay. The linked article even goes so far to comment that bringing your own wine is shaming the sommelier, because you don't like his offerings. So, you quibble with the quality of truncheon that you are mugged with. Ah. I suppose I've never found a use for a sommelier, and that's likely because it's a class warfare thing, sommeliers are great if you're a 17th century royal, otherwise be your own sommelier. Anyhow, the word indicates the servant who ran ahead and prepared a meal. In the United States, nobody runs ahead, unless it's a mugger waiting for you in an alley. So, sommelier, great. The article states that if you really want to be nice you should offer the sommelier a taste. This is amazing. The guy who marks up his swill 1000% gets honor? How about chased out with torches and pitchforks?

Yeah yeah yeah. Be nice. Don't be so grumpy. But why should a meal out spiral out of control and cost you way more than the “food” you are purchasing? The experience is usually the answer. You pay for the experience. So when it comes to wine, you are paying to “enjoy the services of a fine sommelier” or, really, paying for the opportunity to be screwed on price for a bottle of swill and think it's honorable – and defensible.

Partially this comes down to palate. You are paying a sommelier, and his palate to guide you. Because each palate is unique, like a fingerprint, what if you've paid 300 dollars for wine you detest? Instead you've brought a 3 dollar bottle of wine that you love. The sommelier is angry. They charge you a 85 dollar corkage fee as a matter of revenge for not being able to tear the alimentary canal out of the sommelier and staple it to your central nervous system. I mean really, this screams palate bigotry.

So the way out? Water. Fuck you and your worthless overpriced swilly “wines”. No corkage fee, no mugging, no obnoxious useless mugger behaving like a chimpy King Louis XIV court fop being all pretentious and galling over reprehensible palate bigotry. I never asked anyone to run ahead. So, screw off.

But then there is the setting too. “Fine Dining” is a euphemism for “Food Poisoning”, so in many ways that too is just so much of a waste of time and valuable resources. These self-puffed joints get grumpy and bent if you bring your own wine and so either pay their mugger to sulk in the corner or get your food to go and enjoy it at home with your own wine. Alas, you'll need a roll of TP too, so it's not like there is a win condition here anyways.

At least the water is chlorinated, so you at least have that basic thing to go on… Always remember to tip the angry sulking mugger too. He really wanted to bash your brains out and rifle through your pockets for loose change.

I'm honestly surprised they don't have a $50 charge for a glass of water. Seems like they've followed a theme and left out a gloriously glaring exception. After all, this is Fine Dining! LOL.

iOS 7 and Logitech Ultra-Thin Keyboard Cover

Posted on October 5, 2013 by bluedepth

I’ve run into a very curious issue with my Logitech Ultra-thin keyboard cover for my iPad 3 running iOS 7.0.2. Here’s the problem:

1) If you are in any application when you start all of this with the application ready to accept text, the iOS virtual keyboard appears. So for example, I start Drafts and start to type on my iPad.

2) Turning on my Logitech keyboard makes the virtual keyboard drop down off the screen, as usual, and I can type using the keyboard. Everything is all regular up to this point.

3) If you turn off the keyboard, the expected behavior is for the virtual keyboard to reappear. It does not, at least not on my iPad 3. I can open any other application that features text insertion, like Notes or Email (with an open new email) and the virtual keyboard will not appear.

4) So far I’ve found two ways to fix this. The first is the inglorious kung-fu grip of holding down power and the home button at the same time to reboot the device and the other solution, which is more acceptable but still annoying is to start the Logitech keyboard, open an app that uses text insertion functions and press FN-F3, which should make the virtual keyboard appear. Then turn off the Logitech keyboard and you should be good to go from that point forward.

If anyone has noticed this problem and knows of a fix, please leave a comment!

Thanks!

EDIT: As it appears, the keyboard is not reliable so it seems that I’ll be resetting my iPad after all. Blah!

Encrypt Everything

Posted on August 18, 2013 by bluedepth

Lavabit and Silent Circle have given up when it comes to providing encrypted email communications. Mega plans on providing something to cover the gap and in general the only real way to deal with privacy-in-email is end-to-end encryption. There was talk that at some point email might give way to writing letters and using the US Postal Service but there as well you’ve got Postmasters writing commands taped to mail about how everything has to be photocopied and stored – so even the US Postal Service is full of spies, the only thing the US Postal Service can be trusted to carry is junk mail.

What is the answer? Pretty Good Privacy. PGP, or rather, the non-Symantec version of it which is the GNU one, the GPG. If you really want to keep what you write private when you send it to someone else, the only way to do that is for everyone to have GPG installed on their email system so you can write email using their public key, which converts your email to cyphertext, secure from even the NSA’s prying eyes, and requires your recipient to unlock the message using their secret key, which they have.

I’ve been playing with PGP and GPG now for a very long time and I decided I would at least make a route available if anyone wanted to contact me with privacy intact – my public keys are on my blog, they are also on all the keyservers including the one hosted and run by MIT and the GPG Keyserver as well. To send me a private message via email all you need to do is get GPG, set it up, create your secret and public key, get my public key, use it to write me an email and only I’ll be able to read it. The NSA will just flag the encrypted contents for later analysis and thanks to AES–256, they’ll be hard pressed to get to the plaintext in your message.

That’s the way around all of this. GPG for everything. GPG public keys for email, for chat, for VPN, for files, and HTTP-in-GPG. Everything pumped through GPG. Since the government won’t stop spying on us, it’s our duty as citizens to secure our own effects against illegal search and siezure, and technology exists to do so.

Encrypt everything.

Grayed Folders in Macintosh OSX

Posted on August 16, 2013 by bluedepth

While copying files to an external hard drive with a bum cable using my Mac’s Finder to move the files I ended up with an accidentally half-copied folder that was grayed out and I couldn’t open it at all. I could go into Terminal and access it that way, but Finder was a dead duck. Even after I properly unmounted and remounted the drive it didn’t work. I putzed about for a while searching for a solution and the general answer most people have is to use the ‘cat’ command to copy the files elsewhere and just be done with it. This didn’t sit well with me, there should be a way to correct the situation without having to duplicate the folder or copy the files or do anything laborious like that – and it turns out there is just that.

The folder had a creation time of some date in 1984. Probably the first possible date for OSX knowing Apple. They initiated the folder but since the move was interrupted the later adjustment never got made. This is a bug, Apple. Anyways, how to correct it? Some people seemed to think that the ‘touch’ command could possibly do the trick, but touch can’t really get to all the dates that come with files in the HFS file system. This folder, for examples sake I’ll just call it “folder” had displayed this 1984 date as it’s creation date. The touch command was successful in mangling all the other dates, except for the specific one I was after. I used the ‘stat’ command on the folder and discovered that the st_birthtime of the folder was 1984. How in the hell do you change that date?

I found out that you need another utility to do it properly. You need to download the Command Line Tools for XCode, which is the development platform for the OSX Operating System. It’s free and easy to install. Once you do that, you will get a new command to use in the terminal called SetFile. So here’s how to fix this problem if you run into it: SetFile -d [todays date][file or folder] and press enter. So for my file, it would be SetFile -d 08/17/2013 folder/ and press Enter. Voila! Folder is real and not-grayed and Finder thinks it’s just peachy keen.

So for anyone with grayed out folders, check your dates. Use the stat command, download the XCode CLI tools and use SetFile to rescue your folder or file from inaccessible hell.

Bluedepth's Journal

Thoughts & Opinions

Category Archives: Rage