Tag: blogging

Posted on
by

In response to girrodocus’s question: #PersonalWebsite creators… what’s your rationale for deciding when to use a subdomain or a subdirectory?

I usually prefer to put sections in subdirectories. That makes it possible to make the entire site portable (depending on authoring tools, anyway). Ideally, I want something that could be zipped up and moved. Or sent to Archive Team. (One of the downsides of dynamic site generators is that you can’t do this.)

When I use subdomains, it’s typically because I want some sort of isolation between the content, or the server apps, etc. But in those cases I’m as likely to use another domain entirely.

I originally put my main blog in a subdirectory (/journal), but if I set up my own git repository or something like that, I’d probably put it in a subdomain.

That said, I’m currently trying to sort out what I want to keep at the domain I’ve had for the last 20 years and what to move to my IndieWeb identity site.

IndieWeb and Identity

It took 4 or 5 years from me discovering IndieWeb to actually building support into my website(s), because Hyperborea.org, named after a fictional place, felt like a digital home, but not an identity. So I set up KVibber.com as my digital identity instead.

I’ve been considering several approaches:

  • New stuff on KVibber, leave old stuff where it is.
  • Professional stuff on KVibber, fun stuff on Hyperborea.
  • Original work on KVibber, fandom stuff on Hyperborea.

I might move my scenic and nature photos over to KVibber but leave the funny and comic-con photos on Hyperborea, or move my tech articles over but leave the personal posts.

I’m also planning to put together a light microblog to be the canonical location for short posts on Mastodon/Twitter/etc that I want to keep, but don’t feel big enough for a full blog entry. That’ll probably go on KVibber, even though it’ll blur the pro/fun and original/fan distinctions.

Originally on Wandering.shop.

Update September 2022: I’ve tabled the whole question at this point. For now, I’m just using KVibber as a profile page and putting everything else on Hyperborea, like I was doing before.

Update April 2026: I’ve been moving stuff over to KVibber, and put the blog on a subdomain because subfolders have .well_known problems.

Posted on
by

I’m not ready to give up on the flexibility of WordPress for my main blog yet, but holy crap are these pages heavy. Even with compression. There’s no reason it should take 450K (before compression) and 20 requests to display a 500-word post.

And I don’t even do ads, popups, social sharing buttons or anything else like that.

By contrast, my Les Mis blog, where I post about once a year, is currently generated by Eleventy using a custom minimal theme that only takes around 10K of HTML, 3K CSS, and a third request for the icon. And another 40K for the header font, which I recently set up locally so it no longer has to call out to Google Fonts.

One domain, just four requests, and only 50K for the first hit and 10K for each subsequent page.

Never mind the Gemini version of the blog which is around 2-5K per page and a single request per page!

Compression cuts down on those 500Kb WordPress pages — all the text and code compresses really well so only around 200K bandwidth is needed. But it’s still got multiple JavaScript and CSS requests going on.

I was able to cut it down significantly by switching to a lighter theme and turning on the minimize/combine feature in WP-Optimize so it’s making fewer script calls. But it’s still way bigger than the minimalist setup I have with 11ty.

Some of it is images, though. I still have my latest Flickr posts in the sidebar, and I’m using Jetpack’s related posts feature which includes thumbnails. I could cut out a big chunk by removing those, but I kind of still like the idea of having them in there.

I think I need to take a look at how much extra stuff I really want on this site and rip some of it out. Eventually I’d like to replace all the JetPack features because they just seem to keep adding more scripts. Plus I want an entirely local stats package instead of one that’s offloaded to a third party even if they’re less awful than, say, Google or Facebook.

On the other hand, I want to keep Gravatar on the comments sections (on the older posts where people actually commented) because that’s actually useful to readers as an aid for following a conversation better. But that’s all on top of the base page size.

Posted on
by

Sometimes you choose which social app to open based on

  • who you want to talk to
  • who you want to hear
  • what you want to talk about

Sometimes you’re just shouting into the void. At those times, I figure I’ll choose the void that feels less exploitative.

That’s part of why I still have a blog. And why I post more on Mastodon, while Twitter is mostly auto-shares from my other networks, retweets, and occasional cross-posts.

(And politics, because I’d rather keep that on Twitter, where it’s sort of the main topic anyway, than on the network that’s still fun. Not that Mastodon is apolitical. Far from it! But it’s a lot more varied than the overwhelming focus on US partisan politics I see on Twitter. And the culture and structure make the discussions at least somewhat less train-wrecky. Most of the time.)

Update: If you’re interested in checking out Mastodon and the Fediverse, good places to start are JoinMastodon.org and JoinFediverse.wiki.

Posted on
by

What’s the minimum viable blog feature set these days?

  • Rich text posts (output; the source can be anything)
  • Titles
  • Permalinks
  • Tags/categories
  • Navigation
  • RSS feed
  • Images hosted locally
  • Media embed (remote or local?)
  • Author info for multi-author blogs

I won’t back down on RSS/Atom, because there’s SO MUCH you and subscribers can do with it.

I also think images should to be built-in and not something you bolt on clumsily afterward.

Not sure if I’d consider comments part of the base level.

What else am I missing?

Candidate Software

Looking for something lighter weight than WordPress.

The last time I tried Plume and WriteFreely, they didn’t support images, though IIRC you could embed remote images in at least one.

Static site generators I’ve tried like Jekyll require you to bolt on separate commenting systems like Disqus, or jump through hoops to roll your own in a way that will re-generate the site when someone comments…and you still have to reinvent spam filtering.

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.

»All pages site-wide with this tag