Tag: blogging

Posted on
by

In advance of Google shuttering their third(?) attempt at a social network, Google+, I’ve retrieved a full archive, and I’ve trawled through it looking for anything that I want to keep online after the shutdown. Most of them were cross-posts of one sort or another, or (early on, especially) the kind of random social media status that maybe has value in the moment, but not down the line. I found around 30-40 posts worth keeping. Some had their own merits, some fit in with other posts here on the blog.

Rather than just import them verbatim, I’ve decided to do some minimal cleanup. No major rewriting or anything, just the kind of things that I’d be willing to silently change on an old blog post that was already here:

  • Fix up the formatting
  • Fix typos
  • Link to related posts
  • Add a quote to linkblogging posts if they need more context

Yeah, it’s slower than copy-paste or direct import (I never did get around to writing the converter I wanted to), but there’s no rush for old news, and I’ve got copies to work from even if I’m not done by April 2.

Posted on
by

Last month, Tumblr and Flickr both announced policy changes that will impact a lot of users, and upset even more. Flickr announced that they’d be shrinking the storage offered to free accounts while adding features to paid accounts. Tumblr announced that all adult content was going to be banned, and immediately set about flagging posts and accounts. In the clumsiest way possible. With a lot of errors.

I feel like Tumblr has been knocked out of orbit, and it’s only a matter of time before it goes the way of GeoCities (or at least LiveJournal). But I actually feel more confident about Flickr. Why?

  • Flickr was bought by SmugMug, a company that’s all about photos. Tumblr was part of the Yahoo! package bought by Verizon, a giant telecom conglomerate that’s searching for a way to monetize users’s content.
  • Flickr has had a freemium business model as long as I can remember.
  • The new free tier at Flickr may be limited, but it’s still big (1000 photos), and it’s still more than they offered before the move to “Let’s get people to host ALL their pictures here!” a few years back (200 photos, IIRC).
  • And that limit is both clear and non-judgmental, not a fuzzy, badly-implemented line that on other social media sites has frequently turned out to be the first step down a slippery slope (like the “Strikethrough” episode at LiveJournal that ultimately led to a lot of fanfic writers and fan artists leaving LJ in favor of, well, Tumblr.)
  • Flickr’s customers are the paying Flickr Pro users. Tumblr’s customers are the advertisers.

In short: Flickr is focusing on their core. Tumblr just jettisoned a huge segment of their users and gave the rest a big red warning flag.

I’ve been a paying Flickr customer for years now, and I’m happy to renew. I still post galleries there, and and my better one-off photos.

Tumblr…I don’t have anything that violates the new rules, but it seems like they’ve taken a step towards self-destruction. Between this, Google+ closing, and the ongoing train wrecks of Twitter & Facebook, I’ve decided to pull back. I’ve downloaded an archive of my entire blog, and I’m in the process of clearing out all my share-posts, reblogs, mirrored posts, basically anything that’s not either original to that blog or an actual conversation. And I’m starting to import the original content here, where it’s under my own control.

It’s clear that Verizon has even less idea what to do with Tumblr than Yahoo! did. When they finally give up trying to monetize what’s left of the user base, they’ll have no incentive to keep it going. Or to respect all the user data they’ve amassed.

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

For today’s daily blog, I was thinking about posting something about getting out there and voting in the midterm election tomorrow. Aside from the fact that I already posted about elections a few days ago, I realized another problem: who’s going to read it?

I mean, K-Squared Ramblings doesn’t seem to have many regular readers as near as I can tell. And Key Smash! is for testing – I’m not really expecting to pick up many regular readers there. So a call to action isn’t going to reach many people on either of these blogs.

Of course, that brings up the question of why am I blogging these days? Who is my target audience?

  • How-to and troubleshooting posts are intended for other people with similar problems. They don’t have to be blog entries, it’s just easier to write and edit that way.
  • Recurring themes (like funny signs, or solar halos) are intended for anyone who lands on a related article or photo. It’s easier to tie things together on one site than across several.
  • Some of it is soapbox material that I just feel like I need to get it out there. The kind of stuff you shout into the void on Twitter or Mastodon, but maybe it was too long for that, or maybe I did post it on one of those sites and decided that it was worth hanging onto. (Aside from lack of control and limited search functionality, sometimes social networks shut down.)
  • Some of it is stuff that I find interesting and want to share. I usually end up sharing links over social media, and then if I have more that I want to say I’ll do it on a blog, because it’s much better-suited for that. I don’t have anyone specific in mind, just whoever might find the same stuff interesting.
  • And some of it is for me. I don’t think many people read my convention reports (these days people just go for the photos), but I’ll go back myself and check, “Which year was that, again? Was that WonderCon or SDCC?”

