This website is like 10 years old from memory, well before grid-scale batteries were widespread (well they still aren’t in many countries).

You can always self host forgejo, but yeah, codeberg is an opinionated place, I suspect primarily due to resource constraints. Not a github replacement and not really trying to be.

I integrate Miniflux with readeck, which is then combined with a readeck plugin for koreader, allowing me to easily read articles on my ereader, without relying on a paid service.

I’m also one of those people that still uses custom ROMs on Android, and since the backup and restore situation is still kind of dire if you don’t use Google (and sometimes even with) it’s easier to have most of my configuration and state stored on a server, and so I can wipe a phone with relatively little risk.

You could use tailscale or netbird. Alternatively, you can use a dynamic DNS provider which usually provide free subdomains, if you don’t want to pay for a domain. And even with all of that, Jellyfin doesn’t require HTTPS, although there may be clients that do (make sure you’re behind a VPN in this case).

I had a quick look and the AI features that are added:

• LLM driven tagging suggestions
• Remote OCR (Azure AI)

They do look to be optional at least. I’d probably be a bit more concerned if the code was largely written with LLMs, given the large number of commits in what looks to be only a few months.

Effective as of the end of this sentence. This sentence I’m speaking right now. Period.

They mean on the client side most likely. A reverse proxy will be transparent to the user.

Almost as annoying is if they give you a single /64. Here’s an absurd amount of IPs but you only get one subnet. Thankfully, I’ve had nothing smaller than a /56.

Not the OP but:

• FreshRSS interface is kind of ugly (probably can be tweaked). You can use third party RSS readers, but that ends up being almost as much work as installing readeck and the like.

• FreshRSS doesn’t support OPDS or have any koreader integration, unlike readeck. These are essential features for reading on an e-ink reader, which is my preferred way to read longer articles in particular.

I think country TLDs don’t have WHOIS privacy protection if you care about that.

The risks of auto-updating now include “devs losing their shit” which has become increasingly common.

I like that matter provisioning requires verification of their certificate, but I don’t like that certificates can expire or the certificate authority can shut down. Although maybe that’s all taken care of by the DCL? In which case that’d be fine.

It’s also pretty obnoxious that it requires an Android phone with Google play services enabled (and even a Google login IIRC) or an iOS phone. There are ways around this, but they are pretty complex and not well documented.

If any ai Ia involved they will dismiss not only it but you and it’s a really irritating habit that is starting to emerge.

It’s perfectly understandable. It used to be that a project that had the appearance of a significant amount of work and polish put into it could be reasonably trusted. With the rise of LLMs, that assumption has gone completely out the window as people can churn out appealing looking slop in record time. In addition, LLMs are dominated by the most transparently evil tech companies in existence, and the fully open models aren’t yet good enough, and are still built on the backs of the absurd amount of energy usage used to train the models.

That all being said, I don’t think the OP is being malicious and I appreciate the disclosure but I’d give this project a year of maintenance before I would reasonably trust it.

I’ll add that often random appliances and the like are using Tuya firmware so people might not be going out of their way to buy explicitly Tuya devices but still want to use them with HA. Some of them can be flashed with ESPHome but it’s more likely to require soldering these days.

The main benefit of Matter is that it is split into two layers (Matter and Thread) where as Zigbee is essentially one layer that handles everything. This makes Matter more flexible, since it can work over both Wifi and Thread (and any future protocol at the same layer). At the moment there isn’t a huge advantage, but in the future if the standard succeeds, you would hopefully be able to buy most smart devices and use just one protocol (Matter) to control and integrate them.

At the moment, the main advantage I can see is that more wifi smart devices can be locally controlled because they have Matter support (which requires it). Which historically, was limited to HomeKit over WiFi, ESPHome/Tasmota flashed devices, and sometimes through Home Assistant integrations that found a way to locally control devices for a given company.

Because I didn’t really explain Thread, I’ll just quickly say that it’s a protocol much like WiFi and the “closer to the hardware” part of ZigBee. I’d prefer buying Matter over Thread vs Matter over WiFi devices, particularly if you’re planning to build out a Thread mesh network (the Matter over wifi devices won’t help in that).

I’m going to echo the zigbee recommendation for bulbs. Can be had for dirt cheap and work reliably (and there’s high end options too if you want that). And are fully locally provisioned and controlled.

Matter over thread is also becoming an option but the default provision option requires Google (including play services and an account) and they tend to be quite a bit more expensive.

Not FOSS or open source in any sense. You could still say it’s self-hosted, but I suspect most people self-hosting care about this.

Can I see it?

Snikket is essentially just prosody but more of an all in one package.

Endurain, a self hosted fitness app, may get gadgetbridge integration once the network helper is finished.