My music setup was a pinned browser tab for years. It worked, technically. It also ate RAM doing nothing, my media keys only worked when that tab happened to be focused, and I killed the music at least once a week by closing the wrong window. There's no official YouTube Music desktop app on Linux, and most of what exists is the same web player in an Electron shell.
So I built my own. It's called Limusic. Rust and Tauri, no bundled Chromium, audio goes through libmpv.
You sign in with your actual YouTube Music account, so your playlists, likes and subscriptions are just there, and liking a song or adding it to a playlist syncs back like you'd expect.
The part I actually care about is that it's not bare bones:
- Proper MPRIS, so media keys and your now playing widget just work
- System tray, closing the window doesn't kill the song, plus play/pause and skip from the tray
- Discord Rich Presence with album art and a live progress bar
- Last.fm scrobbling, connect once and forget about it
- Synced lyrics in a side panel, click a line to jump there
- Listen Together, synced rooms so you and a friend hear the same thing at the same time
- 8 themes, including Catppuccin, because obviously
- Gapless playback, volume normalization, shuffle, repeat, autoplay radio
- Your queue survives a restart
Free and open source, GPL. AppImage (self updating) or an rpm for Fedora, which is what I daily drive. No Flatpak or AUR yet, both are on the list. There's a Windows build too, and no macOS one yet.
Would really love for people to try it, and I'd genuinely like to hear what everyone thinks. ❤️
Site: https://simohypers.github.io/limusic/ Downloads: https://github.com/SimoHypers/limusic/releases/latest
Not affiliated with Google or YouTube, just a thing I made because I wanted it
If you view the first commit, you can see the
CLAUDE.md, so at least in part vibe-coded.Tbh all the vibe-coded apps look the same, and the UI has that vibe-coded style, so I'm not surprised.
AI use does not mean vibecoded
I didn't say it did, but also "vibe coding" is a fairly new term that does not have a strict consistent definition anyway.
I'm not sure how else to interpret your comment.. You found evidence of AI and concluded its at least partly vibe-coded. As for the definition, no I don't think its all that inconsistent. Feel free to look it up.
Semantics are defined by how a term is used, and people use the term to refer to AI generation of code in any capacity, as well as stricter definitions. The first commit is not just "evidence of AI", it's no code and just a markdown file instructing an LLM, which meets at least some definitions of vibe-coding.
Insisting "a word doesn't mean X, it means Y" doesn't make it so. Arguing about definitions can be on one of two premises: the word is in practice used to mean Y and not X, or it's useful to define the word to mean Y and not X. You've argued neither, just made an assertion.