marsara9

More technically there's two ways to move data between two separate services. You can either pull or push the data.

Assume for both scenarios that the client is your phone and the server is some machine in the cloud.

With pulls the client calls an API and the server returns a response. Generally the www works this way. You ask a server for a wab page and you effectively pull the source down to your browser.

Pushes work the opposite, in that a server has data for the client and needs to push or otherwise give it to you. Pulls are relatively strait forward because every server has a well known name (the domain name and url). But your phone's IP address changes constantly. So how does a server know how to contact your device? There's generally two ways:

1. Your device can poll (make repeated pulls to a server checking for new data)
2. Or you can register some identifier and your IP address with some central server every time it changes. And then the server can essentially call a URL on your device directly. This is essentially what Google and Apple are doing as it doesn't waste CPU resources and your battery.

You could in theory implement either of these yourself but because of the way the OSes work on both Android and iOS there's no guarantee that you can keep a process running in the background forever. As the OS can kill your process if the OS needs more free ram, etc ... The built in notification APIs are exempt from this because they are part of the OS.

If you're worried about your IoT devices on your LAN the problem isn't necessarily that they can access WAN but rather that there's a security vulnerability and that they can be accessed by the WAN. Once a device is compromised and attacker can then use it as a "beachhead" to access other devices on your network.

So for example, with my setup every IoT device is on a separate VLAN (the guest network acts similarly) which can't get access to WAN, can't be accessed from the WAN and can't initiate any network calls to any other VLAN. Now my primary VLAN can talk to my IoT VLAN, and IoT can talk back, it just can't start the communication.

This does pose a problem for TVs though that need to talk to Jellyfin as hinted at in the original post. So what you could do is create a specific firewall rule that allows the TVs to at least initiate communication to Jellyfin but not any other device on your primary VLAN. This will probably require a more sophisticated router though than most of the consumer ones out there. Just be mindful that if n IoT device is compromised they can then try to attack the jellyfin server to jump to your other VLAN and then the rest of your network.

Just wanted to add... After reading your initial post I did some more digging on adding tracking headers, etc... especially by T-Mobile.

While it's definitely a thing, it only applies to HTTP traffic. Even HTTPS blocks their ability to add those headers. So any traffic that's using any other protocol (DNS, email, ssh, or just gaming, etc...) would be safe from your ISP from at least trying to add these tracking headers.

Yes but while the service is targeted for home use there still is remote work which generally requires a VPN back to the company network. They wouldn't be able to block this. Now sure they might be more inclined to block Mullvad but they'd impact too many businesses by blocking wireguard as a whole.

And assuming they did block Mullvad but not wireguard... Just rent a VPS and install a wireguard server and client there to bridge back to Mullvad.

I know this doesn't help much but I use T-Mobile cell towers with an always on VPN with no issue. But I don't see why they'd block Mullvad. (I'd be more concerned that they'd block them than wireguard in general). But there's completely legitimate reasons to use both so I don't see them really bothering to block either.

To also add to the other comments: because the government doesn't want or even need to have a balanced "checkbook".

Assume for example you want to buy something from me. But you only have "don bucks". So you buy a widget from me and I charge you 10 "don bucks".

Problem though, through taxes you've only got 5 bucks left. So you just create 5 bucks and add it to your pile. (Deficit spending) Now if you don't balance that with a loan, your "don bucks" are now worth less because why would I want one of your "don bucks" when tomorrow you could just create a million of them for no reason. (Hyperinflation) So you instead borrow 5 bucks from a friend of yours with a promise to give him back 6 tomorrow. (Bonds)

I still sell you my widget for 10 "don bucks" but now what can I spend my newly acquired "don bucks" on? Well, since everyone has their own currency I ultimately have to spend it on you. This means I end up giving you those 10 bucks back in hopes that you'll either give me more in return (another loan/bond) or give me back my own currency from money I've traded to you.

