Categories
Weblogging Writing

Google is not God, Webloggers are not capital-J journalists, the only thing emerging is my fear of war, and a headache

Recovered from the Wayback Machine.

Though my opinion will not be shared by the majority of those who read this, I greatly appreciated the article appearing in the BBC News, Is Google too Powerful. Not only did the writer, Bill Thompson, challenge this continuing nonsense about webloggers ‘replacing’ mainstream Captital-J Journalism, he also exposed the falsity of the godhood with which Google is treated.

Of the so called ‘superior accuracy’ of webloggers, he writes:

The much-praised reputation mechanism that is supposed to ensure that bloggers remain true, honest and factually-correct is, in fact, just the rule of the mob, where those who shout loudest and get the most links are taken more seriously.

It is the online equivalent of saying that The Sun newspaper always tells the truth because four million people read it, and The Guardian is intrinsically less trustworthy as it only sells half a million.

 

When it comes to world news and opinion, he or she who gets the most links, wins in the world of weblogging. Those with the pareto charts and your esoteric algorithims of popularity tend to prove this out. According to the charts, rather than a new form of connectivity, we’re really just another instance typical of medieval community: with the indifferent, smug supremacy of the elite at the top and rule by the mob at the bottom (we know about the viablity of mob rule for fair and ethical treatment of either person or subject).

Within this view, occasionally the mob and the elite might join forces, briefly, and we might help with a story, such as Trent Lott and his big mouth. For the most part, though, we’re a bunch of editorialists without much concern for research, fact checking, or accuracy. That’s okay, though, because I didn’t start writing this to become yet another journalist-wanna be. Nor an elite. Nor part of a mob.

I’ve heard two common threads this last week: Weblogging is a whole new form of individual expression, without hinderance from editor or government; weblogging is a movement with power to report and shape the news. You can’t have it both ways — either we’re individuals with individual interests and independent thoughts and writing, in which case we’ll seldom have impact on the accuracy or direction of the news; or we’re a mass mind with too little independence to think outside the herd, but with enough power to stop war, throw out presidents, and change the course of history.

You can’t have it both ways. Either we’re different and unique and independent. Or we’re not, and weblogging is nothing more than a variation on an all too common societal theme.

Michael O’Connor Clarke wrote about journalism’s failure to cover the story of the deaths of thousands of Iraqi soldiers during our first battle with Iraq. Michael writes:

This suggests an urgent need to recruit and train an army of Iraqi bloggers, either here in the ‘Free West’ (*cough*), with strong connections to feet & eyes still resident in their homeland, or preferably right there in the thick of the horror.

We should arm them with satellite WiFi blogging tools and digital cameras to record and publish the unvarnished, un-CNNed truth.

 

What Michael forgets is that there would have been no witnesses because the people would be dead. In the starry eyed rush to show the glory of weblogging, and it’s full unleashed power via Google, he neglected to remember that the people were dead. Dead people don’t weblog.

We’ve long had the ability for people to “get the story out”. We have telephones and cameras, and if anyone had access to this at this battle, the story would have gotten out. But the only people who witnessed this act were those who died, and those who buried them. And the reason we know the story now is that some of those who did the burying are speaking out.

Who would have blogged this? Ghostly fingers from a grave?

Forget the pareto charts, and the Google and Blogger crap and focus on what this war is going to be like. We, the US and a few allies will invade without UN support. We’ll start with a barrage of missles and remote weapons, battering the Iraqi until we bring them to their bloody knees. Using this approach we can, hopefully, minimize the number of our troops lost. Though I agree with protecting our troops, this tactic is also the one most likely to maximize the deaths of civilians, as well as the destruction of services necessary to the survival of the people.

In retaliation, Saddam Hussein will blow up the oil wells, the dams, and the bridges. He’ll deny food and services for millions, effectively creating a human wall of misery around himself to protect himself from the invading army. However, even those within his protective sphere won’t be undamaged, because they’ll be the ones being bombed.

Saddam Hussein will also release whatever chemical and biological weapons exist, and he’s not going to care who gets exposed. His own people, his neighbors, Israel, our soldiers. For the first time in history, there will be one thing commonly shared by the peoples of the Middle East — exposure to weapons that should never have been invented. Excuse me if I don’t clap.

