if you need a POSIX interface

SSHFS isn’t POSIX compliant. It doesn’t support hard links, file locking, atomic renames, full support for changing file permissions, umasks, and probably other things.

Versity S3 Gateway is another option that’s trying to focus on simplicity. https://github.com/versity/versitygw

Out of all these, SeaweedFS is the most scalable. Seaweed’s design is based off some of Facebook’s whitepapers about their warm storage system, and it works especially well for use cases that have a very large number of small files (like images).

SSHFS is very unreliable. At least use NFSv4 or even SMB/CIFS.

Practically every other object storage provider offers an S3-compatible API.

I haven’t tried any yet, but my understanding is that recently there’s been a trend of immutable Linux distros, where the root filesystem is immutable (read-only). Instead of directly changing stuff in /etc, installing apps, etc, you instead update some sort of config that says exactly how to set up the system, and rerun a script that rebuilds the root.

System updates are atomic - either the whole update is completed, or the whole update is rolled back. If the system breaks, you can revert back to an old config file and restore it to exactly the same state as it was before.

It’s still not very common - the majority of Linux systems aren’t doing this.

Monochrome? It still works.

They really are turning the frogs gay

If you’re fine pulling with legit services then https://monochrome.tf/ is probably the easiest to use (or their backend service if you want to automate it).

Musicbrainz is fine; it’s just Lidarr’s usage of it that’s a problem. Lidarr uses its own mirror of Musicbrainz, plus its own custom search code, and it’s not as reliable.

Other apps that use Musicbrainz data, like Beets and Picard, don’t have the same issues that Lidarr has.

Thanks for the info. It looks like there’s no way to migrate from Conduit. If I reinstall from scratch using the same domain, and create an account again, will everything still work properly including federation with other servers?

My server is just for myself.

What did you end up doing? I’m still running Conduit at the moment.

I like Pushover too. I’ve been using it for over 10 years now.

you need at least two NICs to properly setup a firewall.

I’m not sure I’d recommend it, but two (or more) VLANs on a single NIC would work fine too. This setup is usually referred to as “router on a stick”

I’m not sure about other OSes or Linux distros, but it’s easy to add multiple VLANs on Debian. You load the 8021q kernel module, then add interfaces suffixed with the VLAN ID (e.g. if your NIC is ens3, you’d add ens3.10 to /etc/network/interfaces for VLAN 10). You’d also need to make sure the switch port is configured to allow VLAN10.

Older NICs lead to regular crashes and/or slow network speeds.

but the ones you’re suggesting (I350-T2 and -T4) are 12 years old.

My guess is that they’d have a pool of accounts, and cache the most popular songs rather than streaming them from Tidal every time.

Sorry, I didn’t mean to say they’re the same. I meant to say that if all songs on an album are by one artist, the Artist and Album Artist will be identical. This is the case the majority of the time.

The major exceptions are collaborations (like you said), and compilations (which have “Various Artists” as the Album Artist)

Tidal would be seeing their site URL in the referer for the network requests.

Using it through Lidarr just uses the search feature in slskd, so it might not make it much better.

It’s even open-source! Nice site.

it had the ARTIST tag copied to the ALBUMARTIST tag

This isn’t wrong though - it’s a proper use of both tags. I think most of my music has both tags populated.

That site is pulling from Tidal, which is why the tags are good. All the legit streaming sites have well-tagged files.

Yes. The search results and music files are coming directly from Tidal, using someone else’s account. If you look in the network tab in the browser’s dev tools, you’ll see requests to Tidal.

Interesting design, since it’s trivial for Tidal to block something like this - they can see that the requests are coming from that site. I’m surprised they haven’t blocked it.

yt-dlp has a strict policy against cracking DRM

This is how it stays legal in the USA. Bypassing DRM is a DMCA violation (section 1201), but just downloading freely-available content is totally legal.

Its predecessor, youtube-dl, was subject to DMCA takedowns from the RIAA, and they had to get the EFF to help. yt-dlp doesn’t want to experience the same issues.