Categories
Just Shelley Weblogging

Weblogging and 9/11: Something kind of broken

We look at today’s social media world post-Trump Presidency and we see a highly disconnected and fragmented world. The media proclaims it’s never seen society so polarized, but we’ve always been polarized. The only difference now is who controls the visibility of the fragments.

Unlike earlier years, what was fit to print, or fit for all of us to know, was controlled by the media. First the newspapers, then radio, and finally TV.

Now, we’re all publishers, even if all we publish is 280 character blurbs to a handful of people. And as publishers, every single one of us proclaims as loudly and emphatically as we can our interests and our beliefs, and all too frequently, our disagreements. It’s a wonder we can still think with all this chaotic noise.

It never used to be this way I think to myself, as I spend time recovering old weblog pages from the Wayback Machine. Before there was Twitter, and before there was Facebook or TikTok or Instagram, we had weblogging: a tightly integrated community of early practitioners who linked each other in a continuing dialog that was equally special and mundane, profound and silly.

Yet at the very beginning, we were broken.

9/11 and the rise of social media

Weblogging wasn’t the first example of social media. I’d say that honor goes to Usenet, which was fairly popular before the invention of the web. But weblogging made social media accessible to everyone, not just enthusiasts and geeks.

This page is as good a history of weblogging as I can find online. As you can see, weblogging started not long after the web, itself, though the number of webloggers began small. But this all changed with 9/11.

I remember watching the horrific events of 9/11 unfold in real time on TV that day. We watched as the planes hit and the towers fell. In the days after 9/11,  many of us wanted to reach out to people, to connect, and to talk about the events and try to make sense of what happened.

At the same time, our country was in a virtual lockdown. We’ve forgotten with the recent COVID-related restrictions that this isn’t the first time the country has been locked down. It isn’t even the first in recent history. The photo at the beginning of this writing is one I took from my apartment in San Francisco. Two days after 9/11 the military showed up with barbed wire and concrete barricades, blocking off a major street in order to protect the machinery of the Bay Bridge.

A combination of wanting to connect while physically distanced combined with new tools and inexpensive hosting led to an explosion of weblogs. And thanks to blogrolls and linking, we formed communities of seemingly like-minded people who became close even though we might be on the other side of the world from each other.

However, if 9/11 brought us together, the events following 9/11 soon started tearing us apart.

9/11 and the fracturing of social media

What brought on this writing was spotting a graphic from a Wayback Machine archived page of my friend Jeneane Sessum’s Allied weblog. I had recently discovered my old Radio weblog pages in the Wayback Machine, and shared the discovery with my Facebook friends. Many of these friends are people I’ve known for decades now because of our earlier weblogging connections. So, I posted links to some of their pages, too.

In a page from 2002, Jeneane had posted a sidebar graphic that read “1st off Mike Sanders’ Blog”.

Graphic reads 1st off Mike Sanders' BlogI hadn’t thought about this event, or Mike Sanders, in years. The graphic brought back the memories, albeit a bit fuzzy from time.

I searched throughout my Wayback Machine archives for the same time frame, and found the post that explained what this was about. I’ve recovered it to Burningbird, but you also have to look at the page in context.  It links a March 1, 2002 weblog posting that read:

I was out of town but had to return early.

This morning I received an email from Mike Sanders asking me to remove his weblog link from my blogroll and he has removed my weblog from his. The reason is because of my “moral equivalency” arguments last week, and because I linked to Daniel Ord’s piece Stereopticon in Friday’s post.

According to Mike:

    • Unfortunately some of my fellow bloggers understand and/or support both the Palestinian terrorist reign against Israel and terrorism against the US. I can longer in good conscious include those people on my blogroll list and I respectfully request anybody who understands or supports Palestinian terrorism or Islamic terrorism to please remove my name from your blogroll list as well.

I wrote the following in an email to a friend, regarding my posting on Friday:

    • No one noticed in my posting, my use of “viewpoint”, not opinion. Though sometimes treated as synonyms, they aren’t the same thing. A viewpoint is a point of view, the culmination of all our life’s experiences. How we see things. From this issues both action and opinion. Without understanding and respecting each other’s viewpoints, we can’t hope to understand where each of us is coming from when we speak or act.
    • I started my list with Ord because he is doing just that — he’s showing two viewpoints of the same incident. Without understanding the Palestinian viewpoint of the WTC tragedy, we can’t hope to stop these incidents from happening again, because we’ll never understand why they happened in the first place. The title of his piece tells us this — stereopticon.
    • stereopticon — viewpoint
    • I deliberately listed absolutely conflicting opinions, and invited the audience to understand the different viewpoints.

My first time being accused of supporting terrorism

