Dear Brian —
My somewhat legitimate position in the world as speaker, historian, archive dude and rabblerousing mascot means that it probably doesn’t do me any favors to do my really too easy to do slam of other people, out of the blue. But you know, sometimes I can’t help myself. I wrote about this, sort of, a while ago. But I said I wouldn’t do the jib-jabbery thing. Now I will do the jib-jabbery thing.
Way back when I was working on the BBS Documentary, in fact, before I was even shooting, which makes it around 2001, I knew that I needed a lot of help on the back-end when it came to research. So, besides reaching out to Slashdot, I also brought in a lot of friends and made myself very available. This availability went on through the entire three years of shooting. One of the ways was a mailing list called “Co-Sysops” where I had a bunch of computer types who knew their stuff, and I’d fling out an obscure question like “What was the highest baud you can make a USR do” or “Does anyone know who wrote X” and then, more often than not, people answered. One of the people on this list was Brian Dear.
It would be really good to present the scale of the endeavor. With no previous major filmmaking experience, I had assembled a 500 person list of “possible to interview”, hundreds of my own “definites”, and, over the course of filming, sent out something like 3,000 e-mails. Really. The resulting epic was, in my mind, a miracle that it actually happened. And to this day, I get mail from people stumbling onto it online, or through the website, or any of a bunch of other ways, and the general consensus is “oh wow”, with a dash of “wtf”.
Now, during this time, Brian Dear explained he should be one of the people to interview. He lives just outside of San Diego, and twice my travels took me near there, and on two occasions, I mailed him about an interview. No response. Again, keep in mind he was subscribed to the Co-Sysops list, which itself had me going “I’m heading out to ______ for a week to film.”. In other words, he had an enormous amount of chances to make it happen. I was very confused by this all at the time.
So the movie finally came out in May of 2005, a happy time all around for me. Happy, that is, except for one or two annoyances, specifically, a spontaneous appearance from Brian in the comments about the CD.TEXTFILES.COM project, where he says:
“Still mystified why Jason seems to have decided to exclude the whole Coconut story from his BBS Documentary. The Coconut era (COCONET, CocoTalk API, CocoMedia; radically different software from everything else on the market at the time — client/server architecture; EGA/VGA graphics only, with eventual Mac/Win support; first BBS to offer embeded graphical emoticons, which are now so common on web-based BBS’s); Unix-based, not DOS/Windows based) is an important chapter in the whole BBS drama, and no matter what the excuse, his history project will remain incomplete without coverage of it.”
What a twerp!
ANYWAY, the reason I bring this up is because Brian has his own little favorite subject, that of the PLATO system, which the BBS Documentary does mention and which is quite an enjoyable little history of its own. Enjoyable enough, in fact, that Brian decided to write a book on it. In fact, he’s been working on this book for years and years and years. In at least one bio he claims 20 years of research, although if we’re going to play that little game I’ve been doing BBS research for 32 years. Regardless, he’s been working on it for FOR-EVER.
For years, the only updates on his regular site about this project was to mention when someone he’d interviewed had died. However, he eventually did come out with a date: the book would be released Fall of 2010.
Well, it’s 2011. In the time since Brian slammed me for having an incomplete history of BBSes, I shot, edited, and released another film and now I’m shooting three more. The Computer History Museum has switched from the Visible Storage structure they had to an amazing, world-class museum setup of their materials. (I got a tour this year. Trust me, it’s worth going to if you’re within 100 miles of the place. A 1000 miles!)
Why am I saying all this? Like I said, it doesn’t help me all that much as I work on all the stuff, but every once in a while I see this dude’s name, I see that the book covers something other people haven’t covered, and something in me just snaps. The world is full of people fat-fingering their cheeto-stained keyboards with how you’re failing to be perfect, not achieving your potential, and that you shouldn’t have even tried. The advantage of them all dying in a fire is how long the fire would burn.
Hopefully this book will come out soon – I’ll be sure to get a copy. Until then, I’m going to get actual shit done.
Categorised as: documentary
Comments are disabled on this post
I’m sure Mr. Dear has done stuff to deserve this criticism, but as far working speed goes in general, it’s not a very meaningful measure of anything. Perhaps an artist is extremely obsessive compared to others; or perhaps they split their focus; or perhaps both. In any case, it seems a universal rule of artistry that no matter how fast or efficient one is, there is always someone faster or more efficient that one suspects of carelessness. Conversely, no matter how slow or painstakingly one proceeds, there is always someone slower who, one fears, might say something deeper, in the end.
He makes a short, slightly rough comment about your project but you seem to have overreacted. Unless there are other derogatory comments that he has made that have contributed to your view of him, you seem to be guilty of what you are accusing him of. If he spent a lot of time criticizing others I would understand. I think it would be better to focus on what he has achieved rather than what he has not achieved.
There are others. I do realize it might seem a singular event. It is not.
Don’t let the turkeys get you down.
Given how poorly written his little synopsis is, I don’t think I’ll want to read the book if it’s ever finished.
It was nice of you to give him a shout-out at least. I wouldn’t have heard of the book otherwise.
I remember Brian. I was the first and only person in the DC/VA/MD beltway to have Coconet. I was so proud of it and the experience. I was in the backyard of AOL and I was their ONLY competition with Coconet as the experience. I remember all the people who were in our user group back then. The frustrating thing though with Brian was that he just dissapeared and left us all hanging and we could not modify the code, fix bugs, or do anything, because it was a proprietary system, completely. So I appreciate that I was exposed to Coconet and it forced me to get into unix/xenix (i was already deep into AmigaOS and IBM/PDP os’s and ofcourse Hacking and Phreaking all at the same time :D.
Thanks Brian, and it was quite a time back in the daze 😀
Lance Romance “The Cleveland Phrankster”
I am surprised that Coconet was not included in the story of bbs’s cause it truely was revolutionary. Just like fidonet was to networking, Coconet was to user experience. But then i think back to how whenever i see stories on computing history, The Commodore story is completely skipped over in favor of Apple and IBM/PC. THey sometimes include Atari however it’s very rare that Commodore is even mentioned and that is ubsurd because it was the Amiga that started it all in my opinion. A1000. The first REAL Computer!
One last thing about Coconet….
If Brian had listened to all the Sysops back then, (there were sysops in Canada, South America, Europe, and the Far East (if my memory is right – it was a way way long time ago)), we would have kicked AOL’s ass. The technology behind Coconet was original and graphically superior in performane and apperance. The problem was it didn’t have the kind of financial backing it needed. It also wasn’t code available to all of us sysops that had invested in it. It was expensive for the day, but it was worth the experience and education. It’s to bad it ceased to exist.