Friends Zone at 20

friends
In early 1994, I was the Manager of Dartmouth’s Computer Resource Center, an artisanal pre-sales and consulting office in Dartmouth’s Computing Services. One morning, the Director of Computing stopped by my office and handed me a floppy disk and told me to check out what was on it. I popped it into my computer and saw that it contained a single application, Mosaic 0.9b. Curious, I launched it and thus began my experiences with the World Wide Web. Within a week, I had created Dartmouth’s first Web site (and one of the first 50 college web sites in the world, near as I could figure at the time). By fall, I created my blog (one of the first ever) and was looking for new, higher-profile projects.

I noticed that TV show websites were becoming a popular and I sought out a show I could get in on. My big obsession at the time was The X-Files so I reached out to the webmasters of one of the better sites offering my help. They told me they had things in hand and didn’t need any help so I cast about looking for other things I could do.

In the fall of 1994, Friends premiered and I noticed that since there was no USENET newsgroup for the show, people were talking about it in alt.tv.mad-about-you, much to the chagrin of the folks there who didn’t care for Friends or who were just OCD about things staying on-topic. It had no website, no mailing list, no newsgroup. And, hey, I really enjoyed the show. So, I sprang into action. I created alt.tv.friends, a LISTSERV mailing list, and a website.

Soon after, a supervising producer of Friends reached out to me to start providing some information back to us fans on the list. He told me that they put the Episode Guide and FAQ up outside the writers’ room to help with continuity. A thriving fandom had been born.

But by around January 1995, as people on the mailing list began to get to know one another more, topics began to stray from the show to talking to each other about anything. Friends were being made. This upset those people who preferred the list stay on-topic and there began to be some anger running around. I decided to split the list into two lists: Friends-TV for discussions only about the show, and FriendsZone for folks to just hang out.

On February 6, 1995 the list was created and the first subscribers began to appear.

The history of this virtual community is long and storied but the short version is that, 20 years later, it is still around. While there is still a mailing list, it is almost never used. Instead, a Facebook group now carries most of the conversation.

And this weekend, in Las Vegas, a group of these folks are getting together to celebrate the 20th anniversary. I wish I could be there with them but it just wasn’t in the cards for me. I hope they all have a great time and post a lot of pictures.

Happy Birthday Zone!

Fixing “Trust this computer” Problem

I had a strange problem crop up on my iMac running Yosemite and both of my iDevices (iPhone 6, iPad 4). When I plugged either in, I would get a dialog on the iMac saying photos could not be imported because the device was locked. On the devices themselves, I would be asked to Trust this computer. This happened every. single. time.

In the system.log, there were error messages to the tune of:

11/7/14 7:16:52.086 AM usbmuxd[57]: AMDeviceConnect (thread 0x1002fe000): Could not connect to lockdown port (62078) on device 1076 - [long ID number here]: 0xe8000084.

Digging further, I discovered that there is a directory, /var/db/lockdown, that contains a plist for each device connected to the Mac over the years (and since I have been leading an iOS Dev Team for Ozmott, I had a lot of devices listed in there!) and it seems that, for some reason, changes were no longer taking. I am not sure why. There were no errors related to permissions or otherwise.

On the advice of a thread I found online after some extensive Googling, I removed the lockdown directory. Theoretically, it would be recreated by the system. However, it wasn’t. Now when I connected my devices, I got the following errors:

11/7/14 7:22:44.510 AM com.apple.usbmuxd[57]: WriteDataToPath unable to create file /var/db/lockdown//SystemConfiguration.plist.tmp: No such file or directory.
11/7/14 7:22:44.510 AM com.apple.usbmuxd[57]: CreateAndStoreBUID WriteDataToPath failed: No such file or directory

So, I created a new lockdown directory using sudo mkdir lockdown. Then the errors changed to:

11/7/14 7:27:09.767 AM com.apple.usbmuxd[57]: WriteDataToPath unable to create file /var/db/lockdown//SystemConfiguration.plist.tmp: Permission denied.
11/7/14 7:27:09.767 AM com.apple.usbmuxd[57]: CreateAndStoreBUID WriteDataToPath failed: Permission denied

The directory was owned by root (because I created it using sudo) and clearly needed to belong to the usbmuxd process. Directories belonging to processes are named for the process preceded by an underscore. So I executed: sudo chown _usbmuxd lockdown.

That worked. Plugging in my devices resulted in the same dialogs as before but once I told the iDevices to trust the computer, new plist files were created for each and subsequent connects/disconnects have not had the errors recur. We’ll see if this sticks over time but at least I know how to fix it, even if temporarily.

Update 18 December 2014: The problem routinely returns. After I leave my computer running for a day or so, the problem comes back. I haven’t needed to resort to the fix above as simply rebooting my computer fixes it. It’s safe to say that something I am running on my machine is responsible. Now for the sleuthing…

Update 15 January 2015: Solved! Thanks to this thread on Stack Overflow, I have a solution that works! When this happens, open up a terminal and type

sudo launchctl stop com.apple.usbmuxd

And it restarts the broken usbmuxd process and things are happy again.