Two things made Sanders’ email stand out. The first was that it was the only time when someone had asked me to remove a weblog link, not just remove a link to my page from their weblog. Today, this would be equivalent to someone on Twitter blocking you, but having to ask your permission, first.

The second was being accused of supporting terrorism because we weren’t willing to condemn Palestinian actions post 9/11. Mike Sanders was a strong supporter of Israel. In the process, he not only stepped over the line into Islamophobia, he raced across it. To the point where he would label us terrorists solely because we were willing to listen to other viewpoints.

Being labeled a terrorist by some extreme conservative isn’t all that unusual on Twitter or Facebook today, but it was a shock back in the early days of weblogging. Especially when the person leveling the accusation was a friend, or at least, you thought he was a friend.

And the fragments would only grow as our group broke into pieces over the Bush invasion of Iraq.

Killing the Blogroll

My response to the Sanders’ request was to eliminate my blogroll in its entirety. I had been considering doing so anyway, because I thought it was better to introduce folks through my writing and referencing them, rather than a static list of links in the side of the page.

If you random sample my old weblog URL on the Wayback Machine in later years, you won’t see a blogroll. Hell, you won’t even see more than one page column to my site now, in deference to mobile devices.

Mike Sanders’ request was the tipping point to the decision. I didn’t want to list or be listed or be beholden or not to someone because of links or not. I didn’t want to endorse or be endorsed. If I liked what someone wrote, I wanted to point it out to folks. If I wrote something interesting, I hoped for the same.

barbed wire

Thankfully, I never had anyone email me and tell me not to link to their writing. Perhaps this will change as I become more active in this space again.

End of Story

So much writing about something that happened so long ago. And probably much ado about nothing.

Mike Sanders quit his weblog that December, but he was back weblogging the following spring. And yes, he had a blogroll, and yes, I was on it.

It wasn’t as easy for me to push it all aside, though. It wasn’t just being accused of supporting terrorists. It was the idea that someone felt that they could tell me what I could or could not do on in my own web space.

Yet here I am, on Facebook and Twitter, letting them tell me what I can or cannot do in my own space.

There’s something kind of broken about that.

 

 

 

 

 

Categories
Weblogging

Comments cont.

I just published the second part of the essay on comments at Many-to-Many:

When I chastised the other person, when I suggested how they should change their interaction and behavior, we were no longer peers discussing a volatile subject – I had assumed a parental role, trying to force a child role on the other person. And, in some ways, Sam assumed a parental role when he chastised me.

I hope you also take a moment to read what others have written on this subject by following the trackbacks attached to my earlier posting, and those who have trackbacked to Sam’s postings. There are many eloquent and thoughtful arguments on what is not an easy issue.

Categories
Weblogging

Weblogging: More Than Words

Two friends have stopped by to say hi since I turned comments back on.

Bill mentions the Radio Userland days,which puts us back in very ancient weblogging territory. So ancient that today’s TikTok kids weren’t even born when we got together in Userland pages.

I also used to have a Userland Manila weblog, but those days are permanently gone. The Manila weblogs were lost in the Wayback Machine because of a bot-killer Dave Winer implemented. Sad, but such is life.

AKMA also stopped by and discussed doing weblog  recovery for his space, but what about the comments? We can recover the words, but we can’t recover the comments.

Indeed this is the biggest loss when we’ve moved our spaces all about: we can move our words, but we’ve left the community behind.

Thankfully, Wayback Machine rode in and saved the internet. Not only does it preserve a page, it preserves the theme of the page, the look and feel and in-place context. It also frequently preserved the comments.

I may have recovered the words to Cheap Eats at the Semantic Web Cafe in this space, but the Wayback Machine saved everything else about that old posting in its space. And I’m eternally grateful for the gift it’s given us.

You see what I did there? I did weblogging.

Categories
Writing

The Old is…still old but at least it’s back

The second part of my Burningbird server re-awakening from the dead is my effort to find any and all past writings and import them into this weblog, one at a time.

I’ve had so many variations of weblogs: some at domains I’ve controlled, others at domains I haven’t. I was able to export the posts from many of the domains, but I haven’t loaded them back into this place. The task just seemed too daunting.

Then I realized something: I’m retired. I can do stuff like this now.

As I note in my About page, you can see many of my writings thanks to the wonderful people at the Internet Archive, and their incredibly important Wayback Machine. Still, I want the posts in one single spot, even though so many of them are so dated.

As I import the page, I set the publication date to the original publication date, which is why you won’t be seeing them here on the front page. I may, from time to time, link an older story in a new posting, for grins and giggles.

I’ve also turned comments back on, though the comment form is a bit buried with this theme. Comments close five days after I post, so make your point quickly. Your first comment will be held in moderation, but after I approve it, you should have freedom to post at will. Do let me know if you run into issues.

It’s been fun to go through the old posts. I can’t believe some of the tech way back when. And we won’t even get into the politics.

