Oh good, Pixelfed.social is back!

Oh good, Pixelfed.social is back! And the post I made 5 minutes before it went down actually did go through!

I’m over on #pixelfed as @KelsonV@pixelfed.social where I mostly post suburban #nature photos these days, but occasional other stuff.

And I have an *ahem* @AddHawk account where I, well, add hawks.

On Wandering.shop

The downtime did get me thinking about picking up that minimalist #indieweb gallery project I’ve been thinking about since…um…January

On Wandering.shop

Subdomains vs Subdirectories & Indieweb Split

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.)

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 put my main blog in a subdomain, 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. But that’s a whole different conversation.

On Wandering.shop

Replying to their interest in how I’m sorting:

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 & nature photos over to kvibber.com but leave the funny & comic-con photos on hyperborea.org, or move my tech articles over but leave the personal posts.

I’m also planning to put together a light microblog, probably on kvibber, 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 & original/fan distinctions.

On Wandering.shop
Imported to K2R

As part of my exploration of #IndieWeb, web gardening, and #11ty, I’m collecting some of …

As part of my exploration of , web gardening, and , I’m collecting some of my reviews from old blog posts, amazon, etc. at https://hyperborea.org/reviews/ as a way to continue refining the minimalist layout for more use cases. I’m also starting to write new ones!

I’m cross-posting the book reviews to @bookwyrm as a more topical way to bring them into the Fediverse than just linking on Mastodon.

On Wandering.shop

Here goes: I’ve taken the troubleshooting posts that I already put on #gemini and set …

Here goes: I’ve taken the troubleshooting posts that I already put on and set up a web mini-site with them. I figure on adding more as I go along, redirecting some blog posts and linking others.

https://hyperborea.org/tech-tips/

Digging deeper into and /#11ty, trying to make it both light and responsive, and building a reusable template setup.

Once I’ve refined it a bit more I plan to generalize it & post a git repo of the structure & styles

https://hyperborea.org/tech-tips/about/

On Wandering.shop

More rethinking my website in the #IndieWeb context. The “garden and stream” metaphor…

More rethinking my website in the #IndieWeb context. The “garden and stream” metaphor brings up a good point: Not everything we put online is sequential.

I have a lot of stuff on my blog that doesn’t belong in the middle of a long stream of time-based posts as well as it would in a topic-based collection. Heck, I already reorganized the tech troubleshooting when I mirrored stuff to #gemini

https://indieweb.org/garden_and_stream

gemini://hyperborea.org/howto/

On Wandering.shop

But it’s also gotten me thinking: What kind of approach do I really want to take?

But it’s also gotten me thinking: What kind of approach do I really want to take?

I want a unified, self-hosted, #IndieWeb enabled gallery of the photos I’ve shared on social sites, yes, but are my Instagram / Pixelfed / Twitter / Mastodon photos *actually* that different from the ones I share on Flickr? There’s a lot of overlap.

Would it make more sense to just make one big #photogallery with everything?

On Wandering.shop

I guess the big questions are:
1. How differently do I use IG/Pixelfed/Mastodon/birdsite compared to Flickr (aside from volume)?
2. How differently are the sites structured, and how can I best combine those?
3. Do I want to?

On Flickr, each photo has a title, description and metadata, and you can build collections of as many as you want.

On IG etc, several photos might share a description and tags. And I think Pixelfed is the only one that has an album equivalent.

On Wandering.shop

Back in the day I used Instagram as sort of the rough draft for Flickr – I’d take a snap with the phone, and if I had a better camera with me I’d take a photo with that, and then when I got back to a desktop I’d take whichever came out better, adjust it as needed, and post that one to Flickr.

Then phone cameras got better.

On Wandering.shop

I still put a lot more on Flickr than other sites, but I suspect if I went back through my whole Pixelfed archive and my IG archive from the point when they allowed non-square aspect ratios to the point when I stopped using it, most of the shots on there are going to also be on Flickr.

