With yesterday’s news that Google+ is shutting down next August, I found myself looking again at my exported archive from the network. This time I was less interested in the format (which has changed since January – you can export as JSON instead of HTML if you choose, and it includes media now), and more interested in what I had posted there over the years.

Early on I used Google+ a lot like Twitter: short statuses and link sharing, most of them short enough they could have been cross-posts.

After that early period I still mostly posted short items, but not as short. More like Facebook, really. I checked a few and found some tailored cross-posts, where I’d cram something into 140 characters for Twitter, then restore the missing words and abbreviations for Google+.

I tried using it as a blog. I did a few longer text posts and some photos, and a handful of galleries: A partial solar eclipse, Endeavour’s stop on the way to the museum. I contributed to a shared photo gallery from SDCC, and I’d share the occasional post from someone I followed.

Somewhere in there I’d figured out what felt like Google+ instead of what felt like Twitter or Facebook.

But most of my friends went back to Facebook, and the few people and sites I was still following on Google+ were also available elsewhere. So I stopped visiting, and I stopped posting.

From around 2015 on, it’s mostly auto-posts from my blog and the occasional picture that Google Photos’ auto-stylize feature actually made look interesting.

Ironically, I got my first +1 in ages on yesterday’s here’s-where-you-can-find-me post!

Update: Google has moved up the sunset from August to April 2019.

Printed sign: Please use the other Door (with arrow). Hand written on it: To the left - yes, that one (with another arrow)

They really want to make sure you know which door to use.

The funny thing is: I still reached for this one (even if momentarily) right after taking the photo!

(Every time I go back to this restaurant I remember that I still haven’t posted this photo, and by the time I have a chance to post it, I’ve forgotten again. Well, I finally remembered!)

Edit: I should mention that the door has been broken for several months. (I took the photo at the beginning of August.) I’m surprised they haven’t fixed it.

Update (Oct. 17): The door still isn’t fixed, but someone’s added another hand-written note to it since I was last there!

The air has finally cleared up enough to see Downtown Los Angeles and the mountains. After several weeks of smoggy days, wildfire smoke, and occasional gloom, it’s nice to be able to see something other than a gray blur in the distance!

Also interesting: seeing how much the view changes from late afternoon to really late afternoon. These shots were taken at 4:22 and 5:52pm on the same day. Unfortunately I seem to have held my camera at two different heights, so the foreground jumps around, but the skyline and mountains are in nearly the same spots, and you can see not just different colors, but different details as the shadows move.

I sent the following to the California Governor’s office, urging him to sign SB 822.

Dear Governor Brown,

I’m writing today to urge you to sign SB 822 into law and restore net neutrality protections within California. SB 822 goes further than the now-repealed FCC rules at protecting business competition, consumer choice, and freedom of communication over the internet.

As it stands today, we’re back to trusting the cable companies to have our best interests at heart. Competition won’t keep them in check. Many areas only have one or two ISPs to choose from.

Before the FCC stepped in, ISPs would do things like intercept and redirect search queries, block tethering apps, or block VOIP applications on their phone networks. Now that the FCC has stepped back, we’re already seeing cellular companies throttling service. In this era of increased consolidation, it’s not hard to imagine a cable company that’s part of a media conglomerate choose to prioritize data for their parent company’s streaming service over a competitor’s service. They could also legally slow down access to websites critical of the company, or sites that advocate political positions that the owners disagree with.

Net neutrality helps businesses. It helps start-ups. It helps consumers. It helps political activists. It helps *citizens*. And while the ISPs might tell you it will hurt them, they managed all right before the FCC repealed its rules. Abandoning net neutrality helps ONLY the cable and phone companies, at everyone else’s expense.

The effort to re-instate the FCC’s rules at the national level faces an uphill climb. If that effort fails, we can still preserve a free internet in California – and serve as an example to other states. If it succeeds, SB 822 will provide even more protection. With this in mind, I hope that you’ll sign SB 822 and restore net neutrality in California.

Thank you.

Back when I was comparing social media archives, I considered resurrecting my old LOLspam project as a Mastodon bot. I never quite got around to it, partly because I was able to do most of what I wanted to automate using IFTTT, so I stopped investigating that last 5%.

Last night, I threw together a quick and dirty bot to post a random item from a text file in about 20 minutes.

Then I spent three hours going through the Twitter archive for @LOL_Spam, pulling out jokes that are too dated or cringeworthy. (I hope I didn’t miss any. It was midnight by the time I finished, and I was really tired!)

This morning I modified the script to take a second file as a queue for new items.

  • I can add new items to the queue file as I find them.
  • It’ll post from the queue on a schedule (using cron).
  • When it uses up the queue, it returns to posting random posts from the archive.

If you’re interested in funny/odd spam subjects (and you’re OK with swearing and occasional lewdness), check out @LOLspam@BotsIn.Space. You can follow from any Mastodon or other Fediverse account.

The script itself is called fedbotrandom. I wrote it in Perl, using text files, so I could just put it in cron on any *nix box instead of worrying about language/database support or installing a runtime or DB engine. I’ve made it really simple on purpose, and while I do plan on writing some better error handling when I have time, it’s already more complex than I wanted it to be!

A few years back, we replaced our aging Windows PC with a newer system, figuring on using it mainly for office-type applications, casual games, and kids’ games. (Both of us had drifted out of playing the sort of game that really pushes a system’s specs, largely because there was a small person in the house who needed a lot of attention.) So we bought a Dell Inspiron, and it did its job for quite a while.

But eventually that small person discovered Minecraft. And Youtubers who play Minecraft. And the other games that those Youtubers play that need stronger hardware.

OK, it was old, it could use upgrading anyway. I didn’t want to flat-out replace the system, because it was still quite usable otherwise. And I hate moving data from one computer to another, because there’s always something that doesn’t transfer, and there’s always something that you forgot, and so on.

So we’ve been upgrading things bit by bit over the last few months. Continue reading