Category: Computers/Internet

Posted on
by

Phone notifications aren’t just reminders. They’re interruptions, especially if you have sound or vibration turned on. That gives them a lot of power, and means they should be used responsibly.

In short, phone notifications should serve your interests as the person using the phone. Not the app’s. Not the service’s. Yours.

If someone you know sends you a message, you probably want to know that. If you put an appointment on your calendar, that reminder is going to help you. A shipping update, or delivery notice? Probably helpful as well. Completion of some long-running process that you requested or are waiting for? OK. App and system updates? You do want the phone to keep working properly, so there’s a case there.

If your friend tags you on a photo, or replies to your comment, or sends you a message, then yeah, Facebook or Twitter or Tumblr or Mastodon can justifiably notify you. It’s the start or continuation of a conversation between you and that other person. (Though you should still be able to mute it if you don’t want to talk to that person.)

But when Facebook starts pushing friend suggestions, or “did you see so-and-so’s comment on this conversation that you’re not part of,” or choosing to promote some subset of people’s broadcasts? That’s not in my interests, and that’s not in the other person’s interests. That’s Facebook advertising itself, because they’re desperately afraid they’ve lost my eyeballs.

It’s no different than the Black Friday through Cyber Monday ads that Amazon pushed into my notifications over Thanksgiving weekend.

We can pare down notifications, but it takes time, and not every app offers fine enough controls over which notifications it sends. And of course you have to re-do it every time you get a new phone, and every time you add a new app.

Advertising in an alert is, IMO, an abuse of the feature. We’re bombarded by so many demands for our attention as it is. Phone notifications should stick to those that help us do what we want, not those that distract us from it.

Posted on
by

Working through a book on modding Minecraft with the kiddo. It knows its target audience: the first few lessons are all about explosions!

It’s written for 1.8, which is a problem because a lot of the structure has changed between then and 1.12, but a decent IDE with auto complete and a sense of common naming schemes has made it relatively easy to adapt the simple lessons so far. We’ll see how well that works as they get more complicated.

Posted on
by

Now that Pixelfed federation and Pterotype are taking shape, I can hook up my photos and blogging directly into Mastodon and the Fediverse, but you know what would be even cooler?

Connecting them to each other.

A lot of my blog ideas grow out of photos or statuses that I’ve posted previously, as I find more to say or a better way to say it. And while it’s always possible to just post a comment or reply with a link, imagine posting them into the same federated thread.

Here’s a scenario we can do today:

  1. Photo of something interesting on Pixelfed, boosted to Mastodon. I believe we’re one update away from Mastodon replies and Pixelfed comments appearing together.
  2. Blog post on Plume or WordPress with Pterotype going into more detail about the photo. Comments and Mastodon/Pleroma replies can interleave right now. (Try it, if you want!)
  3. Another photo on Pixelfed as a follow-up. Again, comments and replies can interleave.

This is already pretty cool, but it still creates three separate discussions. The best I can do is add a “Hey, I wrote more on my blog over here: <link>” to the first discussion.

What if there were a way to publish the blog entry as a reply to the PixelFed photo? Or to publish the second photo as a reply to the blog?

And that opens up other possibilities where people can reply to other people’s photos and blog entries with their own. (Webmentions sort of do this, but they’re not going to create a single federated discussion.)

I’m not sure what form this interleaved discussion would take, or what the pitfalls might be. (Visibility might suffer, for instance.) Blogging and photo posting tend to be platforms for an original post that can have comments, rather than platforms where a top-level post can be an OP or a reply, and this would change that model.

Posted on
by

While looking up importers that I could use to move various third-party archives into something self-hosted, I found an add-on to pull Facebook posts into Keyring Social Importers, an extensible WordPress plugin. At the top of the list of built-in services: Delicious.

“Hey, I used to have a ton of stuff on Del.icio.us! I don’t know what percent of the links still work, but I should at least export it!”

delicious.com is gone, but I remembered they moved back to del.icio.us at some point, so I went there, and found…

The delicious site is temporarily offline while we move servers. We'll be back! Your bookmarks are safe and sound. The site should be available again on Monday, July 24.

Yeah, so I guess that’s not gonna happen. It turns out I exported my bookmarks in 2016 (into one big HTML file), which is probably as current as it needs to be.

The maintenance page mentioned Pinboard, so I looked up some articles. Apparently Pinboard bought Delicious in June 2017 and put it into read-only mode. I know I was able to look up bookmarks on Del.icio.us as recently as January, so it’s at least this July they’re talking about, but I’m guessing the server migration probably failed and it never came back.

The Fanfic Connection

In an interesting twist, I discovered that there’s a fanfic-related history in the past rivalry between Del.icio.us and Pinboard.

TL;DR: Delicious was once extensively used to categorize fic on LiveJournal, but an overhaul left it unsuitable. (Among other things, “/” became an unsearchable character, making it impossible to search for pairings.) There was a mass exodus of fanfic writers and readers, many of whom ended up at Pinboard…and Pinboard’s owner put in extra effort to address their needs.

Posted on
by

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.