• 0 Posts
  • 33 Comments
Joined 2 years ago
cake
Cake day: August 4th, 2024

help-circle
  • WG is not meant to be a stealthy protocol and is easy to detect at the ISP level. It has distinct characteristics that packet inspection tools can use to identify it by examining the traffic and block or flag it. Blocking it completely is trivial for any ISP, much less a nation.

    There are modified versions like AmneziaWG that make it stealthier, or alternative protocols built to evade traffic inspection like xray or sing-box (these two are really more like protocol frameworks that have multiple protocols you can use). It’s a bit of an arms race for packet inspection tools to be able to reliably identify these intentionally stealthy protocols, but the advantage is generally in your favor as long as you are using your own servers and not public VPNs. Though even then you need to take care to camouflage your traffic to be truly safe, like if you are shoving all of your traffic through one remote server that has approximately the same amount of traffic going out immediately etc that is something that can also be identified.

    How much precaution is actually warranted depends on where you are and what the potential consequences are. You don’t have to go to a full tinfoil hat paranoia level setup to avoid most blocking.















  • Not entirely sure about the de-google’d version of the Home Assistant companion app, but I know the regular companion app uses Firebase (and whatever the Apple equivalent is called, I forget) to deliver notifications, and it still would using Telegram as Telegram also uses Firebase. Apprise is a bit different as it can use multiple backends. Regardless, there are multiple ways to do things. Ntfy iphone and google app do not route your data through a third party server. I self host the ntfy server on my own machine and domain and my phone connects to it and receives data. It will deliver notifications wherever I am, not just in my LAN. It also provides a nice UI akin to Pushbullet I can use to send myself stuff privately.

    You can’t replicate all of what ntfy does with Home Assistant. There’s more to it than just delivering notifications, it’s the whole app frontend and persistent data etc. If it’s not clear to you what it’s for from my description you might have to go look into it yourself. Look at PushBullet, that’s most similar to what I primarily use it for.


  • Home Assistant notifications and almost all other notification services on phones actually route notifications through a cloud service like Firebase because Apple and Google try to railroad apps into their platforms. Ntfy lets you actually self host notifications without a third party, but also without killing your battery.

    That’s not the main thing I care about, though. Mainly I use it as a self hosted replacement for PushBullet, to share links and files with myself across machines and do some light alerting for servers and stuff (e.g. TrueNAS errors). Some of that could he done with HA, but ntfy is just better for some other uses with stuff like its web ui.

    Plus, apart from that ntfy is really easy to integrate with other stuff, like its easy to send a notification from a shell script or web hook so you can hack it into things that don’t otherwise support notifications (there are also lots of things that support ntfy natively, e.g. the arrs).