During this battle, the Iranians will most likely make inroads into Iraq, and the Kurds will begin the battle for control of the country, since they’ve already been told by the White House that they’ll not be allowed to run the country after Saddam Hussein is gone. We’ve promised Saudi Arabia and Turkey there will be no elections, no democracy. In addition, the Kurds will have been treated badly and if there’s one thing we know about the Middle East, the concept “an eye for an eye” is alive and well in that region.

In the midst of what promises to be one of our more vile wars, with human warring against human in our most inhumane ways, we’ll find our lone bloggers, bravely sitting at laptop with satellite phone, blogging the story so the truth will be told. I don’t think so.

We won’t need the bloggers to tell us the truth. We’ll see the millions — yes, millions — who are starving, the soldiers as they suffer the effects for years to come of the agents used against them. We’ll be able to smell the smoke of the oil fires for years into the future, and we’ll feel the effects the smoke will have on our weather.

There will be no mass grave large enough to bury those that die in this war we say we want to fight for the good of humanity.

I don’t want to rain on the parades of the enthusiasts. I don’t want to dampen the spirits and enthusiasm of those, such as TomJeneane, Michael, Joi Ito, and others, who think everything will be different if we all just weblog. I admire and cherish their joy and dreams based on our connectivity.

Additionally, I don’t want to rain on the “Poets against War” and the “Readings against War” and the “nudity against war”, and the other refined forms of protests. Any sincere protestation of war should be respected.

I remember the starry eyed enthusiasm of those who protested against the Vietnamese war years ago. I remember because I was one of those who protested, one who placed a flower into the barrel of a guardsman’s rifle, who linked arms, who painted peace signs and flowers on my face, who sang “Give peace a chance”. Thankfully, I was not one of those who said just vile things to the war shocked, exhausted veterans as they came home.

But I was one of those who thought it was these protests that stopped the war, only to realize as the years advanced, that it was those who were silent, the vast majority who did not march, who stopped the war. And they did so because they became tired of the body bags coming home.

The St. Louis area has over 400,000 people, and of those, probably only a tenth, if that, have a computer. Of those, a scant 300 or 400 weblog. It is those who don’t weblog, who will stop the war in this country. And, if I may presume on some cultural similarities, it is the same type of person who will stop the war in other countries.

Joi Ito sees weblogging as small groups of people formed around shared experience or interest. Within these groups, he sees a positive feedback loop that pushes a signal above the noise, identifying important information for other weblogging groups to pick up. The signal grows in strength as more groups link to it and the signal eventually, if important enough, gets picked up my those outside of weblogging. As an example, he points to the recent anti-warpro-war debates

This is a good explanation of what happens with some of our interests, such as the recent Google/Blogger merger. However, this tends to only happen when we sustain the signal for a significant period of time, as we did with the Blogger/Google merger, and as we did with Trent Lott. It’s not enough that we push an item into the charts — it’s that we hold it there sufficiently long enough to attract the interest of others.

Unfortunately, webloggers are nothing if not little birdies easily distracted by some bright shiny new toy just around the corner. Frequently, we indulge in cross weblogging circle conversations; rarely do we do so for any sustained length of time.

As for the aforementioned debate, the quality of it is no better, nor worse, than what one hears on the street, or in the next booth at the local restaurant. This isn’t to detract from those who took the time to participate in this debate. It is to say, in effect, what makes anyone think we’re so erudite in our debates that anyone other than webloggers would want to stop long enough to hear what we have to say?

Joi Ito also writes:

Many bloggers begin their weblogs to communicate with their strong tie peers. They will mostly link to and communicate within their small group.

 

Of the group I linked to when I first started, half are no longer weblogging, and most of the rest, I no longer link to because of changed interests. Of the people I linked to a year ago, several quit weblogging, some went in directions I couldn’t follow, and others, well, for one reason or another, we just stopped communicating. Of the people I link to now, they’ll stay on my blogroll regardless of their views because will no longer de-link another active weblogger. Even if they go in directions I can’t follow, I’ll still read their adventures along the way. How will my blood flow except by the push it gets when I read words that make it boil?

