smiletolerantly

joined 1 year ago
[–] [email protected] 1 points 2 weeks ago

Which shouldn't really be an issue since you should only host on 443, which tells bots basically nothing.

Configure your firewall/proxy to only forward for the correct subdomain, and now the bots are back to 0, since knowing the port is useless, and any even mildly competent DNS provider will protect you from bots walking your zone.

[–] [email protected] 2 points 2 weeks ago

Sorry, saw this only just now. I don't really have any guides to point to, so just the basic steps:

  • host jellyfin locally, e.g. on http://192.168.10.10:8096/
  • configure some reverse proxy (nginx, caddy, in my case it's haproxy managed through OPNSense)
  • that proxy should handle https (i.e. Let's Encrypt) certificates
  • it should only forward https traffic for (for example) jellyfin.yourdomain.com to your Jellyfin server
  • create a DNS entry for jellyfin.yourexample.com pointing either to your static IP, or have some DynDNS mechanism to update the entry

90% of this is applicable to any "how to host x publicly" question, and is mostly a one-time setup. Ideally, have the proxy running on a different VM/hardware, e.g. a firewall, and do think about how well you want/need to secure the network.

In any case, you then just put in https://jellyfin.yourdomain.com/ in the hotel TV.

[–] [email protected] 1 points 3 weeks ago (2 children)

I have never used Tailscale. I have also Jever seen anyone in the wild recommend it and explain what exactly the use-case is beyond plain, old, reliable, open source WireGuard.

So yeah, agreed.

Also I have been hosting Jellyfin publicly accessible for years with zero issues, so idk... I also dint k ow what the "you have to use Tailscale for jellyfin" people are doing with TVs/Firesticks/... in hotels, airbnbs,...

[–] [email protected] 1 points 1 month ago

Chat, is this AI-generated ads on Lemmy?

[–] [email protected] 8 points 1 month ago (1 children)

Are we talking permanent background tracking? Or sending a message "hey, I'm here"?

[–] [email protected] 16 points 1 month ago

Just in case this post is real: the world does NOT hate you. Not you, not your people, not your country.

We wish you could achieve the freedom to experience the entire world.

[–] [email protected] 3 points 1 month ago (1 children)

For manga, I've found Mihon to be nicest, by far, and it supports the API. For books, I am currently "stuck" on koreader on Android (which "only" supports OPDS-PS). I do most of my reading on a reMarkable currently, and that has no supporting client. Writing one is on my to-do list, but it's a bit daunting of a task....

Here is a pretty good list of what is supported where.

[–] [email protected] 2 points 1 month ago (1 children)

I think I have set Suwayomi to download / convert to CZB, not for Kavita specifically, but because a lot of reader apps cannot handle loose images

[–] [email protected] 2 points 1 month ago (3 children)

Haven't had any issues in that regard, so can't really say, sorry. I have two folders (Mangas and ebooks) on my NAS, and in Kavita, created a library for each.

You absolutely can edit metadata, although I personally haven't had the need yet. I use readarr and suwayomi for "obtaining" books and manga, respectively, and what they come up with is usually just fine.

[–] [email protected] 9 points 1 month ago (8 children)

I went through essentially the same thing a couple months ago. Tried Calibre (and Calibre server) since everyone recommended it.

Really disliked it. Calibre is great for converting ebooks, but has shit management and webserving capabilities.

I ended up with Kavita and am super happy. On the web client, both management and actual reading are a pleasure. Any phone/tablet client supporting OPDS works perfectly to read/download your manga/books from the server.

And a select few clients go a step further, supporting Kavita's API, which allows for 2-way sync (effectively, syncing reading progress between all your devices).

[–] [email protected] 7 points 1 month ago

Yeah but conduit is so stale, it might as well be discontinued

[–] [email protected] 4 points 1 month ago

I still find it hilarious that since dd-wrt and OpenWrt are just… Linux, you could install Super Mario Bros on there. I checked, nobody seems to have tried.

Oh, definitely, but there are varying degrees of difficulty, esp. with what kinds of packages / package management you have available :D

Ah, that make sense. Is Wireguard P2P?

Yes, in the sense that each node/device is a peer. But the way I'd suggest you configure it in your case is more akin to a client/server setup - your devices forward all traffic to the "server", but it never takes initiative to talk "back" to them, and they do not attempt to communicate with each other. Unless you have a separate usecase for that, of course.

You both are perfect for each other, so don’t screw it up!

❤️

Closing in on 8 years

view more: ‹ prev next ›