Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @[email protected]
every time I have an idea for some little quality of life tool that involves pulling data from a site I would normally have to browse to directly, I can’t do it because everything is captcha’d to all hell.
On the flip side, a bunch of services / web apps (mostly paid ones) are adding APIs to become “AI native”… but you can use those APIs without having to use AI too.
A lot of sites wouldn’t exist without ads, because they want their stuff to be freely-accessible and don’t have any other revenue streams. It would also cut off lower income people that couldn’t afford to pay.
The only business models that have really worked online have been:
If ads go away, a lot of sites/services would have to become paid services, and smaller ones might just shut down entirely. We’d end up with even more consolidation of the market.
Your comment isn’t entirely accurate.
in an overwhelming amount of cases, that host networking will be a “here’s a device-local subnet your containers can join to”, so no, a Docker container won’t by default “get it’s own IP address”
With the default NAT network, it gets its own IP in the 172.16.x.x range that Docker decides to use. That IP is accessible from the Docker host. It doesn’t matter that it’s not on your LAN - it’s still a dedicated IP. Port forwarding (or a reverse proxy) to it is a separate thing, and you can map a different port if you want to.
Plenty of Docker containers use the same port (often 80, 3000 or 8000), and the reason you can use multiple of those containers concurrently is because each one is on a separate IP.
The default NAT network isn’t commonly used for Home Assistant, though. It usually has a direct network connection to the LAN, since plenty of smart home devices rely on broadcasts for discovery.
Also claiming that “nothing else will use port 80” is a gross over-simplification.
It’s true for both the Home Assistant Docker container and for HAOS. In both cases, there’s no other web servers running in the container/VM. For the Docker container:
If you’re using the default Docker NAT network, the port you use to expose it to other devices is completely unrelated to the port used in the container. When you expose a Docker port, you specify the host port and container port separately.
proxy_pass http://hass/If you bridge the Docker container to the LAN, it has its own IP on the LAN and no other web servers will be running on that IP.
The actual reason that Docker containers don’t use port 80 by default is so they’re able to run in rootless mode without any extra capability grants. I don’t think Home Assistant supports rootless mode though.
I generally respect this guy’s opinion (I probably use the term “enshitification” multiple times a week
A lot of people don’t use it the way he used it though. He used it specifically for two sided markets (eg a service that has both businesses/advertisers and personal users) where the focus shifts to the business customers, but people have started using it to mean anything that used to be good but isn’t good any more.
There’s two supported ways to run Home Assistant:
In both cases, it’s running on its own IP address, so nothing else will be using port 80.
With Docker, you’d normally either use its standard NAT network, or bridge it to your LAN using a macvlan or ipvlan network. Bridging is usually better because some devices rely on broadcasts.
You used to be able to run Home Assistant directly on an existing Linux system, but that’s been deprecated for over a year and unsupported since December last year.
I use healthchecks + runitor for notifications. Would recommend. I posted another comment about them.
I’d recommend self-hosting healthchecks and using runitor for your cronjobs. Runitor pings healthchecks when the cronjob starts, then pings it again on completion with the status (success or fail) along with the stdout and stderr.
Healthchecks can be configured to expect a ping periodically (once per day, once per hour, whatever) and alert you if it doesn’t receive one.
For backups, Borgmatic has a healthchecks integration.
RFC3339 is better than ISO8601 since it doesn’t allow some of the esoteric formats, and allows some useful formats that ISO8601 doesn’t (like separating date and time by a space instead of by T)
For example, 2026-W32-1 is also a valid ISO8601 date: Monday on the 32nd week of 2026. That format isn’t allowed with RFC3339.
RFC3339 is better than ISO8601 since it doesn’t allow some of the esoteric formats, and allows some useful formats that ISO8601 doesn’t (like separating date and time by a space instead of by T)
For example, 2026-W32-1 is also a valid ISO8601 date: Monday on the 32nd week of 2026. That format isn’t allowed with RFC3339.
This looks like an AI edit rather than an actual renovation.
The shelf thing on the left has exactly the same items on it. Why would they keep the hole with the CRT TV in it? Also I’d hope that nobody would actually put a square table in a round space.
For other alternatives with their own engine - the main ones are Yandex, Mojeek, and Qwant. DuckDuckGo is good, but most of their results come from Bing.
Kagi is priced well for what you get. Search engines are very expensive to run. You don’t have to pay for the premium AI, and the pricing of the starter ($5/month for 300 searches) and pro ($10/m for unlimited searches) plans hasn’t been affected by AI. They’ve remained the same price ever since they launched in 2022.
The hostname will be encrypted eventually (ESNI) but you’re right that the IP address is visible.
Destination IP is starting to mean less and less these days, given there’s a large amount of sites that use shared IPs rather than dedicated ones (for example, if they use Cloudflare, Vercel, Netlify, AWS CloudFront, etc.)
- It encrypts your internet traffic in transit
Note that most sites use TLS these days, so your data is already encrypted in transit.
There seems to be two groups of people:
People that use services like AWS and pay hundreds (or more) per month: “Wow, hosting is so expensive now!”
People that host a bunch of stuff on a $40/year VPS: “Wow, hosting is so cheap now!”
I’ve got several VPSes with 40Gbps (shared) networking, 8 or 16GB RAM, decent amount of space on RAIDed enterprise NVMe SSDs, fast AMD EPYC CPUs, that cost less than $60/year. 20 years ago before VPS hosting became popular, you’d need to pay at least $100/month for a dedicated server with a consumer CPU, single IDE hard drive, tiny amount of RAM, on a 100Mb/s connection.
Not to mention being able to host a bunch of stuff at home for cheap with a low-power single-board or mini PC., and Hetzner making dedicated servers very cheap too.