Saturday, October 21, 2017

My latest attempt to reclaim my wife's stolen email address from Facebook

You cannot reclaim a personal email address used by a stranger’s Facebook account. Facebook’s procedures do nothing. 

Today I tried something different.

To review, a year or so ago my wife started getting Facebook notifications from “Ding”. Her iCloud email address was used by “Ding Ling” (https://www.facebook.com/ding.ling.98031) to create a Facebook account. I don’t know if my wife accidentally validated it or not but we’ve been unable to retrieve her email address.

Since we control the email we can reset the account password, but Facebook’s poorly documented procedures to reclaim the address did nothing.

So this time I again reset the password but then I followed Facebook’s directions to upload a legal ID (a way to take control of the account):

PleaseRemoveMyEmailFromThisPersonsAccount

I used my drivers license as a template to get past Facebook’s image size test then overlayed a text image requesting release of her email address.

I’ll update this post if it works. 

Yeah, there should be a law.

Update 10/29/2017

It worked. It took a few go rounds. Eventually I was directed to the same kind of form I’d submitted a year ago, but this time it got to a human. I had to send a summary response email from Emily’s iCloud account. I think it helped to point out that “Ding Ling” was obviously a fake account. Once the email was retrieved I added it to her account.

I wonder if somehow it mattered that Emily has both an iCloud and a “me” address for the same account (due to Apple’s old mobile.me migration). Her .me address was already associated with her Facebook account.

iCloud calendar invitations to non-iCloud accounts are still broken

It’s been over a year since I first posted that iCloud invitations to a non-iCloud (ex: Google) account have been broken since 2011. Briefly, if someone sends an invitation from iCloud to my gmail address I’ll never see it. Somehow Apple looks up one of the four (that I know of[1]) iCloud accounts that I have, presumably one that references my gmail address, and uses that one instead.

In late 2016 Apple introduced an obscure workaround, an advanced iCloud (only) Calendar setting to receive event invitations by email — “if your primary calendar is not iCloud”.

I was working on a book chapter today so I revisited the old bug to check out the workaround. From my son’s (unused) iCloud Calendar I sent myself an invitation. Despite the setting nothing appeared in any of my (unused) Apple iCloud Calendars.

I waded through my Apple IDs to identify which one was associated with that Gmail address. I had to answer Apple’s “secret” questions [2] several times, but I found an Apple ID of mine associated with an iCloud account that did had the “receive by email” option enabled and had iCloud mail services. I tried from several iCloud accounts; none of the invitations appeared anywhere. They didn’t show as email, they didn’t show up on my iCloud calendar. They went into the ether.

Apple iCloud calendar invitations to non-iCloud addresses are still broken.

[1] Multiple iCloud accounts, some with email services and some without, is a longstanding Apple fiasco. Cook promised to clean it up several years ago and quietly abandoned hope. I periodically read hints from insiders that Apple’s identity management is more screwed up than even the most cynical outsiders can imagine.

[2] Also known as a hacker’s best friend.

 

Photos.app flailing during sync with iCloud Photo Library? Maybe it's a permissions problem.

My daughter uses Photos.app and a 50 GB iCloud Photo Library to manage her videos and images [1]. She edits on an older Air with a small SSD, in that environment Photos.app caches scaled res images and only downloads full res when editing.

In addition I run an instance of Photos.app for her that stores full res images. The Photos.app Library is stored on an external SSD that hangs off an Elgato T2 Hub attached to my beloved Air. The hub has been very reliable under El Cap and Sierra.

I have a user account for her on my drive, and in that account the external library is the Photos.app System Library. My Time Machine [3] and Carbon Copy [4] backups include that Library.

All was well under El Capitan. A few months ago I upgraded to Sierra [2]. Yesterday I decided to update her Photos.app library — only to discover I was a few months behind [5]. Her user account hadn’t been updated to Sierra; when I opened Photos.app her Library had to be updated.

Things did not go well. Photos.app said it was uploading @8,000 images (really it shouldn’t have uploaded anything, but Photos.app sucks), then @2,000, then @11, then … You get the idea. It did that when I went to bed, and it was doing it in the morning.

After a bit of playing around I discovered that a Sierra bug meant that she no longer had write permissions to the external SSD, even though macOS said she did. I switched to an admin account and there she had no permissions, so I added her. After that she could write to the SSD. Photos.app “stuck upload” was because it had no write permissions at all.

I decided to create a fresh Photos.app Library for her. To do that I turned off WiFi and did option-Photos.app startup to create a new Library. I copied the old Library to an external drive and deleted it. I then opened the new Library, made it the System Library (interestingly it showed images from a cache!), turned on WiFi and enabled iCloud Photo Library. The images then downloaded from iCloud (source of truth) and restored my local backup copy.

- fn -

[1] She is chronically running against the limit — which isn’t all bad. It enforces some editing. I might switch to sharing a 200GB plan, but I’m not sure how that will work with our current family use of a single iTunes password. Future experiment needed.

[2] I like to wait at least 8 months before accepting Apple’s dangerously buggy macOS updates.

[3] Our two Airs do Time Machine backups up to a Synology NAS. After some initial issues that has been utterly trouble-free. The NAS has two RAID 1 drives, if one fails the other survives. This is another reason I wait for macOS bugs to get fixed; I also need things like VMs and NAS to be updated.

[4] CCC backups to a 4TB low heat drive in a Voyager cradle with Firewire 800 connection to the Elgato hub. I rotate 4 drives. Rotation is every 2-3 weeks, 1 drive is across town, the other in my Van. A Yellowstone eruption would take them all out unless the van outran the pyroclastic flow. It is a shame that offsite internet backup has failed.

[5] Only automated backup ever works — and no form of backup is reliable.

Saturday, October 14, 2017

Mobile device management and Apple Classroom for home

Contrary to Ziff-Davis (ok, it was 2013) there are several vendors who provide MDM solutions for home use. MMGuardian and Qustudio are two of them.

I wonder though if it’s possible to cobble something together at home that would work with Apple Classroom. OS X server ($20) includes Profile Manager, Apple’s MDM manager (support). Joshua Jung has written a nice tutorial on getting Profile Manger working. In theory Apple Classroom should be able to work with this …

Anyone try it?

Saturday, October 07, 2017

Quicken for Mac moved our financial data to their servers and we can't remove it

From Quicken.com support:

What is the Quicken Cloud?

 …The Quicken Cloud data cannot be deleted, although there may be an option to delete it in the near future.

Quicken Cloud is used to sync data for mobile devices. We don’t use Quicken mobile, we only use Quicken for Mac. We did not enable Quicken Cloud sync, we were careful not to enable it.

It appears an update turned it on. Our financial data is now on Quicken’s servers. The servers of a company that clearly has its head deeply buried in an orifice. I’m sure they’re just great at net security.

Anyone know of any good lawsuits against Quicken.com we can support?

Update 10/29/2017

Via Twitter: FAQ: How to remove cloud data in Quicken Mac 2017 4.6.x. I followed the directions. As best I can tell data can flow from most of our transaction partners either directly or via the Quicken cloud. When this procedure is applied transactions revert to Direct where possible. Some don’t work Direct, they stay in the Cloud.

Tuesday, September 26, 2017

Life with Apple: Podcasts move to streaming only

In a move that feels as inevitable as death and taxes, Apple has made podcasts effectively streaming only. The same thing is likely to happen to all media, Podcasts just went first.

Until recently macOS iTunes and iOS Podcasts.app supported both file based sync, including Playlists, and streaming based distribution with an unreliable sync of podcast metadata.

With iOS 11 iTunes playlists are no longer represented in Podcasts.app. You can still create Playlists in iTunes made up of local files and/or cloud references, but they stay in iTunes. The Playlists were the main way I organized listening to my large collection of file-based In Our Time podcasts and my medical education podcasts. No more. I’m now dependent on the very limited (ok, crap) organization abilities of Podcasts.app.

Apple has long had problems with video that moved to an iPhone from both iCloud and iTunes. iBooks synchronization is a mess too if you mix non-Apple store ePub with streamed iBook.

This is ugly and going to get worse. We’re moving fast into the DRMd hard data-lock rental-only future.

Update: Many good threads on this in Apple Communities. They reminded me to leave feedback. Stations are not a substitute for playlist sync, but even on their own they are missing a key filter — limit to on-device items.

Sunday, September 03, 2017

Photos.app is as stupid about JPEG Export as iPhoto and Aperture.

Try this experiment.

1. Import a camera produced JPEG into Photos.app. Check the size. Let’s say it’s 6.8MB.

2. Don’t edit the image. Export it as maximum quality JPEG. Check the size. It will be something like 17.2MB.

Even though the image was native JPEG, and it wasn’t edited, Photos.app decompressed and then recompressed it. Adding 11MB of non-value.

Unchanged from iPhoto and, for that matter, Aperture.

There should be a better way. (No, unmodified original is not a better way — because if editing were done, or the original were not JPEG, then you would want the transformation.)