RSS feeds seem like the obvious replacement—how is your vibe-coded solution better?

MediaWiki’s probably overkill for basic wiki functionality, but I use it for the sake of Semantic MediaWiki and associated extensions. But SMW has more of a learning curve, so it might not be worth it for a casual-use wiki.

In terms of software, yes. But HA can be run on nearly anything—there’s no need to buy their hardware to use it.

Having a world map that has pins on it based on location EXIF data in photos

Don’t you get that in NC already, if you go to Maps > My Photos ?

Syncthing uses a centralized discovery server to connect device IDs to IP addresses (although you can change this to point to your own discovery server, too).

I don’t know if Funkwhale has a similar option.

I don’t have a thermostat, but I have indoor and outdoor temp and humidity sensors, and a window position sensor. HA notifies me (via lighting color) if I should open the window because the outdoor conditions are better than indoors, or vice versa.

I assume it’s because it reduces the possibility of other processes outside of the linked containers accessing the files (so security and stability).

CasaOS is not an operating system and more like a GUI for Docker

So it’s more like Portainer?

Internal server (Home Assistant etc.): domus
External server (Nextcloud etc.): nimbus
Router/firewall: murus

I believe so—see Wake-on-LAN.

If anyone’s interested in adding similar functionality to their own MediaWiki installation, you can use the ModernTimeline and SemanticMW extensions without the need for an AI to parse the pages for dates.

deleted by creator

One under-appreciated aspect of Docker is that it forces you to document all your setup steps in your dockerfile and docker-config files.

I haven’t tried it because I’ve read a lot of negative discussions of it—and because (by my understanding) the only reasonable use case would be if there were a large number of users and each user is likely to have copies of the same files but don’t want to expose their files to each other (so you can’t just manually de-dupe).

the tech community keeps waiting for everyday people to take the baton of self-hosting. They never will—because the effort and cost of maintaining self-hosted services far exceeds the skill and interest of the audience.

The same argument could have been used a century ago to claim that everyday people would never switch from trains to private cars, because the effort and cost of maintaining a car exceeds the skill and interest of most travelers. That may have been true at one point, and may be true again in the future—but it’s contingent on changing circumstances, not a categorical truth.

You can install and run Stable Diffusion locally (Pinokio is a versatile installer that can run SD and many other open-source AI tools as well). With SD you can build your own upscalers that are better than Upscayl, and do things like background removal too (in addition to prompt-based generation and such).

A typical use case is to forward a single port to the proxy, then set the proxy to map different subdomains to different machines/ports on your internal network. Anything not explicitly mapped by the reverse proxy isn’t visible externally.

Does it need to be accessible via API (e.g. SQL) or just a spreadsheet-style web interface?

You can use any port for SSH—or you can use something like Cockpit with a browser-based terminal instead of SSH.

If you didn’t map a local config file into the container, it’s using the default version inside the container at /app/public/conf.yml (and any changes will get overwritten when you rebuild the container). If you want to make changes to the configuration for the widget, you’ll want to use the -v option with a local config file so the changes you make will persist.