From the tragedy of a mass shooting to a new hope for the future

“Shooting reported at school”

You read the words in Twitter and feel your shoulders drop, your head lower, and you don’t want to hear any more, but you want to hear everything.

The scenarios run through your head. “A teacher accidentally shot themselves in the foot.” “One kid was showing another a gun he found at home and it accidentally discharged.” “Troubled teen kills himself.”

“A shooter entered the school and killed several people using an AR-15 and a high capacity magazine.”

It’s almost overwhelming when you realize that you’re hoping you’ll read about some troubled kid killing him or herself, because you don’t want to read the alternative.  But it was not to be on Valentine’s Day at Marjory Stoneman Douglas High School.

Continue reading “From the tragedy of a mass shooting to a new hope for the future”

We Kick Out Trump and Greitens. Then What?

The St. Louis PD headline reads Missouri Republicans debate whether Greitens should stay or go. The debate is centered around revelations of the Greitens’ affair, and especially whether he photographed a bound, blindfolded woman and threatened blackmail.

Of course, discussions about kicking out a Republican in charge are not new this year. They happen all the time with President Trump. People breathlessly wait for the culmination of Mueller’s Russian investigation, hoping for a criminal indictment and impeachment.

Just stop for a moment, though, and think about what would happen if Greitens was forced to resign, and Trump kicked out of office?

Continue reading at The Democratic Difference.

Break the Internet

For the next two days, when you first access this site, the following image will show, with a form you can use to send your concerns to Washington DC. The FCC is about to destroy everything we hold dear about the internet, while pretending to serve the public. Don't let them. Save the Internet form

Brought to you by HTTPS

As you can see when you access this page, I’ve made the move to HTTPS. I detail the experience at my new technology-only site, Shelley’s Toy Box.

I upgraded my server before I made the move, and eliminated all the cruft. I also moved my DNS records over to my name registrar, rather than manage on the server.

All in all, the experience was challenging at times, but also interesting. It was fun tweaking with the tech, and I need to do more tech tweaking in the future.

One of the downsides to the move is removing my archived statically generated HTML pages. I now get, on average, over seven hundred 404 requests a day. The numbers will go down as I gradually add the older content into this site, and as search engines drop references to the missing pages. Still, I feel like one big link black hole right now.

The Wayback Machine is extremely helpful when it comes to recovering pages that, for whatever reason, I don’t have backups for. I even found a link to my earliest weblog, a Manila site, hosted by Dave Winer and Userland.  I was excited when I found the link. My reactions to the events of 9/11 were recorded in my Manila weblog, and I don’t have a backup of the old posts.

I could have dropkicked Dave Winer when I discovered all the pages have the same message:

Your crawler is hitting our servers too hard. Please slow down, it’s hurting the service we provide to our customers. Thanks.

Thankfully most of the pages for my many other sites and weblogs are intact. When I restore a page, I try to include a link to the Wayback Machine archive page, because the site also archived the comments.

Seriously, if you’re not donating to the Internet Archive, you should think about starting. It’s our history.

Google and the power we give in exchange for security

A couple of weeks ago,  I received an email from Google. It read:

Chrome will show security warnings on

To owner of,

Starting October 2017, Chrome (version 62) will show a “NOT SECURE” warning when users enter text in a form on an HTTP page, and for all HTTP pages in Incognito mode.

The following URLs on your site include text input fields (such as < input type=”text” > or < input type=”email” >) that will trigger the new Chrome warning. Review these examples to see where these warnings will appear, so that you can take action to help protect users’ data. This list is not exhaustive.

The new warning is part of a long term plan to mark all pages served over HTTP as “not secure”.

Here’s how to fix this problem:

Migrate to HTTPS
To prevent the “Not Secure” notification from appearing when Chrome users visit your site, only collect user input data on pages served using HTTPS.

Like many web sites, mine contain an input field that people can use to search through articles. It’s this search field that triggered the warning.

Continue reading “Google and the power we give in exchange for security”