Tag: IndieWeb

blathering about combining metadata formats on a web page

This article on the minimal markup needed for link previews has got me thinking about consolidating metadata again.

I could go pure #IndieWeb and throw out everything that isn’t visible on the page and marked up with microformats2, but I there’s a lot of stuff out there that doesn’t read microformats2.

I’ve already consolidated most of the <meta> tag-based labels like OpenGraph and older HTML conventions. What I may get rid of:

  • OpenGraph category/tag/etc. details, unless something out there actually uses it.
  • The redundant chunk of JSON-LD for Schema.org

I assume anything that uses Schema.org will fall back to OpenGraph or plain HTML for anything they have in common, but I don’t know whether they’ll still fall back if I keep a JSON-LD chunk with the Schema-specific fields like more detailed article types, what media/event/place is being reviewed, etc.

I wonder if I can add them as microdata where I already have the microformats2 info….

Question for #indieweb folks: I remember a discussion about a syndication model that describes one …

Question for #indieweb folks: I remember a discussion about a syndication model that describes one of the ways I handle social media and my own site. It's sort of a selective/curated #pesos.

I don't import *all* my posts, just the ones I feel worth preserving, and those often as first drafts. I'll expand, rework, or otherwise finalize the posts on my website.

I could swear I saw someone come up with a term for this model, but I can't remember what it was!

On Wandering.shop

Geocities

Found something I wrote in 2009, when Yahoo shut down Geocities:

“It’s funny: the things we expect to disappear from the web often don’t, but the things we expect to be permanent often do drop out of existence. GeoCities appeared 14 years ago. Will today’s blogs, Facebook pages, forums, and wikis still be around 14 years from now?”

GeoCities, RIP: Fandom’s Lost Pages

The blog I posted it on is still there. A lot of sites it linked to aren’t.

#permanence #SelfHosting #linkrot #Geocities #Indieweb

On Wandering.shop

Thinking about this post on “permanence” with #SocialMedia / #IndieWeb / #SelfHosting (for things that …

Thinking about this post on “permanence” with #SocialMedia / #IndieWeb / #SelfHosting (for things that you *want* to keep permanent, anyway), balancing questions like are you going to outlive Facebook or the other way around, etc.

I still think an “export to static site” option should be standard on any CMS as an exit strategy (on top of actual data portability) for cases where you no longer have the resources, time, inclination, etc. to maintain it.

On Wandering.shop

I’ve been slowly redoing parts of my personal website

I’ve been slowly redoing parts of my personal website over the last year or so, continually pulled between two extremes.

1. I want to make everything federate with everything else so it’s as interoperable as possible, from #ActivityPub to #IndieWeb!

2. I want something that doesn’t add any attack surface on top of the webserver, that loads and renders super-fast, and that can be zipped up and tossed on an S3-compatible bucket in the event of financial trouble or untimely demise.

On Wandering.shop

ugh… I’d noticed the change in behavior for following links to posts and profiles …

ugh… I’d noticed the change in behavior for following links to posts and profiles *within* the web app on #Mastdodon 4, but I hadn’t looked to see that the *actual* post and profile web pages do not actually contain the post or profile content, just JavaScript and the metadata to load it.

In essense, Mastodon profiles and posts are no longer actually interoperable parts of the web. Or as #indieweb puts it: #jsdr

On Wandering.shop

IMO the web has plenty of room for both applications and documents. Applications can be applications, and they can certainly include documents. I’m not objecting to the overall web application UI.

But a document should be reachable *as a document*.

On Wandering.shop

Aha, there is a Github issue:

https://github.com/mastodon/mastodon/issues/19953

On Wandering.shop

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

As part of my exploration of #IndieWeb, web gardening, and #11ty, 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 #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.

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

Digging deeper into #IndieWeb and #Eleventy/#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