On Wandering.shop

While messing around with IndieWeb, I’ve decided I want to build a consolidated PESOS gallery

While messing around with #IndieWeb, I’ve decided I want to build a consolidated #PESOS gallery of my photos at Instagram, Twitter, Mastodon, Pixelfed etc. I’ve got current archives for all (including from a dead Pixelfed instance).

Specs:
* Gallery, individual, and tag galleries
* Include captions and descriptions (I can add descriptions to the old photos)
* Links to wherever it’s posted (may be several sites)
* Light page code. I’d rather things load quickly than act fancy.
1/3

On Wandering.shop

I’ve made a prototype in #WordPress so far, and it looks nice, and I already know how to automate new posts using IFTTT. But it feels heavy. And of course it’s one more instance to increase my attack surface & maintenance.

I’m going to give #Eleventy a shot next. I’ve worked with it before, and I can optimize the templates however I want. The image plugin can generate different sizes, thumbnails, etc. The main drawback: I haven’t researched ways to automatically import to 11ty yet.
2/3

On Wandering.shop

Long-term I’d like to add #POSSE (selectively) to make it easier to cross-post. I had a set of 3 photos yesterday that I wanted to post to Flickr, Pixelfed, my blog, and my gemlog, and while it was mostly copying and pasting, it was also time-consuming.

Some of the stuff @stringerblog and @dansup have been talking about kind of overlap with this space.

Portfolio – an upcoming Pixelfed feature that allows users to create their own portfolio website that best represents them and their work…

3/4

On Wandering.shop

Oh yeah, Flickr…the way I use it is different enough that I don’t want include my zillions of photos in this project. I might try a more full-featured gallery like Piwigo at some point. It’s less linear and more collection-based. But for photos I’ve cross-posted, I would like to link to it same as I would to Pixelfed or wherever, and it would be nice to include it in the outgoing posts once I get that up and running.

And I do like the idea of just federating the photos out directly!

4/5

On Wandering.shop

OK, this got way more complicated and should’ve been a blog post.

So: building a personal #IndieWeb capable gallery of my sociallly-shared photos from various sources, keeping it light, pulling in new posts automatically (#PESOS) and eventually posting on my gallery and auto-posting it to Pixelfed/Twitter/Flickr/etc. (#POSSE) on a per-photo basis. Probably using #eleventy.

Anyone have any recommendations on tools that might be better than WP/11ty, or that would work well with this workflow?

On Wandering.shop

Ooh, I could also generate a Gemini gallery! I remember @FiXato came up with some ideas on how to format one. I’d probably want to break it into categories or do it by tag or something

On Wandering.shop

I wonder how much storage this will end up taking up. I probably won’t need to use S3 (finally started setting things up on DigitalOcean instead of AWS!) for this gallery unless I really want to CDN the images. By the time they’re scaled for whatever social network, it doesn’t take up any more space than by blog storage.

If I ever make my own Flickr mirror, though, that’s going to have to be a consideration!

On Wandering.shop

The article mixes up some of the terminology (IndieWeb is more specific than the way they use it here), but otherwise it’s a decent intro to decentralized social media and what makes it different from Facebook/Twitter/etc.

The article mixes up some of the terminology (IndieWeb is more specific than the way they use it here), but otherwise it’s a decent intro to decentralized social media and what makes it different from Facebook/Twitter/etc. https://www.newyorker.com/tech/annals-of-technology/can-indie-social-media-save-us

On Twitter

Manton Reece: Write locally, mirror globally

Are Facebook and Twitter a core part of the web…or are they just today’s portal into that core? The article argues that if you want your content to last, it’s better to post it on your own site, and mirror it on today’s social networks.

Manton Reece: Write locally, mirror globally

The Atlantic has an interesting essay on whether Twitter is on a slow decline, less useful and meaningful than it once was:…