• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: April 11th, 2024

help-circle

  • This looks interesting. Just a few thoughts (sorry if these dont belong in a recruitment post, feel free to ignore):

    Radarr and sonarr already have a function to look at ones library and offer recommendations for new adds. How is your proposed functionality different?

    Lidarr import of existing library or even grabs/downloads is atrocious. It’s damn near unusable, and a lot of people (myself included) don’t use it because it’s functionally useless if one has to manually import every song or album. I’m not sure it’s worth spending time building anything on top of Lidarr. Thoughts?

    The Anna’s archive integration for readarr looks awesome, though. I look forward to trying that out.

    A lot of people are only interested in downloading flac for music. Iirc, spotdl doesn’t do flac. Any plans to integrate for example lucida or, I’m not sure if deemix is still working? There have been several successful tools that built on top of deemix in the past, for example deemon, not sure how integration with those would look. Ideally one could add artists lidarr-style, a deezer arl, and the program does the rest (see lidarr-on-steroids).





  • My interpretation of your linked instruction (granted, I haven’t tried plex) is that it’s the same two scenarios.

    Your plex client app login talks directly to your server login. The client app meeting the server is arranged by the plex relay server and nothing more. There is no ‘logging in’ to the plex relay server; it’s function is to arrange a meeting of two tunnels and that’s it, much like a tailscale derp server.

    The relay server is serving the same function as caddy on a VPS, hell, they could even be using tailscale under the hood and it’d look exactly the same to a user.

    Anyway, attack vectors even with a public facing jellyfin are mitigated because

    a) jellyfin is running in a docker container = a successful attacker would only be able to trash my jellyfin container, which ultimately is not that big of a deal (unless there is a different docker exploit that enables access to the server itself, which is an entirely different issue and larger than a jellyfin/plex discussion)

    b) fail2ban in conjunction with a reverse proxy bans malicious ip addresses that come back with too many errors too many times (errors that you, the admin, specify) So, for example, brute force login attacks are mitigated.

    c) the reverse proxy itself allows access to only one specified internal ip address/port combination. Pending a caddy exploit (again, a different discussion) it is not possible to fish for acrive ip addresses or port scan my internal network.







  • I tried minicpm-v, granite3.2-vision, and mistral.

    Granite didn’t work with paperless-gpt at all. Mistral worked sometimes but also just kept running sometimes and didn’t finish within a reasonable time (15 minutes for 2 pages). minicpm-v finishes every time, but i just looked at some of the results and seems as though it’s not even worth keeping it running either. I suppose maybe the first one I tried that gave me a good impression was a fluke.

    To be fair, I’m a noob at local ai, and I also don’t have a good gpu (gtx1650). So these failures could all be self induced. I like the idea of ai powered ocr so I’ll probably try again in the future…