How to update Synology Cloud Station Server Clients (Cloud Station Drive) after Synology NAS 6.0 update

Looking back, 2009 was kind of a bad year. Somewhere around then we were in the tail end of the Great Recession, Google had turned Evil, and, in retrospect, Apple’s glory days were behind it.

I miss the old Apple. It wasn’t perfect, but it shielded me from a lot of hassles. Like dealing with the complexity of my Synology NAS.

I bought the NAS because Apple’s Time Capsule is broken. Next I started using it as a post-server replacement for Apple’s perennially broken network shares. That’s all I bothered with. I didn’t want to bother my NAS, and I didn’t want it to bother me.

Then, inevitably, there was an update. It took me a while to figure out that Control Panel:System:Info showed the version number: DSM 6.0-7321. 

Oh, great. A complete version update. I #$@$#!# never install those. I’d turn off auto-update, but at this point the damage is done. I’m going to need the big bug fixes; I’ll turn it off in a month or two.

Meanwhile both Time Machine and my Client-Server NAS file sync are broken. I’ll fix Time Machine next, this is about fixing the file sync.

Notice I’m not naming the file sync? That’s because Synology, a Chinese company, uses English words inconsistently. They add and remove “Cloud” to everything and seem to move software names between products on a whim. I think I’ve seen File Sync, Cloud Station Drive, Cloud Station Sync, Cloud Station Server and Cloud Station Client used to refer to similar or identical things.

What I wanted was to update “Cloud Station Drive” running on my Mac, which is actually Cloud Station Server Client, to a version compatible with “Cloud Station Server” running on my Synology NAS. Notice neither of these actually have anything to do with a “Cloud”, they’re both LAN specific.

This document helped: Sync files between NAS and computer Network Attached Storage (NAS)

 Here’s what I did:

1. Quit outdated client on my Mac.
2. Start Synology Assistant to locate FLNAS (IP Address), open it.
3. Go to Package Center, All, find Cloud Station Server, click Open (alt: click the four-square-icon next to question mark to see running apps)
4. Click Overview (sometimes this is empty, quit and start over again)
5. Download Cloud Station Drive
6. Install

It seems to be working. I’ll use the DMG to update my other machines.

Next up: Fix Time Machine. It and Synology are disagreeing about how much space is free in the user-quota for my MacBook Air …

Update 8/23/2016: Synology Cloud Station Server / Cloud Drive is broken again. I think it’s worse in El Capitan than Yosemite. I’ve given up on it.

Using iOS 9.3 Notes.app to safely store passwords and other credentials

I wrote this as part of a book project aimed at caregivers for special needs teens and adults, but the recommendations work for most non-geek users. The trick is printing copies of the Note; it’s too easy for an errant edit to delete credentials. Of course one could also store PDF copies on an appropriately secure encrypted drive or drive image, but that’s way outside the scope of these recommendations …

Managing Explorer credentials with iOS 9.3 Notes.app and Android alternatives

Guides need to create “strong” passwords for Explorer email accounts, bank accounts, Amazon accounts and the like. One way to create a strong password is to combine two randomly selected words form a dictionary, capitalize one or two letters, and mix in some numbers and a symbol like $#&:;. Avoid letters and numbers that can be confused with one another, like l and I or O and 0.

There’s no way any of us can keep secure credential information in in our heads. We have to write it down, and, because you really don’t want to lose password information, you need to have two copies.

The two copies also need to be in different places. Why two places? Well, imagine that you’re storing your passwords on your phone. One day you need to unlock your phone, but you don’t remember the phone password. If the passwords are only on your phone you won’t be able to get to them. Even if your phone is backed up the backup won’t help you, because you won’t be able to restore it without the phone password.

…1Password is too complex for most Guides and Explorers though. What about just keeping credentials in a Note on your smartphone?

If a Guide is using and Android smartphone this can be a risky option. As of early 2015 many lower cost Android smartphones are not truly secure. Google’s Note application, Keep.app, doesn’t support Note encryption. So on an Android device I’d recommend using 1Password.app or one of its competitors — unless you are confident the Android device uses strong encryption and it is secured with a strong password.

If a Guide is using an iPhone with iOS 9.3 or later Apple’s Notes.app is a good, simple way to store an Explorer’s credentials. The iPhone itself has quite good security, and you can create an additional Notes.app password and use it to lock one or more individual Notes. iPhones that support TouchID (fingerprint unlock) make it easy to access locked notes. Just be sure to add the Notes.app password to your document and to print out the Note when it changes.

This approach is simple and secure, and it’s safe as long as a Guide keeps printed copies. It’s easy to accidentally delete critical information when editing a Note, and of course phones get lost and broken. Paper backups are reliable.

There’s an additional important advantage of printed backups. When someone becomes disabled or dead their family will really appreciate the printed copy.

Airport Utility: How to load an external configuration file for a brand new AirPort Extreme

The AirPort Utility tries too hard to be friendly. It wants to do some fancy migration from an older device that’s running, but I’d already exported that configuration file and removed it. Everything was connected, I just wanted to import the configuration file.

I couldn’t!

The trick, of course, is the option key. Cancel out and look for “Other Wi-Fi Devices”. Option-click the new one. You get a ‘power user’ interface (same one with option clicking any device in AirPort Utility). Now you can import the .baseconfig file you exported previously.

It came up perfectly, except it had some odd default password initially. I changed it to my admin password and updated.

My 2014 AirPort Extreme just died.

I liked the ME918LL/A AirPort Extreme for 17 months. It covered most of our house with a single device and it was pretty reliable. Around 17 months it started to spontaneously power down. I suspect an issue with the power supply, Apple has a long history of wonky power supply problems.

