StarkZarn

They place arbitrary limits on home users as well, which is a secondary reason to not use it compared to open source offerings. For instance:

• you are limited to 1Gbps line speed
• you are limited to one week of analytics, with no export option, so you can’t even ship them elsewhere
• there are also resource limits that prevent ram and CPU utilization

I’m not sure you understand what “objectively” actually means… Care to provide your data in support of your objective conclusion?

Ran into a similar conundrum. We use mealie for recipe management and occasionally meal planning, but the shopping list is clunky. We resorted to just making a list on a card in Planks. Not purpose-built, but it has worked rather well for us.

I don’t know how you got a picture of me, but I demand it is removed!

Potentially, but precision is important, especially if you’re going to make sweeping claims about a topic, acting as an authority.

This is absolutely not what DNSSEC is. DNSSEC provides authenticity of the response, not privacy. You’re describing a means of encrypted name resolution, like dns-over-tls, dns-over-https, etc.

I haven’t done a code review so I can’t answer that question with facts. I do think however, that anything that bootstraps a FLOSS framework like openwrt could easily be a risk to privacy.

You use privacy and security interchangeably here. They are not the same.

If you have any question on truth worthiness, you can flash stock openwrt on them. You just lose out on their proprietary webUI and pre installed plugins. I believe their firmware is public on GitHub though.

You don’t need haproxy on the vps at all, unless I’m misunderstanding you. Just route the traffic using iptables hooks in your wireguard config. This is exactly how I manage my email server and it’s entirely transparent.