Will I my blogroll grow? Sure, but I’ll manage.

My point is that whatever weblogging circle we’re in at any point in time, it isn’t a fixed circle, and neither is it harmonious. The ‘best’ weblogging circles, if best is the correct word, is one in which the members don’t all agree. Otherwise, reading each others posts would be like looking at ourselves in the mirror all throughout the day — no matter how vain we are, we’re going to get bored eventually.

This means though that seldom will we all agree and when we do, seldom will we sustain that agreement. And because of this individuality, seldom will we push a signal above the general noise long enough to be heard by others. Our acts of individuality counter-act the formation of a mass-mind with enough power to effect change globally, though we may wreck chaos, at times, about ourselves locally.

I started weblogging because I wanted to write, and I wanted to share what I write in the hopes that others might like it, be moved by it, even grow from it. I’d like to think I could stop this war with it, but I can’t. And nothing Google can do with weblogging will change that.

What irony: by being an individual and writing on what I want, when I want it, and encouraging others to do the same, I’m trying my best to disrupt this push for a mass-minded power capable of possibly changing the very war I fight with all my breath.

You know what moved me today? poem, a songa bit of writing, a shared picturespoken words, a giggle, a new story. That’s what moved me today. They won’t move the world, but they moved me.

Categories
Burningbird

All I want is a server all my own

My two year weblogging anniversary is coming up, April 2nd. Two years ago on that day, I signed up for a Manila account at burningbird.manilasites.com, though I took a hiatus in the middle of the year due to my divorce and subsequent move to San Francisco. Some of the entries have been deleted but some are still there in October and November.

I know what I want on my anniversary: I want a server of my own. I want a dedicated Linux box with loads of space and great bandwidth, maintained by a reliable ISP. I want to load it up with Movable Type and software for managing our photos and our music, and Tomcat for Java applications as well as Python and Perl and PHP.

I want to offer my server as home for my favorite webloggers, and also want to provide a place for people to post if something has gone wrong with their server — sort of a community emergency bulletin board weblog so to speak.

I want to finish the Java-based applications I was building but had to stop hosting because I lost my server late last year. Then the next time I interview for a company I want to work at, and I start to freeze up at the questions because I’m tense and a bit scared about finding a job, I can point to the applications and say “See. That’s what I’ve done. That’s what I’m capable of.” They still might not hire me, but at least I won’t be embarrassed.

We can share Movable Type libraries, and when the next release is out, and we’ve tested the release, I can upgrade us all at once. Quick and easy. And there’s so much great open source, free software for doing anything we can want available. All we need is space, and the ability to install the software.

Hosting Matters is very cool, and they were very responsive to my email spam problem. But I want a server of my own. That’s what I want.

Categories
Burningbird

Variations on a nasty theme

Not long after I went to bed last night, my friendly neighborhood spammer changed the name he was using while sending his or her virus-laden emails and I woke this morning to 803 new emails with variations of failed delivery, thanks for signing up, and messages of rejection due to the presence of a virus.

I’ve pointed the new email address to the blackhole, but I’m now wondering whether this ‘attack’ is direct or indirect. Is the person using a program to generate new email addresses, while still using the same domain? Or did the person read that I had pointed the old address to blackhole, and change the name manually. There’s a world of difference between the two, and it’s bothersome not knowing which is the answer.

I guess we’ll see the ramifications from this one over time. There is a potential of the domain, yasd.com, being blacklisted though spam blacklists are usually based on IP address rather than domain names; those that operate spam blacklists know how easy it is to use someone else’s domain.

How easy is it? Go into your email and change the reply-to email address. That’s it. Of course, my kiddie hacker is also using open ports on people’s machines to send the emails so that they’re not traceable. Might even have used an open port on your machine ifyou don’t have firewall protection. How safe is your machine? How about your domain?