Posted on
by

I don’t have the time or ideas for Nanowrimo this year. It’s actually been a decade since I last did it, now that I think about it. But I’ve done NaBloPoMo a few times, and I think I can manage a month of posting one blog entry a day.

Plus it’ll be a good way to test Pterotype federation and other stuff.

I’ve already posted two days in a row at my main blog K-Squared Ramblings. Yesterday I posted a couple of Halloween photos, and today I posted about a hosting problem that took out this blog for a few days.

I do feel like I should try to put some effort in rather than just taking a tweet/toot and calling it a blog entry. But what makes something suitable for blogging vs a social media post?

  • Long-form writing that doesn’t fit in a short note.
  • Image(s) with long descriptions or extended commentary.
  • I think I can probably take something that fits a series and justify it as a blog entry even if it’s short or just a photo with a caption.

So between Key Smash! and K2R, I’ll try to post at least once a day this month. If there are days I end up only posting here, I’ll probably move the posts over when I’m done.

And somewhere along the line I’ll turn on Pterotype on K2R!

Update: I tried for a couple of days but dropped out. Though I did manage to make 19 posts across 15 days of the month between the two blogs – probably more, since I didn’t import all of the Key Smash! posts before taking it offline.

Posted on
by

Twitter is suited for short statements and back-and-forth conversation.

It’s terrible for anything long-form.

Long Twitter threads* and images filled with text remind me of the old tech support days when users would paste screen shots of error messages into Microsoft Word documents and email me the document. It was a terrible tool for the job, but it was the one they knew.

Once you get past two or three tweets (doesn’t matter whether they’re 140 characters or 280, it’s the structure that matters), your ideas will hang together better and be better understood if you write an actual article somewhere. Sadly, Twitter has trained people to stay in Twitter instead of going outside to read the %#$ article**, because you won’t be able to get back to where you were in your timeline, and besides, that’s just too long to read right now.

And that would require you to have, like a blog or something, and what sort of weirdo has one of those? 🙄

So people use what they know, and we get screenshots of long paragraphs that are awful for accessibility. And we get 40-tweet threads that people only see fragments of and take bits out of context. And they’ll reply to tweet #5 complaining about something that’s addressed in tweet #12, but they didn’t see it, because that was hidden behind the “read more” link, and how long does this thread go, anyway? (Scroll bars solved this problem decades ago.) And we get links to articles that people don’t read, but they reply to them anyway — or rather they reply to what they assume was in them.

Which I suppose is what we had in the old days, I mean “nobody reads the articles” was a joke on Slashdot 20 years ago. But it’s still frustrating.

Update: I realized I don’t see this so much on Mastodon. I wonder if that’s one of the ways the culture is different, or if I just happen to not be following anyone who writes/boosts long threads on a regular basis, or if 500-character posts give people enough room to breathe that they don’t feel like they’re already writing a long chain, so why worry about keeping the number of posts down, what’s the difference between 10 tweets and 15?

Update March 2024: Apparently it was a posting culture thing, because it’s common on the Fediverse now too. At least on platforms like Mastodon that maintain a smallish size limit.

*To clarify, I’m talking about long threads that are effectively one piece of writing, not a series of “oh, and another thing” follow-ups, live-tweeting as things come up, actual conversations, etc.

**This part is true of Facebook as well.

Posted on
by

Most social networks don’t give you the ability to backdate your posts. That’s good, because it provides a trail that you can point to, saying “Yes, I did in fact post this before it became common knowledge/was plagiarized/etc.” But other publishing platforms do. It’s helpful for things like transferring an archive from another site — though it seems a little weird (and vaguely dishonest) to backdate a new post.

That said, I do backdate posts on this blog from time to time, generally when:

  • The post is imported from another site (Instagram, LiveJournal, a comment somewhere, a Twitter thread, etc.), and I keep the original posting date. Basically it’s a smaller scale version of transferring an archive. Sometimes I’ll make a note, sometimes I won’t. But the post was already online somewhere on that date, even if it wasn’t here.
  • I’m splitting an old post into two or more smaller posts, in which case I’ll usually keep the date but adjust one of the times.
  • I’ve got an old draft that I never got around to posting, it’s no longer relevant today, but I’d like to make it available in its original context. In that case I’ll add a note that it was backdated.

There’s also the accidental backdating that sometimes happens when I create a draft in the mobile app and it decides to keep the upload date as the posting date. I try to fix these as soon as I notice. But that’s not really the same thing!

»All pages site-wide with this tag