Categories
Technology

Moving servers

It was time for me to upgrade my version of Ubuntu, from 18.04 to 20.04. I upgraded my software, thought I had a clean site, and tried to upgrade in place. After all, upgrading from 16.04 to 18.04 was a simple one line command.

Moving from 18.04 to 20.04 was not so simple, and the upgrade failed. Time to do a manual build of a new server and port my site to it. Which also ended up being more complicated than I thought it would be.

Moving to 22.04

First, if I was going to go through all the work, I was going with the latest Ubuntu LTS: Jammy Jellyfish, otherwise known as 22.04. I spun up a new Linode instance of 22.04 and set to work.

The LAMP installation went very well. I ended up with not quite the latest Apache, since the absolute latest wasn’t supported on 22.04 yet. However, I added the famous Ondřej Surý repository and I was good to go:

sudo add-apt-repository ppa:ondrej/apache2 -y

MySQL is 8.0.29 and PHP is 8.1.

All that certbot stuff

I had manually built a new server when I went from 14.04 to 16.04, but times have changed. That move was pre-HTTPS, pre-HTTP/2, pre-HSTS (HTTP Strict Transport Security), well, basically, pre-everything. I had the support in my existing server, so I know my pages and installation are clean. But the sheer amount of work to set it up again was a bit daunting.

Thankfully, since I had made these moves in the past, my site was already clean. All that I needed to worry about was installing certbot to manage my Let’s Encrypt digital certificates.

You’d think moving a server wouldn’t be that unusual, but neither Let’s Encrypt nor certbot cover what to do when your certificates are on one server and you need to set them up on another. Searching online gave me two options:

– copy everything and change symbolic links for the certificates

– just install new certificates on your new server, and delete the old

And that’s when things got sticky.

Where am I and who is managing my IP address?

When I made the move to 16.04, I was manually setting up my network configuration using ifupdown and editing the /etc/network/interfaces file. But when I went to 18.04, netplan was the new kid on the block for network configuration.

The problem is, I had one foot in both camps. So when I tried to access a test page on the new server, it failed. I certainly couldn’t run the certbot web validation for installing a new digital certificate if I couldn’t even serve a simple page on port 80.

In addition, Linode has the ability to manage network configuration for you automatically, so if you change servers and IP addresses, you don’t have to do a thing. But when I tried to turn it on, even SSH no longer worked. I had to restore the site from a backup.

It took a bit of painful digging around, but I finally upgraded my network configuration to netplan, and only netplan. I could now use SSH again, and install a new digital certificate for my test domain. But then, things got tricky again.

I hate the old propagation thing

When I created the new Linode server, I installed it in the Atlanta data center rather than the Dallas center I was using with the old. After all, Atlanta is now only a couple of hours away.

But doing so meant when I switched, I had to update my name registrar to set my DNS entries to the new server IP addresses. This is a pain, in itself, but it’s also a bit of a fragile time when trying to determine if my site will work on the new server. After all, you don’t want to permanently change your IP address only to find out your site doesn’t work, and then have to change it back. And digital certificates kind of mean you have to have all or nothing.

Thankfully, Linode had a peachy keen workaround: swap IP addresses. If two servers are in one data center, you can swap the IP address between them.

Of course, doing so meant I had to migrate my existing site to the new data center and change the DNS entries, but still, it would be worth it to be able to switch back and forth between servers when making major modifications. And the migration should be a painless button click from the Linode cloud control manager.

So, I migrated my old Linode VPN to Atlanta, and then tried to swap the IP addresses. Crash and Burn.

IPv4 and IPv6

What I didn’t know about the Linode IP swap facility is that it only swapped the IPv4 address, not the IPv6 address. So when I did the following

ip -a

My IPv4 address reflected the new server, but my IPv6 address reflected the old, and everything was just broken. Again.

The only recourse at this point was to bite the bullet, make the move to the new server, do the DNS propagation, and then deal with the digital certificates. I put up a warning page that the site might be off for a time, had a coffee. and just made the move.

After the move, I thought about doing the Let’s Encrypt digital certificate copying like some folks recommended, but it seemed messy—sort of like the network configuration issue I had just cleaned up.

I used certbot to do a new installation, and the move was flawless. Flawless. This is really the only clean way to move your site to a new server when you’re using digital certificates:

– Make sure you site can support port 80, at least temporarily

– use certbot to generate new digital certificates for your site(s)

– delete the old server and certificates

Five Years. I’m good for five years.

So here you are and here I am: on the new server with all new software on the data center closest to me, with clean, uncrufty network configuration and sparkly digital certificates.

Best of all?

Jammy Jellyfish has standard support until April, 2027. I’m good for five years; ten if I want extended support. And who knows where I’ll be in ten years.

Probably back here, doing it all over again.