You should now use the NHS App for viewing your medical records, viewing test results and documents, and requesting repeat prescriptions. Appointments can be booked using our website. We are no longer using the eMed app.

https://www.gpathand.nhs.uk/nhs-app-update/

https://terminaltrove.com/new.xml

There are smart valves. You can just unscrew/unclip the existing dumb ones and replace them with smart ones. They usually even report the temperature (well, near the radiator - so you might want to get extra temp sensors for the other end of the room).

On the receiving end of this controller, there’s probably just a relay shorting 2 wires from the boiler together - like the Honeywell BDR91.

So, you could just replace that by some Shelly switch and wouldn’t have to use the proprietary radio protocol.

On a sidenote: Those room controllers usually “learn” how long it takes to reach the target temperature (as this can be vastly different between summer and winter) and move the starting time accordingly. So they reach the target temperature at the programmed time. At least the more expensive ones do. You’d have to do something similar in your automation if you want that comfort. (Unless HA already has some code for that…)

While a non-profit sounds very honourable, I personally think Gitea has the more future-proof model. In fact, Gitea Actions was something they got commissioned for and were allowed to open source it as well.

This is basically how I think about it. (Not my comment.)

But we’ll see…

And Gitea has Gitea Actions. The big difference - and also the sole reason ForgeJo was forked - is that Gitea has a business behind it that allows them to sell support hours to other businesses. And then use the money to progress Gitea. Similar to how Zabbix and others do it. But the community decided that this is a bad thing and moved to ForgeJo.

how so?

I’d like to get educated as well, please. So far, ForgeJo doesn’t seem to have any specific advantage over Gitea. (And the name couldn’t be worse…)

If you spin up a Lemmy instance and subscribe to a community, all new posts and comments inside that community will be mirrored to your instance. As I’m subscribed to around 100 different communities, that was a LOT of traffic without me doing anything. That’s why I’ve given up on self-hosting Lemmy just for myself and went back to using lemmy.ml.

However, I do self-host a GoToSocial server just for myself. It’s probably not necessary as mastodon.social isn’t going anywhere anytime soon, but if you’re on a smaller instance, it might be worth it. Also, you get to show off your own domain name. And, while other instances may block yours, your content stays online as long as YOU want it to. There’s no way for an external moderator to delete posts on your own server.

People can find you via Boosts from others or by searching for your @username@domain.com.

Maintaining my GoToSocial so far consisted of simply getting WatchTower to update the Docker container. Migration of data to a new version happens automatically. (Well, there was one accident where some pre-release version got released under the latest tag and I had to use the development branch for a few days … but that was an accident from the GtS-team and shouldn’t happen again.)