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.

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

Kiddo’s been wanting to learn programming, with the ultimate goal of modding Minecraft. We’ve done some Ruby, but he’s impatient, so last night I we started Java with a simple program that repeats a println X times.

He wanted to pass it the integer limit.

After a few minutes, I suggested we watch a movie and check back later.

After dinner, he decided to stop it and we timed some shorter runs.

I think he has a better understanding of scale now!

I have mixed feelings on Facebook closing down automated posts to personal* profiles. It might cut down on spam, and it will lead to better descriptions on link posts, but it also locks you further into their silo.

You can still write elsewhere and link back to it on Facebook, but you can’t use WordPress Publicize or IFTTT to post it, or Buffer to schedule it. You have to do it manually, which adds more friction, and you can’t time-shift it. I used to spread out look-at-this-cool-link posts using Buffer, and queue them up from Pocket while offline, but I can’t do that anymore.

If you want your Facebook audience to see your words or photos, it nudges you to maybe just post on Facebook to begin with (never mind that you want its main home to be somewhere you have more control). And it’s another way for them to get you back onto the site so they can try to keep you there for another 15 minutes, see some more ads, and generate more value content for Facebook.

Then again, I can’t help looking at it in terms of the debate over cross-posting from Twitter to Mastodon. There’s an argument that if you’re not actually on the platform, you’re not contributing to it. And while that debate tends to focus on auto-posts from a specific mismatched (and hostile) community, I think it’s fair to consider the broader context that if you’re not at least following up, you’re not really participating. (I’m especially guilty of that with my cross-posts to Tumblr.)

Though I suppose it matters more to a smaller community like the Fediverse than to something as massive as Facebook.

*Pages and groups can still accept automatic posts through the API, but those supposedly represent a business, or an organization, or a public persona rather than a “real” person.

Expanded from a Mastodon post on Wandering.Shop.