Categories
Weblogging

When reality and virtuality meet and clash

Recovered from the Wayback Machine.

During my brief contract earlier this summer, a jarring moment occurred when I walked up to one of the people I worked with and saw that he was reading my weblog. I’ve never had such an obvious mix of the ‘real’ world and this virtual world before, and I found it uncomfortable. He’s a very likable person, friendly and personable and now a budding weblogger – but it was still a moment that stopped me dead in my tracks.

I don’t encourage my friends to read my weblog, though they are welcome especially if it helps me maintain contact with them. However, I don’t talk about it with my family, and hope that they’re too busy to check up on what I’m writing.

When I went back to San Francisco this last trip I had kind invitations for lunch and fireworks, from a fellow Wayward Weblogger as well as Marc Cantor, but the trip was a difficult one for me, and I wasn’t ready at that point to bridge the real and virtual. I will be, soon, and am planning on taking a few road trips later this summer to meet webloggers who live close by, as well as, hopefully, getting the interest of a few folks to stop by St. Louis this fall for the Open Aire Conference. Well, those folks who are on this continent and can therefore make it that is. I’d also like to attend a few of the St. Louis Bloggers get togethers, though I’m a bit shy of gatherings. Odd as this may seem to people from my obvious in your face style of writing, I’m rather a quiet person in ‘real’ life.

There’s that real/virtual life dichotomy again. I’m frankly envious of those who can mix the two so easily and effortlessly – you see their pictures out and about, hugging this person or that, attending gatherings and shmoozing with other webloggers. More, they not only tell friends and family about their weblogs, they encourage them to get involved with one of their own.

However, I have a strong suspicion that those people who write weblogs read by spouses, kids, and employers tend to write differently then people like me who are, for all intents and purposes, obscured from view because we’ve kept the two worlds far apart.

We’ve all seen webloggers who have pulled postings because they made family members unhappy. We’ve heard about people who have lost their jobs or been reprimanded for talking about their professional lives, even their personal lives online. We’ve also heard about the people who have met their spouses and close friends through online connections. This isn’t necessarily new. But what about the opposite?

What happens when someone’s real world breaks into the virtual? For instance, your sister, wife, mother, brother, son, husband starts dropping comments in your weblog or other weblogs? If it’s difficult at times to separate the real from the virtual in your weblog writing, how much more so is it when bits of that reality appear here and there, like scattered fluff from a dandelion?

Of course, if the ‘real’ person is integrated as part of the environment, and by this I mean introduced and encouraged to participate, as well as supportive of the weblogger’s efforts online, the mix of real and virtual works smoothly. For instance, there’s a certain man of faith who has gracefully and graciously bridged the gap between real and virtual with family, friends, and co-workers.

However, there have been times when I have made comments in other weblogs, and have been surprised and discomfited by the nature of responses made by the weblogger’s family and friends. Not recently, not often, but it has occurred a few times in the past. It jarred just as much as rounding that corner and seeing a co-worker reading my weblog.

The easy rapport that I had shared with the weblogger – the friendship I had assumed – was put into perspective. The associated to the weblogger by the real world responder was saying that no matter how much I may connect with the person, it will never be the same as the connection that person shares with ‘real’ people. With ‘real’ family. With ‘real’ friends.

But I am a real person. Even a real friend, though the connection is virtual. Not family, true. But I am a real person.

There are other times when the ‘real’ person disagrees with a weblog post made by their loved one, or with other weblog postings and comments, even to the point of seeming hostility. These leave you confused as you’re not sure how to react. You want to respond in kind, but then you remember your association with the weblogger and you hold back. Or you don’t, and then you worry if the weblogger will get upset because you just slammed their husband/wife/son/daughter/boss.

You might choose to stay silent, or be tempted to email the weblogger privately asking ‘permission’ to respond freely. Worse, you ask the weblogger what the ‘real’ person’s problem is, as if they’re accountable for this other person’s actions.

