Samsung Smart TV owners can now use Jellyfin natively, as the open-source media server is now available on the Tizen platform.

        • NewNewAugustEast@lemmy.zip
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 day ago

          You have to do a lot of work. You would have to keep up on what domains it’s using (which were in the dozens four years ago for samsung), and make sure it doesn’t use some as kill switches if it finds something blocked.

          • kieron115@startrek.website
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 day ago

            Yeah. To be honest on the DNS side it would probably be far easier to just do a whitelist instead, block everything except your specific service. and yeah, its a stupid amount of work. i hate smart tvs but i’ll be damned if im gonna pay extra for a streaming box =|

              • kieron115@startrek.website
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 day ago

                to get something as flexible as my android tv i’d need an nvidia shield and those are going on ten years old at this point. maybe if/when they do a hardware refresh, assuming sideloading isn’t completely impossible by then.

      • kieron115@startrek.website
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        no it helps to block everything that isnt just netflix or whatever streaming service you use. you combine a DNS adblock along with blocking all the unused ports and it severely limits the communications. you could also add a vpn to add another layer of security.

        • prenatal_confusion@feddit.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 day ago

          Hardcoded IPS circumvent DNS blocks.

          Restricting ports doesn’t do anything since the TV isn’t running a service, it is contacting one.

          Correct me if I am wrong.

          • kieron115@startrek.website
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 day ago

            Not sure if you mean hardcoded DNS IPs or hardcoded “phone home” IPs. Hardcoded DNS addresses in devices are annoying, the only way i’ve found to get around that is using destination nat rules (DNAT) which requires more than a consumer router typically. hardcoded phone home IPs would get blocked by your firewall. you set up a rule that denies all outbound traffic from the TV, then only allow port 443 (or whatever port your streaming service uses) on the specific IP/IPs that your service uses. Here’s Netflix’s published IP info for example.