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).
* 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.
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.
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 @email@example.com and @dansup have been talking about kind of overlap with this space.
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!
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?
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
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!
Well, I haven't gotten around to doing much with the #11ty based #photogallery approach yet. Just enough to realize the template I started with isn't the way I want to go. It puts the image list and metadata in one giant JSON file, and I'd rather use individual markdown files with front matter and the caption/comment/description as the body.
I've found a couple of articles that are closer to what I want to do with it, so I may end up basing it on one of those or rolling my own entirely.
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.
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.
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
Here goes: I've taken the troubleshooting posts that I already put on #gemini 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.
Once I've refined it a bit more I plan to generalize it & post a git repo of the structure & styles
Most of what's left is refinements, but I still haven't decided how to handle comments. I've got a simple structure for *displaying* comments, but no way to accept new ones yet.
Static site generators inherently can't process input. If you want comments, you have to hook something else up, or offload them entirely.
The original posts didn't get many comments, so I might just leave it at the mailto link for now. (Talk about flashbacks...)
@DawnPaladin Yeah, I'd looked at Staticman, but I'm not sold on using the GitHub flow. Though as you say, maybe I could adapt it.
@DawnPaladin Oh, there's a possibility: I hadn't noticed that StaticMan can use other git forges too!
The Wandering Shop is a Mastodon instance initially geared for the science fiction and fantasy community but open to anyone. We want our 'local' timeline to have the feel of a coffee shop at a good convention: tables full of friendly conversation on a wide variety of topics. We welcome everyone who wants to participate, so long as you're willing to abide by our code of conduct.