You also might wonder if the ‘real’ person resents the weblogger’s time spent within this medium, their associations they’ve made. Are their comments arising from interest, or as part of an effort to ‘punish’ the weblogger? Is it unfair to even consider this? Yes, it is actually. All of it.

We shouldn’t allow a person’s relationship with a weblogger to impact how we respond to them. If we do, then we’re just denying that weblogger the right to have their place in this virtual world. Conversely, we need to be able to respond to that weblogger as we want without being jumped on my the weblogger’s friends and family. Unfortunately, this one is less easy. I know this from personal experience, too.

Speaking of online friends, I wanted to congratulate Sheila Lennon getting married. I enjoyed reading about the experience and the cake and the plans and tired but radiant joy that lit her words. I wished I could have been there, licking the cake crumbs from my fingers at the celebration, but my best wishes are no less ‘real’ for not being there.

My good friend, and fellow Wayward Weblogger Chris is looking at new opportunities, which could be taking him to some pretty exotic ports of call. I wish him the best of luck with his decisions and his moves.

I also want to extend deepest sympathy to Jeff Ward at the loss of his father.

As for me, I was also offered a ‘real world’ opportunity from another weblogger that I had to, regretfully, decline. The circumstances just didn’t work out; too many barriers – health, timing, and economics – in the way.

opendoor.jpg

Categories
Weblogging

Typepad beta weblogs

Recovered from the Wayback Machine.

I’ve noticed some Typepad beta weblogs here and about.

Linotype is one weblog that looks like it tried to find my FOAF.rdf file, if I read the sidebar comments correctly. I didn’t know that Typepad was incorporating automated support for FOAF files. Additionally from this weblog, you can check out a Photo blog created with Typepad’s automated photo weblogging features.

Danny Ayers is also testing the Typepad waters with a site devoted to the Echo Project. Interesting concept of highlighting the important N/Echo discussions and changes, as weeded out from what are primarily fussy edits.

(Danny also commented on the disappearance of John Robb’s weblog – exactly who pulled the weblog pages?)

I’m rather hoping that some of the Typepad features get included into Movable Type. In fact, my biggest concern is, if Six Apart is focusing on Typepad now, how much effort will the company be putting into Movable Type in the future? Typepad is more than just a new weblogging tool – it’s also hosted support. Will there be a commercial version of Movable Type that has the Typepad features, but without the hosting?

I may have missed this discussion somewhere – but I’m still curious.

This leads me to N/Echo. We need the tool interoperability, including export/import and the open API, of N/Echo more than ever now. Many of the weblogging tools are undergoing management changes, which eventually may have webloggers wanting to move from one tool to another. Some webloggers will always want to stay in a hosted environment – it is pretty simple and carefree. But others are going to want to move on, and this includes users of Typepad, Manila/Radio, Blogger, Live Journal, JournURL, Bloghorn, and eventually AOL. We as users must insist on, nay demand interoperability, or risk getting locked into one specific tool.

Saying this isn’t picking on the tool makers, and isn’t being disloyal. I see that missing weblog of John Robb’s and I’m disturbed at how easy it is for months of writing to just disappear. Sure John may have been the one to delete the weblog entries – but when you don’t control your pages….pffft!

You don’t need technical know-how to know that this is Not a Good Thing, no matter how much you like the tools…or the tool builders.

Categories
Weblogging Writing

Thankfully

Mike Golby’s Hello, Mister. Writers like Mike, works like this essay – they keep me here, and keep me coming back.

Categories
Copyright Weblogging

There’s an echo with Echo

Joe Shelby, in the comments associated with my last posting made a good point about “Echo” as name of this weblogging initiative:

Echo is already a name for a product, a Java web application framework, that just released its 1.0 earlier this month, and very nicely under the LGPL license. By choosing “Echo”, the Wiki participants have effectively hijacked that name and may potentially destroy a product from a company doing TheRightThing ™, before that product even gets off the ground.

