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

you are viewing a single comment's thread
view the rest of the comments
[–] 42 points 1 day ago* (2 children)

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

  • source
  • parent
  • hideshow 4 child comments
  • [–] 16 points 1 day ago (2 children)

    Does this "dev" even know vibe coded slop can't be licensed?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 9 hours ago

    According to the U.S. Copyright Office, it absolutely can, but it depends on how much control the user exerts on the final product.

    If a single prompt was used and they copy pasted the entire thing, then yes, as you have said, it is not copyrightable.

    However, if multiple prompts were used and the end result is compiled/arranged with enough direction by the end user, then it can be copyrighted by compilation.

    Generating content with AI is often an initial or intermediate step, and human authorship may be added in the final product. As explained in the AI Registration Guidance, “a human may select or arrange AI-generated material in a sufficiently creative way that ‘the resulting work as a whole constitutes an original work of authorship.’”¹²⁶ A human may also “modify material originally generated by AI technology to such a degree that the modifications meet the standard for copyright protection.”¹²⁷

    As several commenters noted, human authors should be able to claim copyright if they select, coordinate, and arrange AI-generated material in a creative way.¹²⁸ This would provide protection for the output as a whole (although not the AI-generated material alone).¹²⁹ A relatively common scenario in registration applications is the combination of human-authored text with AI-generated images. In one early case, for instance, the Office found that the selection and arrangement of AI-generated images with human-authored text in a comic book were protectable as a compilation.

    https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf

  • source
  • parent
  • [–] 3 points 15 hours ago (1 child)

    According to who? Was there a legislation or legal case? In which country?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 13 hours ago (1 child)

    The US copyright office for one

    https://www.skadden.com/insights/publications/2025/02/copyright-office-publishes-report

    Human authorship is a bedrock of copyrightability, and thus works entirely generated by AI are not copyrightable. (...) Where a work includes both human and AI-generated content, only the human contributions are potentially copyrightable.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 9 hours ago*

    That article completely practically skips over the section in the report that says that copyright can be applied by compilation to an overall work. See section II - F: "Modifying or Arranging AI-Generated Content"

    Or you can also just skip to the conclusion of the actual report itself:

    As described above, in many circumstances these outputs will be copyrightable in whole or in part—where AI is used as a tool, and where a human has been able to determine the expressive elements they contain. Prompts alone, however, at this stage are unlikely to satisfy those requirements.
    https://www.copyright.gov/ai/Copyright-and-Artificial-Intelligence-Part-2-Copyrightability-Report.pdf

    Edit: The article you linked does mention that the works can be copyrighted as a whole, but it does not mention this in the conclusion.

  • source
  • parent
  • [–] -3 points 1 day ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 17 points 17 hours ago* (2 children)

    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.

  • source
  • parent
  • hideshow 4 child comments