this post was submitted on 15 Jul 2025
711 points (99.7% liked)

Selfhosted

49589 readers
467 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Not exactly self-hosted but I know many jellyfinners here would cherish this as well.

you are viewing a single comment's thread
view the rest of the comments
[–] somewa@suppo.fi 9 points 3 days ago (2 children)

Looks promising. Does remote controllers work with it?

[–] SomeoneSomewhere@lemmy.nz 12 points 3 days ago (1 children)

I expect so.

KDE Connect also works great as a remote control for many things, presumably including this.

[–] Lumisal@lemmy.world 2 points 3 days ago (2 children)

I'm wondering what I've done wrong with KDE Connect as I could never get it working on any device across 3 different smartphones

[–] SomeoneSomewhere@lemmy.nz 2 points 2 days ago

I found opensuse's default firewall rules were very restrictive and you needed to open a port.

[–] MajorSauce@sh.itjust.works 3 points 3 days ago (1 children)

Sadly the distributions I tried did not open the required port(s) on the built-in firewall (Bazzite and CachyOS, for two).

I would suggest to disable any firewall and check if you can pair.

[–] greybeard@feddit.online 1 points 3 days ago (1 children)

You are probably correct that the firewall is the culprit. Good suggestion.

I realize disabling the firewall for testing is OK, but I recommend looking up what it takes to open the ports or app in the firewall instead. I've spent my whole career running into and fixing instances where techs disabled firewalls for "testing" and never re-enabled them.

[–] Trainguyrom@reddthat.com 1 points 2 days ago

You mean they didn't just turn off the firewall on all client machines and rely entirely on a single firewall at the network gateway? Because that's what I've seen way too much of...

[–] bjoern_tantau@swg-empire.de 1 points 3 days ago (1 children)

HDMI-CEC seems to be currently unsupported. So you won't be able to use your TV's remote yet.

[–] pjusk@lemmy.dbzer0.com 8 points 3 days ago (2 children)

The article actually stated that the featured is untested.

Controller support exists, but getting TV remotes to work over HDMI CEC is still untested.

[–] WhyJiffie@sh.itjust.works 2 points 3 days ago

now, that sounds more interesting than just "unsupported"!

[–] greybeard@feddit.online 1 points 3 days ago

Being Linux, if you were really motivated, you could probably write a shim service that converted CEC to basic input that it does support, or someone out there probably already has.