I posted a note at the wiki about this. I asked that the members form a consensus that they’re willing to use a name that could conflict with another newly released technology. This did start another discussion page.

Wikis are geared to fast, fast, fast. You have to hit the ground running, and be ready to move. Too much for this SysAdmin wore out from getting the Burningbird Network Co-op going (having fun, though). However, in this particular instance, I can also see the power of a wiki.

To me, what brings this all together is combining the technology: wiki to do the actual collaborative work; and weblog to summarize and involve others, to highlight specific points, and make specific persistent comments.

I’m getting a bit burned out on tech at the moment, and need to go back to literature, writing, funnies, life, politics, and photos – but I did want to take a moment to say that I think the wiki combined with weblog approach is very sexy.

Technically speaking. No worries, I’m not that far gone.

Reply from other project:

I do greatly appreciate you asking us before using the name, and
apologize for not having a positive answer. I’d request that you not
name your project Echo. I think the possibility of confusion is too
high, given that both projects are frameworks for building Web-based
applications. I realize that finding a name is very difficult to do (it
took what seemed like forever to settle upon “Echo” in our case).

I am not a lawyer, but I believe that I am required to inform you that
NextApp has a pending trademark registration on the term “Echo” in the
application of “A computer software framework/library used by software
developers for the creation of Internet-and Web-based applications.” It
is my understanding that I am required to state such information in
these circumstances in order to have our trademark be
considered valid, as trademarks must be actively defended. I apologize
again for even mentioning this as a response to your friendly request,
and only state this information because I believe I’m legally obligated
to do so.

I would say that Joe Shelby should take a bow for a good call on this one.

Categories
Weblogging

The Echo Project for Poets

Our echoes roll from soul to soul,
And grow forever and forever.
Blow, bugle, blow, set the wild echoes flying

from Lord Tennyson’s “The Splendor Falls”

If one could typographically represent a blur, then that’s what I would use now to annotate the Echo Project – an online, collaborative, and extremely fast paced effort to define a conceptual data model of a weblog, and then to define politically neutral interoperability functionality, such as weblogging API and syndication format.

The effort has had some discussion in weblogs, beginning with Sam Ruby and continuing elsewhere, but much of the work has occurred in the project wiki, a collaborative editing environment.

One only has to look at the change log to see the number of edits to realize that this is not an environment for the cautious, the tame, or the wiki-challenged (or for those who want to sleep or eat, either). I’m not necessarily cautious or tame, but I do raise my hand for being wiki-challenged. Still, there are points that are solidifying out at the wiki, and I thought to duplicate these here in a format that, if nothing else, will help me understand what it’s all about.

The motivation: (also see wiki:Motivation) I don’t think there’s a one of us who enjoys the battles about weblogging APIs, or RSS, or import/export between weblogging products. Though it is the techies who have to deal with the specifics, these discussions impact us all. Every time a battle rages, we have to stop what we do, which is writing our weblog essays and entries, and add support for yet another button, link, or must have dohicky.

We have to support both RSS 2.0 and RSS 1.0. We have to be able to move our Blogger posts to Movable Type, and our MT posts to pMachine. We have to support comments/trackback/RSS/whatever, because people want to respond, comment, suggest, rant, praise, read, and read more easily.

Still, there are the webloggers, or personal journalists, or what have you that don’t and won’t support these things. They make their pages by hand, eschew comments, and answer with “track who?” This effort doesn’t impact on them, nor should it – the motivation behind this effort isn’t to create a jail about what we do, and how we do it. It’s to provide guidelines for the toolmakers so that all the tools we use, regardless of the tools we use, work together.

The conceptual data model. The question really is, what pieces of data are mandatory in order to meet the needs of a weblog entry? Cutting through the tool specific needs, the group seems to have settled on the following data items and their associated definitions:

Author: There is exactly one Author of an Entry, and that Author is identified by a non-empty name and an optional URI of a person, organization, or system. (A UniformResourceIdentifier (URI) is a short string that identifies a Web resource).

