Comcast (xfinitiy) Arris modem link light blinks orange (yellow?) rather than green - check your ethernet cable.

[jump to the update on this one, it’s not what I thought it was…]

When I switched from CenturyLink to Comcast two months ago my “boost” speeds were 50 up and 10 down on a rented Arris modem. The modem lights were green and i thought the link light was blinking green.

Recently comcast claimed to have doubled my internet speed. It did go up briefly to 100+ mbps, but now it’s back down again. Around the same time I noticed my modem link light started blinking yellow/orange.

It sounds like this may be associated with a > 100 mbps connection, but I suspect it also happens when there’s something amiss with Comcast’s network. Based on what I read and a call to Comcast there’s nothing to do about it as long as you’re getting the speed you paid for (which may not be the speed comcast promised, but there you go.) The comcast rep did say my area was suffering from network issues.

Update: A better thread on Amazon (!) says: "The light is orange when connected to a 100 Mbit device, and blue when connected to a 1 Gbit device”. My modem is connected to a GB device though (Airport Extreme), and the link light should be for upstream connection, not downstream. I may try a different ethernet cable...

Update b: I’m surprised, it’s not at all what I thought. The link light isn’t for upstream connections, it indicates downstream (internal) connection mode — 10/100 is yellow/amber/orange, 1000 (gb) is green. I’d forgotten that, in the midst of resolving an issue with a dying time capsule, I swapped out the ethernet cable connecting my Comcast modem to my Airport extreme. The new cable was a better length, and I thought it was excellent quality. Turns out it wasn’t so excellent! I swapped my original cable back in and the light immediately went green.

I then repeated the Comcast speed test, this time with my Macbook Air within a few feet of my router. For convenience I tried with 5GHz Wifi, not wired gb ethernet. Comcast more than passed the speed test — delivering 125 mbps over wifi. I don’t know if my modem reports a faster internal speed to Comcast and if that impacts provisioning. I’m used to berating my ISP, but Comcast did very well on this one. With 100+mbps (much less gbps) broadband internal networks matter.

In the dining room, a floor below and about 20’ feet away, the same speedtest over 5GHz wifi gave me about 73 mbps (my 11” Air might have been a wee bit faster than my 13” Air). Quite an impressive reduction.

Apple Time Capsule - dead at 2 years 4 months, resurrected as a pure NAS solution

My Apple Time Capsule is dead. It started taking a very long time to join my wireless network, so I did a ’restore default settings’. The restore seemed to work, but it couldn’t join the network; on restart it’s settings were scrambled. So I tried again, and it stopped paying attention altogether.

This TC lasted 2 years and 4 months. Even when it worked restores were agonizingly, impossibly, slow; the Time Capsule is a grossly underpowered NAS. I was disappointed in my previous time capsule, but at least it limped along for almost 4 years.

I have a reasonably modern Airport Express that can take over print server duties for now, but I do need something to run Time Machine backups on. I’ll have to think this over a bit…

Update 10/6/2015: Using broken TC as a wired peripheral

It looks like something is rotten on the network/wireless side of the Time Capsule. I gave it some debug time and some factory resets, but I didn’t invest a lot of time. For one thing I realized there’s only 25GB left on the 2TB internal drive — it really is too small to backup our home network. I’ve ordered a Synology DS215j [1] and two WD Red 4TB NAS drives to be our Time Machine and file server. Over time I may be able to use this to replace an external drive attached to our home server. Shawn Blanc’s 2014 review of the DS213j is a helpful guide.

In the meantime I’m short on backup for our home network. My primary server runs a highly carbon copy clone with offsite backup, and I can run carbon copy manually to a network share from my personal workstation, but that leaves two other machines. I also like having two very different backup modalities for my primary machines. I found I could still use the Time Capsule through its wired ethernet connection.

Our home network is all WiFi now that the Time Capsule (switch, NAS, etc) is dead, so I used network preferences/location to make wifi the primary network option on all devices. Then, using Airport Utility, I browbeat the half-dead TC until WiFi was off and network services were in bridge mode, but file share with local file password was on. Then I found I could connect from each machine by direct ethernet to the TC and run Time Machine manually. I’ll do that until I get the Synology integrated.

Hmm. I wonder what happens if I connect the Time Capsule to a network port on my Airport Extreme...

Update 10/6/2015b: Using broken TC as a pure NAS hanging off my newish Airport Extreme

It took me too long to figure this one out. I blame that partly on Apple’s now opaque Airport configuration tool (designed to try to hide complexity of WiFi, fails at that).

Our newish AirPort Extreme (column thingie with fancy antennae), which plugs into our Comcast “modem”, is powerful enough to cover our whole house — and it has 3 ethernet connectors. So after I disabled WiFi and put the broken TC into bridge mode, I connected its ethernet uplink to an ethernet jack on the Extreme. Voila — it’s lights are happy green and Time Machine works with no configuration changes. Even the photo slideshow on the TC USB mounted thumb drive share works. This will hold us until the Synology arrives (0 drive configuration is out of stock).

The only trick is convincing the TC to accept bridge/no wifi:

