My sense of time is so wonky I thought *today* was 2/22/22 (or 22/2/22). Then I realized it was tomorrow.
Or I guess I should say two-morrow?
Wait, it’s already tomorrow in UTC, isn’t it?
Archiving my Twitter, Facebook and other social network activity
My sense of time is so wonky I thought *today* was 2/22/22 (or 22/2/22). Then I realized it was tomorrow.
Or I guess I should say two-morrow?
Wait, it’s already tomorrow in UTC, isn’t it?
I really need to finish some projects before I start any new ones
Context: I was driving past a park that has a pond with a year-round population of ducks and geese and attracts other waterfowl. Usually near the pond.
This isn’t. It’s at the edge of the park. I pulled over because there was a whole…duckload of mallards just grazing their way down the street along the grass.
Me: Hmm, what’s a flock of ducks called?
Kid: A duckload.
(He looked it up. Apparently it’s a “paddling” of ducks, but I think I’m going to go with duckload.)
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…)
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
Hawthorn Flowers. In this area they start blooming in winter and keep going thrown spring.
Caution thrown to the wind.
I think I found that superb owl I keep hearing about.
Building a website with 11ty is like using Linux back in the 1990s: once you have it set up and tuned it runs great, but it takes a lot of tweaking to get to that point.
“You had to do what with the seat?”
https://fossbytes.com/what-if-operating-systems-were-airlines/
Yay for appliances built with standard parts!
Apparently Fedora has a Brainfuck interpreter in its repository.
Accidentally typed “bf” and it offered to install the package.
What is Brainfuck, you ask? “Code that was designed to hurt” is a good description. https://theoutline.com/post/825/brainfuck-coding-languages
The entire syntax is made up of +,-,<,>,[,],. and ,
Ah, this looks like the description I saw way back when
I really love how, judging by the fan noise, Windows alone keeps the processor as busy as Linux plus several CPU-based BOINC tasks.
Coffee maker started leaking a few days after we descaled it. Just a little at first, then more each day. kid opened it up. One of the water hoses has a crack in it surrounded by mineral deposits. As near as we can tell, the minerals were probably blocking the leak. 🤦♂️
No luck finding dedicated replacement parts, but we found a 5′ length of high-temperature silicone tubing in the right size. Here’s hoping it arrives soon. And works.
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/
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?
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.
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.
I’ve been experimenting a bit with #ClassicPress, also – it’s a hard fork of WordPress from version 4.9, just before they introduced the block editor, so there’s a lot less complexity. If I take the #WordPress approach, I may end up using ClassicPress for it instead.
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.