Permalink: The persistent URL for the entry on the Web. There is some debate still going on with this, but looks like ‘permalink’ is really being redefined to be a unique identifier of the weblog entry; and that both a URL and a URI (Unique Resource Identifier) will be required. For instance, this weblog entry has a URL for the individual item (page), and also a post or entry identifier, which would be the URI.

Publication date: This is the date the entry was “published”; the date used to decide where the entry goes in Movable Type and Blogger. The use of the weblogging tools is, I’m assuming nothing more than a reference point. This definition could use some work, but the consensus seems to be heading towards the date that the blogger specifies the entry was published, not the tool and not an automatic timestamp.

Content items: There can be more than one content item and associated with each is: media type (i.e. JPEG, MOV), language (i.e. ENGLISH), and the actual content. There was at one point debate that a welog entry doesn’t have to have any content, but I think that got shot down.

There’s discussion still continuing on these items, but it does look like we’re starting to see some stability. Someone even created an example data page, and as this shows, the only items still being debated are having a last modified date, and that URI of the entry (itemid). Additionally, someone else created a entry model that seems to have captured all the data being discussed, not just the required. If you’re not a techie and want to see what’s happening in a nutshell – go here.

Now, these are the required items, but not the only items. However, the other data items are considered extensions, and therefore optional. This includes:

license – copyright of item (see Creative Commons)
security – PGP Key
metadata – title, subtitle, summary, optional timestamps, version id, and all contributors (in case there are additional authors)

I’ve only quoted the extensions where consensus has been reached. There are other efforts.

Now, what’s next? After the data is agreed on?

Well there’s a Road Map that details what’s to happen. Taking a snapshot, it says:

 

  • Decide on the conceptual model of a log entry. ConceptualModel
  • Decide on a syntax for this model. SyntaxConsiderations (You are here.)
  • Build a syndication format using this syntax.
  • Build an archiving format using this syntax.
  • Build a weblog editing protocol using this syntax (the Echo API).

 

What does this mean to you, the weblogger? Especially if you’re not into the technology? Well, if all major vendors of weblogging products– and that includes aggregators, weblogging tools, weblog search and popularity sites – buy into this the following could happen:

– Syndication Both RSS 1.0 and RSS 2.0 would be replaced by the Echo syndication syntax, and you would only have to provide one syndication file. In addition, aggregators would only have to code to one syndication format. If there’s any pushback here at all, it’s that the tool vendors will most likely want versioning on this process, as well as some slow down – none of them wants to spend their lives recoding for daily updates.

– Import/Export All weblogging tools would support the same import/export format, which means you could easily move between different versions of weblogging tools. To my friends in the audience moving from Blogger to MT or other tools now – your job would be much easier.

– Common API All weblogging tools and perhaps peripheral tools would support a common API. This means, at a glance, we could post trackbacks to all weblog posts regardless of toll. But more, this also means that you could use any weblogging tool front end to post weblog posts to any weblogging back end. This opens the door to a new set of tools, as well as new technologies to work on top of them – audio/video posts, posting from email, posting from your phone, and so on.

This is the biggie. This is the grand banana. This is where the rubber hits the road. Here’s a scenario for you: you’re on a road trip and you’re writing to your desktop weblogging front end tool (someone else is driving we hope). You put the post in send mode and when you computer finds a passing WiFi signal, quick as can be, your entry is posted. Or don’t bother with the computer, post with your cellphone. Of find a kiosk at a rest area along the way, and send a post, annotated with your map location.

Doesn’t matter your tool – works with all of ‘em.

Of course, this is all supposing that our fictitious weblogger is a wee bit obsessive, and not that any of us are – not us – but it is fun to think of the fanciful situations in which a person could post, isn’t it?

Mine is that I’m in a deep submersible, hunting the Colassal Squid, and I’m blogging the encounter just as I’m about to be swallowed. No! Wait! After I’ve been swallowed!

“May be quiet for a while, I was just swallowed by a squid…”