After doing a hardware refresh AirPort Utility (ethernet connection to Mac) insisted I first configure it as standalone network service. That left it blinking yellow, but I could then get to the “advance” interface that let me make it into a pure NAS solution.

[1] What are the odds its firmware comes with Chinese gov hacks pre-installed?

Search is broken on Simplenote.app for OS X

The developer working on Simplenote.app for OS X took an unfortunate shortcut when coding search. That’s kind of a problem, because search is what Simplenote is about.

It’s easy to see the problem.

In Simplenote 1.1 for OS X a note that has three words in it:

blue green yellow

search on blue and you’ll find the note. Search on blue green and you’ll find it. But search on [blue yellow] and you won’t.

That’s because the developer implemented a very simple string match search (sometimes this is called phrase search, but that’s a bit grandiose). Whatever string you enter in search has to directly match a string in the note.

Now repeat the same experiment with the Web version or Simplenote.app for iOS You’ll find that [blue yellow] works, as does [blu yell]. The developers who implemented search on iOS and the  web used what I call ‘word-starts-with-search’; it means a separate index is created containing all the lexical tokens and the input tokens are boolean matched against the index tokens (see also).

I’m quite surprised the OS X app passed Automatic acceptance testing — search is feature #1 for this app and it’s very broken in the OS X version.

Rich Text Format (RTF) died between 2006 and 2012. Without a funeral. What does that mean?

Nine years ago, when I was looking for a decent word processor (now that’s an old word, almost as obsolete as typewriter) for OS X I had a list of requirements...

Gordon's Tech: Nisus Writer Express: My Review

… It had to use an open file format. Practically that means RTF, RTFD or OpenOffice. I cannot abide yet another file format that will strand my data. That ruled out Mellel and, sadly, AbiWord. I don't care if it's the second coming of WordPerfect, it has a stupid proprietary file format. That also rules out Pages and AppleWorks...

I wanted a Mac native OpenDocument compatible word processor, but that didn’t happen (remember when the EU was going to make OpendDocument work?). So I settled, for a time, on RTF. In theory. In practice I didn’t do much wordprocessing on my Macs, I did most of my writing in Mail.app, MarsEdit and Google Docs. On Wintel I used Word.

I’m not using Wintel these days, so I was looking for something other than plain text for my Mac document work. Pages is an act of desperation, and until recently Word for Mac was a lousy product, so I started using TextEdit as a document editor because its default file format is RTF.

That’s how, rather late to the game, I realized that nothing on my iPhone would work with RTF. Google Drive will display RTF contents, and convert RTF to Google Doc, but since none of my iPhone apps supported RTF I couldn’t use an app extension to open those files.

So I started asking what was up with RTF. The short answer is that RTF died - sometime between 2006 and 2012. I’ve been unable to find an obituary — it simply passed from the scene. RTF only lives on in TextEdit because it’s been baked into OS X since time immemorial — but not iOS. (Nisus Writer still uses RTF as a native file format. Might be time to give that up.)

Sheesh. Shouldn’t there at least have been a eulogy?

I guess .docx is our de facto native document file format; the heir to the dreams of RTF and OpenDocument and many before [1]

Meanwhile geeks are using plaintext and markdown.

This is really not what we expected...

- fn -

[1] If you create a new document in TextEdit, then hit cmd-opt-s, you can specify docx and save. TextEdit will then stick with .docx. There doesn’t seem to be a way in Yosemite, secret or public, to make TextEdit use .docx as a the new document format.

See also:

• Gordon's Notes: Word file formats: the Nisus achievement and a gentle wish for .DOC (.doc sort of died I guess, in favor of .docx. My comment on iPhoto is poignant given what Apple did to iPhoto and Aperture.) 2/2008
• Gordon's Tech: An RTF surprise: 850 KB to 40 MB 10/2007
• Gordon's Tech: Nisus Writer Professional: the undocumented but critical improvement 4/2009 - late fix to to the image compression problem
• Gordon's Tech: Nisus Writer Express: My Review 4/2006
• Gordon's Tech: Nisus Writer Pro, OpenOffice and Rosetta - why I bought Pages.app 9/2011 - shortly after this Pages stunk.
• Gordon’s Tech: Spotlight can now index OpenDocument files (OpenOffice, NeoOffice/J) 10/2005 (Spotlight indexing is more important than ever)

Update 12/12/2015: Scrivener uses RTF in its text editor. Might be last to do so. I suspect it’s using OS X native support. The new version of Notes.app, interestingly, uses a subset of HTML.

Things to do when selling or retiring an old iPhone

Among other issues, Apple has longstanding problems with their customer identity infrastructure and how it intersects with their device registration, DRM rules, and messaging systems. Under iOS 8, for example, there appear to be 4-5 different authentication channels for Apple products even when a user has only one AppleID.

Which is why, in the course of moving the kid’s iPhones around, I made a list of the steps I take when deactivating an old iPhone (for sale, disposal, or migration to the backup stack):

