What is the problem with their docker implementation? I use it for more than one year and had no issues yet.

I keep seeing voidauth and want to try it, but then I get to their disclaimer and I give up:

I am not a security expert! Please do not use VoidAuth for any purpose that is security critical or high risk. VoidAuth has not been audited and uses 3rd party packages for much of its functionality.

Here’s my config for Authelia, maybe it helps:

    - domain: music.server.home
      policy: bypass
      resources:
        - '^/rest.*'
        - '^/api.*'
    - domain: music.server.home
      policy: one_factor

Jellyfin works without any issues with Android TV. I have an nVidia Shield and the simple remote does everything I need.

So let’s go destroy that too. No one would stop us.

I’m so fucking sick of this shit called omarchy. It’s literally everywhere related to Linux: in my mastodon feed, in my Lemmy feed, on YouTube! Someone is pushing it like a corporate product and I hate it. Plus, it’s created and pushed by a fascist. Fuck that too!

Looks like it’s a bug: https://github.com/nextcloud/android/issues/12137 and it’s not yet fixed, unfortunately.

If you’re running nc locally, check the logs, maybe there’s something relevant in there.

Check your DMs.

Call me old, but people should learn to discover music in different ways (friends, press, concerts, etc.) and not wait to be fed by corporations… just a thought.

Jellyfin sucks for music. I tried it several times, hoping it got better, but unfortunately it’s not the case. For the moment I’m still using Navidrome (which I used for the last 3-4 years without problems).

Oh, not this again! Move on with the times!

Tokyo Night comes to mind - it started as a VSCode theme, but you can find a lot more applications/tools that implemented it.

There’s no conflict regarding ports. Each container can have the same ports open. You’re thinking about the host network here, but it’s not the case.

Are you sure both containers (npm and audiobookshelf) are in the same network? I see you don’t specify the network in the NPM compose file.

Check that like this:

$ docker inspect container-name| grep -A3 Networks
            "Networks": {
                "network_name": {
                    "IPAMConfig": null,
                    "Links": null,

See if both your containers are in the same network - they should be.

This is about addressing the containers in docker. It has nothing to do with the local network.

I tested it and it’s not that reliable. At least for me it didn’t let me see events in the future (next 1,2,3 months) and I wasn’t able to modify an existing event, so I gave up. I also don’t have the time right now to open issues in their repo.

Any caldav web app should be able to do it.

Yes… and where are those? I know of agendav and infcloud, both of which are not that good: agendav is not currenly maintained and infcloud is a mess to set up.

If anyone is still using teamviewer after the many breaches they had, they deserve this ;-)

and stupid people are downvoting me for what? because I told my use case? fucking idiots!