Rather than the Streisand effect which is about attempts to censor information, its probably more accurately described by a term I recently learned about (coined by Lee Vinsel and popularised by Cory Doctorow in his various writings): 'Criti-hype'.

Doctorow uses it to describe how a lot of online AI criticism is actually feeding the so-called "growth story" that makes AI look attractive to investors (i.e., by tacitly accepting the narrative that AI is actually good enough to 'take our jobs', for example) which leads to greater and greater stock valuations of AI companies, and therefore continued AI bubble inflation.

I see the parallels here, not sure if it's 100% applicable, but thought I'd throw it out there

This would probably get crazy popular if there was a supported integration for Stash

My pleasure! Good luck with development, seems like a cool project.

It's just a flexibility thing, not a cis women thing. A lot of having a more pronounced arch in this position will come down to thoracic extension mobility more than anything else. Depending on the shape of your hips you might find it easier to arch with your knees closer or further apart. Yoga will def help. Most of the way you can train thoracic extension is actually through rotation rather than trying to extend like this, because of the way the spine is shaped basically.

As a non-US resident that doesn't much read the news, is there any particular reason for the comparison of 'now' vs '6 months ago'? Has there been a particular change in policy or some other big event in the US that's motivated the sudden change in attitude?

A lot of the non-article content on the site read a lot more corporate/generic/AI-vibes than I think you'd like given what you wrote in your AI-usage disclosure article. You might want to go through the non-article copy and see if it can be edited more heavily to actually make it sound like your voice saying it.

Some examples include:
"No accounts. No “Premium” tiers. No metadata harvesting." on your wallpapers page
"Whether you’re a Linux veteran or just looking for an alternative to the Windows/Google ecosystem, I aim to provide direct, no-fluff content based on real-world testing." in the about me section

They stick out really hard when contrasted against your articles, because you can see that your articles actually have your own voice in them. I know you've got the line "I'm a sysadmin not a copywriter" in a few places, but really, if you have a blog, you'll be alienating your readers by not atleast trying to be both.

Also your 'tools' page is probably the coolest part of your site so I think it really deserves a section pointing to it on the homepage, since most people don't go straight for the nav menu.

To end on a sweeter note, I really like the visual styling you did for the archive it's really cute and it pleasantly surprised me.

Maybe you'll find dockcheck is a more mature and rounded version of what you wanted, and you can fork it to tinker with the other features you want for your own personal use if it doesn't do everything you wanted! Or maybe you'll find you like yours better anyway. Hope you find something interesting in it, regardless!

I personally find dockcheck on each host + a simple systemd service is more or less perfect for my needs. I hook it up to a grafana dashboard so it can give me a running tally of what's out of date and what's not alongside the rest of my monitoring stack.

On face value it doesn't look too different to dockcheck. What you've described (CLI, read-only, no auto updates, sends notifications via channel of your choosing) sounds exactly like how my dockcheck is set up. Were you aware of dockcheck and if so, how would you say your project differs?

nice one, always good to have a little reminder to update my outdated services pop up in my feed lol. Had a little peruse through the rest of your website after reading, did a little snoop on the services you're hosting on your homelab atm hehe. Would you be open to a little feedback on the site from a random stranger's perspective?

So the docker container image-watcher and update-coordinator seems quite incongruous with the rest of the tool. It looks like a "network visibility tool" with the container manager just tacked on as scope creep.

I presume if the container is actioning the updates for you, it also requires docker socket privileges? I imagine that will give a number of people pause about installing it on their homelabs, as "cool looking vibe-coded personal project with docker socket privileges" is a ticking time bomb from a cybersecurity perspective.

If it does require docker socket (and Can't imagine how the container management would work if it doesn't) you night have more success getting uptake in users for feedback on the main features if you remove the tacked on container manager and just keep that part for your own personal implementation of the application.