So in the end spending more than you make (at the nation state level) can be a net boon on the economy as you effectively create a vendor lock in, similar to how companies push their gift cards, etc ... because that money is only good in one place. You just have to make sure not to spend too much beyond your means because every dollar you create this way adds to inflation a little bit. So if you create too much then inflation gets out of hand and you end up with hyperinflation and now every one of your citizens wants to get rid of your money because they'll lose too much before they can give it back.

If it was a certificate issue I'd expect youd just get an error from your browser saying the cert is invalid or expired.

If I had to guess though you're running into a nat reflection issue: https://nordvpn.com/cybersecurity/glossary/nat-loopback/

Read up on that. But you may need to provide different DNS entries if you're inside or outside your LAN or add a NAT hairpin rule to your router. But this is only applicable if you're exposing the same service to the WWW.

Some other things to try though:

• Have you tried just pinging the address? Is the DNS resolution returning the address you expect?
• Whats in your nginx logs? Do you see anything when you try and connect?
• Within your nginx container can you ping your service directly? Is something blocking nginx from accessing the site?

Because of changes in how the lemmy API works I had to abandon the project awhile back.

The GitHub page is still up and if anyone wants to take over they're more than welcome. But the project would need a complete rewrite in order to function and even then there'd still be limitations.

Yes, but Google at least innovated and tried to increase customer value with Android. They also make better phones (from some people's perspective) than Apple. I've seen nothing from Epic that tells me that their product is better than Steam. Sure they have free games, but that business model isn't sustainable and for the non free games, why would I buy from them vs Valve? Sure, if I was a developer I might get a better deal with Epic, especially if I can sign an exclusivity agreement), but I'm not a game developer I'm a gamer just looking to play my games on my PC as easily as possible.

I can't speak for anyone else but I can at least share why I didn't care for it.

Steam already exists and there isn't a lot I feel is missing from the Steam store. Not to mention there isn't anything that Epic does better than Valve for their storefronts. Epic doesn't provide any new value that Valve doesn't. In fact I'd argue that Epic causes negative value for several reasons:

1. They essentially fragmented the PC market as now I can't access all of my games in a single location. The same reason for example that I hate that Netflix, Hulu, Disney+, HBO Max, etc ... exist. It just makes the overall experience less convenient and more expensive.

2. Several features that Steam already has working are either broken or missing in the Epic Store. Especially around the shopping cart, etc ... I haven't gone to look recently to verify if any of these have been fixed and probably won't until the other points are addressed, if they even can be resolved.

3. There's no level of trust with Epic compared to Steam. I have a massive Steam collection and Valve has shown time and time again that I can trust that my data is relatively safe with them. When was the last time you saw Valve in the media because of a data breach? When was the last time your Steam account got hacked. Epic is just new here so they haven't had a chance to earn that trust.

4. Their motives for wanting to create a new store wasn't to improve the customer experience. Instead it was to improve their bottom line. The court cases against Google and Apple prove this. If they at least tried to have a PR campaign to show how Epic is innovating compared to Steam especially for making the customer experience better, the Epic Store might have sit better with me.

5. Timed exclusives. Similar to point 1, but they were just trying to use their massive cash reserves from Fortnight to buy their way into the market rather than earn the trust of customers. This again resulted in fragmentation of the PC market.

Anyway, just my two cents.

I've tried commenting out the ports in the compose file, which should make them only available on the internal network, I thought. But when I do that, the containers can no longer connect to each other.

Did you create an explicit network for them to talk on? Otherwise the default docker network doesn't support internal DNS queries.

https://docs.docker.com/engine/network/#container-networks

Specifically you need a network using the bridge driver: https://docs.docker.com/engine/network/drivers/bridge/

Can you share the Home Assistant automation / setup that you have for Uptime Kuma notifications? As I'm in the same boat as you. I just got a webhook setup but I'm getting flooded with notifications, especially after services update.

My hope is I just want to be notified when a particular service is down for say 5 minutes but all I care about is knowing the node name. I don't necessarily care to get notified if the service comes back up.