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

IFTTT Pro

I don’t mind that IFTTT is introducing a Pro subscription for additional capabilities, and if there was something I wanted to do with those features, I’d go for it. But what I use it for isn’t worth $10/month.

I don’t mind paying for stuff… But price points matter, and IFTTT is following the typical (and annoying) pattern for formerly-free services where they squash the free tier down hard and aim the lowest paid tier at people who are going to use a lot more of it than I am.

I also like the idea of boosting a blog post and having replies federate as …

I also like the idea of boosting a blog post and having replies federate as comments.

We’ve all been trained by FB to discuss on the network instead of at the source. That fragments the conversation, and while sometimes that’s a good thing, sometimes it helps to, well, centralize.

Everyone who’s asked me for help using IFTTT with Mastodon has asked *here*, not on the blog post, so they haven’t seen other people who had the same problem & how they fixed it.

https://hyperborea.org/journal/2017/12/mastodon-ifttt/

On Wandering.shop

The biggest roadblock to adoption and the key feature

I’m kind of reminded of XKCD’s initial response to Google+

Ultimately, though, I think the separate instances are going to be both the biggest roadblock to adoption and the key feature that distinguishes Mastodon from Twitter.

On Mastodon.Social

Wait, is there a taboo against naming that other microblogging site? that other microblogging site. Should I call it “You-know-where” or “That which must not be named?”

(I will admit I was amused to see someone refer to it as “The Bad Place” yesterday.)

Conversation On Mastodon

…and I just noticed the editing error in this toot. :facepalm:

On Mastodon.Social

I do wonder about permanence, though: How often do Mastodon instances shut down? How much notice?

Data Export seems to only cover follow/block/mute lists so far. I suppose I could hook up my atom feed to IFTTT or something.

Or I can just do what I do with “the bird site,” and if I really want to make sure I keep something I’ve written, copy it over to my blog.

On Mastodon.Social