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

  • db2@lemmy.world
    442·
    18 days ago

    What part, if any, does “AI” have in the development or use of this?

    • Chloé 🥕@lemmy.blahaj.zone
      344·
      18 days ago

      from the gitignore:

      /.agents/
/.claude/
/CLAUDE.md
/PHASE1-PROMPT.md
/RELEASING.md
/skills-lock.json
/plans

      so probably quite a bit lmao

      and from a brand-new account too. this is slop, people

      • db2@lemmy.world
        162·
        18 days ago

        Does this “dev” even know vibe coded slop can’t be licensed?

      • pineapple@lemmy.mlEnglish
        1111·
        18 days ago

        Just because AI was used in the development process doesn’t mean it is bad. Doesn’t mean it’s good either but you can’t just ignore it because AI had something to do with the process. Things being made by humans doesn’t make it good either people can write really bad code.

        • JustEnoughDucks@slrpnk.net
          16·
          18 days ago

          I think it is the other evidence that it is vibe coded

          • Brand new account
          • Dev only responds to non-technical or feel-good comments
          • other commenters have pointed to AI teltale vibe coding syntax signs in many of the files
          • Claude extra files in early commits and changing gitignores to do it.

          Advertised Vibe coded projects absolutely are by default bad and here is why:

          • Developers do not understand what they have built, so can’t debug it beyond “Claude, fix this”
          • Vibe coded projects are easy-come, easy-go very often abandoned (73% of the vibe projects on flathub, and those are the people who thought far enough to decide putting it on flathub was worth it)
          • developers can’t answer any questions on security when the app will be handling credentials, be hosted on a server, or attach to some sort of live service -> absolutely gaping security hole that you just have to cross you fingers that Claude didn’t do another “oops, you are completely right to push back,1500 common attack vectors were left open and you are now part of a CSAM botnet, do you want me to fix it?”

          If someone wants to make small scripts, one-off test firmware for a home project, writing test cases, design reviews, boilerplates, etc… Are arguably good usecases.

          Vibe coding an ongoing software service is almost always a hard no-go and statistically will be abandoned and unupdated, leading to even more security and usability issues.

          • pineapple@lemmy.mlEnglish
            1·
            17 days ago

            I think your right it is indeed vibe coded, and vibe code does mean it’s bad by default. If it’s made using AI assistance and a developer that knows what there doing is checking over what the AI writes, then it can be fine. But this person advertised they made it using there very own vibe coded vibe coding software!.

    • Richard@lemmy.world
      24·
      18 days ago

      I would say a great part of this code was at least “AI touched”. There are em dashes in the rust scripts, in the markdowns, in the commit messeges. @Simohypers@lemmy.world - disclose your stuff man! people should know what they are putting on their computers

    • communism@lemmy.ml
      142·
      18 days ago

      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.

        • communism@lemmy.ml
          62·
          18 days ago

          I didn’t say it did, but also “vibe coding” is a fairly new term that does not have a strict consistent definition anyway.

          • Zeoic@lemmy.worldEnglish
            28·
            18 days ago

            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.

            • communism@lemmy.ml
              2·
              18 days ago

              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.