We talk about digital identify and protecting said identity from impersonation and theft, but I’m not sure those of you who talk about this added level of sophistication being layered on the existing infrastructure of the Net realize how problematical it is just to ensure the safety of our domains, much less our personal identification. I think in many ways that’s why I don’t join in the digital ID conversation, though it is a topic I was greatly interested in a few years back. When you realize how wide open the Internet is, and how many people connected to it have the barest understanding of what it is they’re connected to, you become amazed that the Internet is still operating.

The only reason you’re still able to read this weblog is redundancy.

My hope is that the hacker is using a generated email address and eventually, the program will move on from my domain. Or a meteor falls from the sky and lands on the hacker’s machine…and the hacker.

Categories
Burningbird

Getting hammered

Someone used a fake email address from my ‘yasd.com’ domain to send a huge spam emailing and I’m getting hammered with email rejections and mail delivery system failures.

If I find the little creep that did this, I’m going to take out that virus code someone embedded in my comments and use it to fry his machine.

Don’t send email directly to me until I send all clear. All clear. The email to the bogus email address is being directed to the email blackhole.

Update

Email is originating from spedia.com servers.

Update Two

Nope, they were victims, too. This could be an email virus. Get an email from ‘zhujil@yasd.com’, delete immediately.

Update Three:

Have forwarded all email to email blackhole, so I’m no longer getting all the responses, though my server is still getting hammered (less than if delivered, though). Question: who is email spam/virus expert in audience? I want to find out where these things originated. I’ve kept all the emails with the headers.

Last Update:

The email forwarding didn’t take at first, but is finally working. All total over a 1000 emails in a very short time. Many of the rejections were from automated virus scanning systems, so I know that the email did contain a virus.

I’m going back to bed.

Categories
Weblogging

Morphing URLs

Recovered from the Wayback Machine.

I signed up at Blogrolling.com to manage my blogroll, and you can the results in this page. Scroll down and you’ll see the ten most recently active webloggers in my virtual neighborhood. Click the “more…” link and you’ll go to my Blogroll page.

I’m using the blogrolling.com feed a couple of different ways. I’m using the raw PHP feed in this page, because it’s simple to process. However, I modified the code of the feed to only display the recent ten updates. I’d create another list, instead, and limit it to the most recent ten (a feature at blogrolling.com), but that’s only for those who have paid, and money is in short supply at the moment. So I tweaked the code on my own.

In the Blogroll page, I’m accessing the feed as RSS, and then using the PHP XML classes to process the data. By doing so, I can access the individual elements of the feed, such as the URL of the weblog, which I then use with my new Talkback feature.

(I’m thinking of accessing the RSS feed in this page and then caching the feed locally, to be used by the blogroll page, and lower the number of hits against the blogrolling.com site. We’ll see.)

Blogrolling.com makes use of changes.xml from weblogs.com to check for recently updated weblogs, a feature I incorporated into my blogroll. I really appreciate this, because it lets me see who’s updated without having to use an RSS aggregator, something I’m not fond of.

The problem, though, is that we’re inconsistent in how we format URLs. For instance, a person might update weblogs.com as “http://www.myweblog.com/”, but a blogrolling.com customer adds them as “http://myweblog.com”. These are two different URLs, syntactically, even though they point to the same weblog. Unfortunately, then, when the person updates their weblog, they’re not floating to the top of my blogroll.

The problem is that we all have different understandings of how a URL works, and what we need to use in a URL, and what not. Time for URL 101, I think.

First, the ‘www’ that is so common in most URLs today. Originally, the ‘www’ part of a URL stood for the hostname of the server on which the website lived. The complete name, ‘www.myweblog.com’ then translated into a specific IP (via DNS lookup of the domain) and a specific server.

Things have changed quite a bit and we now have something called virtual hosting. What this is, among other things, is the ability to create a sub-directory, such as (web server basepath)/weblog, and have the web server map weblog.domainname.com to that sub-directory. For instance, I have the following sub-directories, each of which is paired with the mapped subdomain:

 

basepath/weblog – weblog.burningbird.net
basepath/rdf – rdf.burningbird.net
basepath/articles – articles.burningbird.net
basepath/www – www.burningbird.net
and so on..

 

