• 0 Posts
  • 165 Comments
Joined 1 year ago
cake
Cake day: February 1st, 2024

help-circle




  • Lemmy is not encrypted, my comments are public, your comments are public, we both know that. Anyone with a raspberry pi or an old netbook can scrape them.

    If I use an encrypted service and all of a sudden everything that I thought was encrypted was decrypted by the service provider without my consent? That’s breaking encryption.

    If on the other hand I use an encrypted service and they tell me that they can no longer offer the service, my data will be destroyed after X days, and I need to find another way of storing my encrypted data because of privacy invading government policies? That is not breaking encryption.


  • For many things I completely agree.

    That said, we just had our second kid, and neither set of grandparents live locally. That we can video chat with our family — for free, essentially! — is astonishing. And it’s not a big deal, not something we plan, just, “hey let’s say hi to Gramma and Gramps!”

    When I was a kid, videoconferencing was exclusive to seriously high end offices. And when we wanted to make a long distance phone call, we’d sometimes plan it in advance and buy prepaid minutes (this was on a landline, mid 90s maybe). Now my mom can just chat with her friend “across the pond” whenever she wants, from the comfort of her couch, and for zero incremental cost.

    I think technology that “feels like tech” is oftentimes a time sink and a waste. But the tech we take for granted? There’s some pretty amazing stuff there.











  • 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!


  • qjkxbmwvz@startrek.websitetoTechnology@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    27
    ·
    edit-2
    5 months ago

    The network gear I manage is only accessible via VPN, or from a trusted internal network…

    …and by the gear I manage, I mean my home network (a router and a few managed switches and access points). If a doofus like me can set it up for my home, I’d think that actual companies would be able to figure it out, too.