s3fs-fuse VS beets

The author needs to ask themselves: in this cloud technology stack, is there POSIX involved somewhere lower down, where I can't access it? The answer is, of course, "yes". The sort of cloud storage systems described all run on top of POSIX APIs. They provide convenience (cost efficiency is more debatable) compared to the POSIX alternative, but that's because they exist at an entirely different conceptual layer (hence the presence of POSIX anyway, just buried).

Your point about surfacing a POSIX that's actually there but hidden and thus visible to low-level Amazon employees building the S3 service which makes it invisible to S3 end customers is true but isn't the the point of the article. The author is saying there are motivations for a POSIX-like api visible also the end user.

So your explanation of stack looks like 2 layers: POSIX api <-- AWS S3 built on top of that

Author's essay is actually talking about 3 layers: POSIX <-- AWS S3 <-- POSIX

That's why the blog post has the following links to POSIX-on-top-of-S3-objects :

https://github.com/s3fs-fuse/s3fs-fuse

https://github.com/kahing/goofys

https://www.cuno.io/

sudo apt install build-essential libfuse-dev fuse git clone https://github.com/s3fs-fuse/s3fs-fuse.git cd s3fs-fuse sudo apt install libfuse2 sudo apt install libcurl4-openssl-dev sudo apt install libxml2-dev ./autogen.sh ./configure make

Don’t know actually. Here is project page.

s3fs-fuse

How is this different than these other solutions?

https://github.com/kahing/goofys

https://github.com/s3fs-fuse/s3fs-fuse

I don’t get it. Why not just improve https://github.com/s3fs-fuse/s3fs-fuse

I was always frustrated that there is no solid source for synced lyrics that also offers decent API support. There is good ol' Crintsoft's MiniLyrics that is thankfully free software, was what I used a lot in my childhood, but unfortunately the API is highly obfuscated. Another popular choice is the Musixmatch API, which has a very large database of synced lyrics, but with "free" API that are reverse-engineered from their app, you will quickly run into rate-limit.

That's why I created LRCLIB. It's aimed to provide completely free synchronized lyrics for everyone, especially for FOSS music players, with zero profit intention. It currently has nearly 3,000,000 (not deduplicated) lyrics in database. You can also contribute to the database by adding and syncing lyrics for your favorite songs using the LRCGET client.

I'm trying my best to make LRCLIB server-side code open-source as soon as possible. But right now, full LRCLIB's database dumps have already been uploaded regularly and publicly, which are simply sqlite3 files. Feel free to download, look at or do anything you want with the database at https://lrclib.net/db-dumps.

Many open-source projects have already begun integrating LRCLIB, including:

- beets - music library metadata management (https://github.com/beetbox/beets)

I just ssh onto my server and use beets to remotely organize my navidrome collection and edit metadata. Beets has lots of auto-tagging features and I rarely need to edit anything manually. Works great if you are ok with using the command line.

You could try https://github.com/beetbox/beets but it seemed very manual and extremely slow. I had better luck with Picard.

Honestly? I use https://beets.io/ to organise all my FLAC on my NAS.

I expose the /Music directory over NFC.

I use https://kodi.tv/ to stream music to my amp. I manually pick the album I want to listen to.

Kodi also has a fairly reasonable web UI.

Keep it simple.

If you're technically inclined, there's beets.

You should check out beets.

Yes, you have the torrent client call beets.io on the folder and have beets configured.