• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle

  • I agree with this assessment. You do not need an overlay mesh network like tailscale for your use case that is way overkill.

    And if you are running Jellyfin as opposed to Plex then you probably care about realizing the security benefits of open source so you definately don’t need a closed source proprietary solution like tailscale or creating accounts on someone elses computer for protection from x. Cloudflair is selling a closed source solution to a problem you don’t have.

    This is selfhosting yet these recommendations are all for signing up for accounts and software from the largest centralized systems on the Internet and routing all your traffic through Oracle or cloudflair, lol If your going to do that then why not just host everything with Amazon or switch to Google products. You don’t need any of that noise.

    Your best bet is to create a reverse proxy- a single ingress point in front of those few services with a single open port. Pick whatever web server you want your server already has Apache and it like 10 lines of config very simple.
















  • Custom field support- TXXX is also nice but I was refering to the id3v2 standard fields. It looks like beets doesn’t support most fields actually.

    How about composer or conductor for classical tracks or remix for EDM, language, grouping, media type, mood etc.

    These tags have been part of the id3 standard for over 2 decades, I wonder why beets choose not to support then.

    I read that doc but sadly most fields are missing. I cant see beets being useful for any serious collection without basic field support.

    Its too bad, beets looks promising but Linux lacks an open source solution with decent id3 tag support. There are several windows apps (all closed source) that have been around for a long time with very good comprehensive id3 tag support but none foe Linux.