• log out of FaceTime (remove credentials)
• deregister iMessage: iMessage turn off, FaceTime logout and turn off
• remove iTunes Store AppleID account information (which can differ from iCloud AppleID)
• from Settings:Mail,Contacts, Calendars:iCloud:Advanced:Share My Location: From: (Your device) remove unwanted devices
• log out of iCloud/Find Phone
• log out of FindFriends
• if you can figure out which apps or content apps use DRM to limit installs, then sign out from those (Example, Inkling books.) Good luck.
• wipe phone
• power off
• Manage your associated devices in iTunes - remove the device
• Manage devices associated with your Apple ID (not same as iTunes devices) - remove the device
• Remove device from Apple support/Apple ID device profile? (this is an ugly business)
• In Find iPhone on another device you can remove the device from the list. You’ll need iCloud credentials associated with each device. I believe this updates Apple’s record for device owner.

Note that you can change the iTunes Store Apple ID associated with an iPhone only every 90 days.

Did I miss anything?

By the way, even after doing all this, I found lots of old devices when I use iOS 8 FindPhone...

Update 9/26/2015

While browsing Google Account Security I found this ..

Google keeps track of devices (unclear how it identifies a device) in addition to credentials. If it gets valid logins from an unknown device it sends out a warning email. 

So if you want to be very careful when you retire an old iPhone, you should review the Google Account Security Device activity & notifications page for every Google account you use and remove the old device.

I haven’t bothered to do this methodically, but it’s a reminder of how hard it is to throughly remove all connections between one’s identity and one’s devices.

Appigo ToDo task management suite: Archiving and Export of completed tasks and projects is non-negotiable requirement

Appigo has deferred work on archive and export of tasks and projects for at least two years and possibly longer. When I paid Toodledo to provide back end services I could live with ToDo.app’s missing features, but when I switched full time to ToDo for iOS and ToDo for Mac with ToDo Cloud support it became a real concern. I gradually realized Appigo wan’t showing any inclination to change.

I’ve tried one last ticket request:

[#85787] Archiving and Export of completed tasks and projects : Appigo Inc.

There are two closed discussions related to archiving of completed tasks and related request to export tasks and project data.

I know about setting sync to 1 year, I know ToDo web version will paginate completed tasks (up to 1 year?) and I know I can access tasks via SQLite (but dates are proprietary format).

I know I can sponge off Toodeldo and use them as an archive format without sending them any money (unethical).

I need more than that. I signed up for ToDo Cloud and I use both the iOS and Mac version intensively, including all Project features. I can't continue using ToDo Cloud if I can't have long term storage of project/task information as well as archive export.

It's just an essential requirement. If you can't tell us you're going to do this I need to find another product."

I have a feeling I know where this goes. So I’m looking again at Things an Omni, and it may be that I’ll reverse my shift and return to Toodledo.

Weirdness with Yosemite Google accounts and email configuration: "This message may not have been sent... Report phishing"

I noticed my daughter was receiving email sent from my iPhone with my email address but the sender name of “Gmail personal”.

It took a while to figure out that this sender name was coming from how I named one of the user accounts for Mail.app … on OS X.

I really don’t understand this, but a Google search somehow sent me to this seemingly unrelated conversation ...

Fortunately, I know better than to ignore the nsAI of our time (non-sentient AI) - so I started poking around the configuration of my “Internet Accounts” (Yosemite, click Details after choose account name) and my OS Mail.app Account settings (which are sort of like the “Internet accounts” and sort of not like them).

There I found some oddball settings for Outgoing Mail Server — on a freshly configured machine (I didn’t migrate from prior machine):

I deleted the odd outgoing mail server .. .and Mail.app stopped sending email.

There’s a problem with Yosemite and multiple Google accounts on one OS X user account. i’m still figuring this out. I suspect the keychain is involved...

Update: It seems to be working at the moment. I had to create a unique SMTP server for each account and entering my Google credentials (2F bypass password for one of ‘em). I don’t think it’s supposed to work this way. I think in theory there’s a typical Apple hack whereby one does Google authentication in OS X System Preferences and OS X is supposed to create keychain entries Mail.app uses. In practice this appears to fail when a user has more than one Google account...

An AskDifferent thread also implications the keychain, and since the keychain is iCloud synced its configuration can poison multiple clients. i suspect Apple (engineer? product?) simply decided to ignore people with multiple Google accounts.

Update 9/26/2015: 

In much the same thread I ran into a similar configuration problem on a different Yosemite Mac. This time a correspondent reported Google was warning him my email was suspicious:

I figured that Google was seeing a mismatch between the stated sender domain and the SMTP sending service domain. When I looked in Mail.app account configuration (not to be confused with OS X account configuration) I found this:

I have two Google accounts configured, one a Google Apps account (single factor) and another a Gmail account (2FA). The “Home” (2FA) account was using the SMTP server I’d labeled “Gmail Work”. Wrong one.

I switched the the Gmail Home (my definition) SMTP server, which was setup this way by OS X. NOTE the lack of password. Despite the UI displayed here OS X doesn’t actually use the account password. It does some other form of authentication for this 2FA account, possibly via some OAUTH token magic stored in the OS X keychain (which is synchronized between devices, and since Google looks for matches between device and credentials I suspect that causes issues):

After switching the SMTP service to this one (“Gmail Home”) my next email did not generate a phishing warning.