The last one in the listing shows www.burningbird.net, but I don’t have to use “http://www.burningbird.net” to get to my top-level web site — I can use “http://burningbird.net”. The reason is within my web server configuration files, the URLs “http://burningbird.net” and “http://www.burningbird.net” map to the exact same sub-directory, the one named ‘www’. You’ll find with most modern web installations that “http://www.domainname.com” and “http://domainname.com” map to the same sub-directory on the server (something you can easily check through your browser).

Just think: All that time when you’ve been typing in ‘www’, when you could have saved key strokes. Why you probably could have saved enough time to go and buy a Krispy Kreme.

(Note, though, that this mapping isn’t consistent, and you may actually get errors if you omit the ‘www’. Don’t you love individualism in web access?)

So the use of ‘www’ isn’t mandatory. Neither is the use of the trailing forward slash (‘/’) at the end of the URL, as you’ll see some people use.

In olden times, when you used the trailing slash at the end of the URL, the browser knew that you were accessing a directory not a file, and you saved the browser a second trip to the server to determine this. However, all modern browsers now assume that “http://yourdomain.com” and “http://yourdomain.com/” are the same, and you don’t get any performance benefit from the use. However, if your weblog is off of a sub-directory, such as “http://yourdomain.com/somedirectory/”, you will still, usually, get a performance benefit using the trailing slash.

However, the use of the trailing slash is one more difference in our URLs. At this point we have the following variations all pointing to the same web page:

 

http://www.yourdomain.com
http://www.yourdomain.com/
http://yourdomain.com
http://yourdomain.com/

 

But there’s yet another variation — specifying a file, explicitly.

For most of us, our weblogs are located in a page named ‘index.someextension’. It could be ‘index.html’ or ‘index.htm’ or ‘index.php’ and so on, but it is the index file, which is the default file to load when a directory is specified without a file name (this differs slightly based on web server and configuration).

To load my weblog, you can access “http://weblog.burningbird.net”, and you’ll get “http://weblog.burningbird.net/index.php”, because my web server is configured to look for files in the following order:

 

index.html
index.htm
index.php
and so on

 

As long as I don’t accidentally include an ‘index.html’ file in my directory, you’ll get the index.php page instead.

By not specifically giving the file name extension, what I can do is change the type of file, from index.html to index.php, and you all don’t have to change your links to me because you’re only specifying the directory, not explicitly the file name. In fact, if a person is using the default ‘index’ file name, you shouldn’t use this in your blogroll link to them, because it will break if they go to a new file format.

However, we now have yet another variation of the URL:

 

http://www.yourdomain.com
http://www.yourdomain.com/
http://www.yourdomain.com/index.html
http://yourdomain.com
http://yourdomain.com/
http://yourdomain.com/index.html

 

All in all, our use of URLs is about as distinct as we are, and I’m amazed that the bubble up feature of blogrolling.com works, at all.

To attempt to work around these challenges, I added people to my blogrolling.com list when they showed on weblogs.com, using the URL format they used with their pings. In addition, I checked the person’s perma-links, to see if they used ‘http://www.domainname.com’ or ‘http://domainname.com’, and so on. It became a treasure hunt in a way, but the golden egg in this hunt is a correctly bubble upped URL when the person updates.

BUT…

This has left my Talkback feature in a difficult state. The reason is, that the URL you use to ping weblogs.com, usually generated by your weblogging tool, isn’t the same URL you used in my comments. So, you might bubble up to the top of my blogroll, but querying for the blogrolling.com supplied URL in Talkback results in no comments showing.

Pain in the butt.

What we need is consistency. Perhaps we need a URL cleanup day, to clean up the URLs we use in our blogrolls. And a common guideline for URL usage, such as the following:

 

  • Use ‘www’ only if you need to. You don’t need to use ‘www’ unless your page doesn’t resolve without it.
  • Use the default ‘index.extension’ filename for your weblog main page.
  • If the default filename is used, don’t including this in the blogroll link. You’re putting a burden on the weblogger to have to use redirection if they want to change to a different page format.
  • Use the same URL in your comments that you use when pinging weblogs.com or blo.gs. In fact, be consistent with your weblog URL regardless of where you use it.