• 0 Posts
  • 380 Comments
Joined 10 months ago
cake
Cake day: February 1st, 2024

help-circle
  • I think there’s a bias in the US against this sort of thing that doesn’t exist (or not to the same extent) in Europe due to the age of the cities/buildings.

    In the US, a building from the 1700s is a historic artifact to be cherished, while in parts of Europe a building from the 1500s is just the local pub.

    So, the US is often hesitant to modify these old buildings, but Europe seems to have more of a perspective of “it’s a building, not a museum, let’s give it new life by modifying it.”

    This is just from the perspective of me, from the US — and I think these old/new buildings are really neat!









  • English isn’t even the official language of the United States — we don’t have an official language.

    Various states have official languages (19 states + DC don’t have any official language); of these states, English is indeed official, with a few states also recognizing native languages as official alongside English.

    Of course that’s beside the point, as even calling this sort of racism “thinly veiled” would be far too charitable.


  • Hmm, my understanding was that FQDN means that anyone will resolve the domain to e.g. the same IP address? Which is the case here (unless DNS rebinding mitigations or similar are employed) — but it doesn’t resolve to the same physical host in this case since it’s a private IP. Wikipedia:

    A fully qualified domain name is distinguished by its lack of ambiguity in terms of DNS zone location in the hierarchy of DNS labels: it can be interpreted only in one way.

    In my example, I can run nslookup jellyfin.myexample.com 8.8.8.8 and it resolves to what I expect (a local IP address).

    But IANA network professional by any means, so maybe I’m misusing the term?



  • If you have your own domain name+control over the DNS entries, a cute trick you can use for Jellyfin is to set up a fully qualified DNS entry to point to your local (private) IP address.

    So, you can have jellyfin.example.com point to 192.168.0.100 or similar. Inaccessible to the outside world (assuming you have your servers set up securely, no port forwarding), but local devices can access.

    This is useful if you want to play on e.g. Chromecast/Google TV dongle but don’t want your traffic going over the Internet.

    It’s a silly trick to work around the fact that these devices don’t always query the local DNS server (e.g., your router), so you need something fully qualified — but a private IP on a public DNS record works just fine!