I wouldn't be surprised if there's eventually a recall program. I purchased it with an AMEX card, so I’ll now see how good their extended warranty program is. (It used to be quite good, but AMEX has outsourced the program. If it fails me on this one I’ll deprecate my AMEX card.)

In the meanwhile, sadly, I’ve ordered another Airport Extreme. (Sigh.) I really couldn’t find a better option — Eero is quite expensive, unproven, and it comes from a startup that’s got a 20% chance of surviving. Google's hardware is outsourced and of unproven quality.

Apple’s Airport Express has a great reputation of reliability. If you can make do with the Express I’d recommend it over the Extreme. If you live in a country that mandates 2 year warranties then the Extreme is a good buy. If you live in the US either use an extended warranty credit cards or pay extra for Apple Care. Once you add the Apple Care costs the Extreme is more expensive than Google’s router.

Yes, WiFi services suck. They really shouldn’t. I need an electrical engineer to explain to me why so many of my WiFi solutions last 1-2 years. (I have a 6+ yo Airport Express still running …)

PS. Interesting that Amazon no longer sells the Airport Extreme or the Express. I had to buy direct from Apple.

iCloud Photo Library, Photos.app and my Aperture plan (plus Aperture Exporter)

I recently migrated my daughter to Photos.app and iCloud Photo Library. I ran into some minor issues and one significant bug, but I liked it well enough to pay $1/month for the 50GB tier. It did take hours for her few thousand images to upload. My hope is that she’ll start managing (deleting mostly) her images this way. The full res images are stored in a Photos.app Library in her account on my Air as well as in iCloud; the local Library gets backed up with offsite rotation.

So now I’m trying it for myself. I’ve never liked or used “My Photo Stream”, so I didn’t have to turn that off. I just enabled iCloud Photo Library with an empty Library then added the images from my phone. It’s impressive to see crops and burst select changes made on my phone update my Photos.app Library almost instantly.

Incidentally, turning this feature on disables iTunes photo sync. I didn’t even realize I had 125 orphaned images on my phone from when I used to do iTunes photo sync.

I’m not even dreaming of moving my 350GB Aperture Library to iCloud though. Here’s my current Aperture plan: 

1. Migrate the family Mac to El Capitan after next release and test my Aperture Library against that machine. I assume it will work well enough but I need to do my own testing. I know of a few problems with El Capitan.
2. Once I’m somewhat satisfied I’ll move my Mac to El Cap and stay there for two years unless (unlikely) Aperture runs in OSNext. 
3. Meanwhile I’ll be using Photos.app to work with my iPhone 6 images and perhaps RAW or JPEG images from my dSLR. I’ll “Develop” them there and, when they are “ready”, I’ll move JPEGs (not RAW) into Aperture and delete them from Photos.app on my Mac and my iPhone (replaces importing from iPhone). Yes, this appalls some photographers but I care about archives more than image editing options post initial work. 
4. Somewhere around 2018 I’ll flatten all my keywords (I use Aperture’s inheritance model queries -- which were too advanced for market really) and migrate to Photos.app 2018. Assuming Photos.app is still around in 2018.

Incidentally, while developing this plan I tried out my copy of Aperture Exporter. It didn’t go well. AE creates keywords in Aperture for things like image-album relationships; in my case that resulted in very large numbers of keywords. Probably more than Aperture was ever tested to handle, more than enough to prove the UI doesn’t handle scrolling. If I use AE on the future it will be with a temporary copy of my Library, not the original.

Note/Update: 

At least with Yosemite this seems to work, though it’s stretching the bounds of what Apple allows:

• My Photo Stream: turned off in iOS.Photos, OS X.Photos and Aperture. (It’s a useless feature.)
• iCloud Photo Sharing: turned off in OS X.Photos, on in iOS.Photos and Aperture.
• iCloud Photo Library: on in iOS.Photos and OS X.Photos, not available in Aperture. Download Originals to this Mac in iOS.Photos, Optimize in iOS.Photos.

Aperture Tip: getting from Project in viewing pane to Project entry in the Inspector

It works like this:

1. When viewing Projects in the View/Browser pane, select a Project
2. Look for the little i that appears or tap shift-I (project info).
3. Click that. Windows pops up. Look for the Go To Project button. Click it.
4. Now you are on the left side seeing the project.

I’ve been looking for this for about four years. It’s a kludge.

iPad LTE videoconferencing for a longterm care facility resident?

My 94yo father is a resident of a Canadian longterm care facility (veterans). He’s been surprisingly content there — though funding transitions are likely to make it less agreeable. He’s also retained more cognitive ability than I’d expected; not enough to live without assistance but enough to enjoy family conversations.

I live in Minnesota, and unfortunately none of my siblings live near him. We pay for a friend to visit him weekly, that has worked well. He also gets daily phone calls from my sister, but I have a hard time speaking with him by phone. He doesn’t understand my voice very well. Surprisingly, we do much better on Skype video calls. I think the audio quality is better, and by reading my face he is better able to converse.

The Skype calls require facility support that is likely to fade, so I’m now thinking of iPad LTE FaceTime calls. At the end of his life, in a weird twist of fate for a working class man, he has more money than he needs. He can pay for the device and the mobile fees.

I’m thinking of an iPad 2/3 (full size) with a wall or desk mount support and a lock, setup so he’s not backlit. When not in use for videoconferencing it can play a family photo slideshow (it’s dismally hard to find good products for slideshows). I don’t think he’d be able to initiate or receive a call — FaceTime’s UI is far too awkward, but I’d schedule times around a helper visit.

Anyone aware of similar projects? Leave comments here or email jgordon@kateva.org (or app.net @johngordon).

If I do the project I’ll publish on our experience.