Yeah, I’m not fond of how many open-source and homelab projects are starting to proudly wear the fact they’re just vibe-coded AI slop poured into a trenchcoat, but at least their declaration of the fact is better than pretending they did it themselves.

Amass was one of the listed projects under the “New Software” section of the post. It has already changed project name to Assistant-to-the-Music.

Amass, the Android client for Music Assistant, has rebranded to “Assistant to the Music” since this was written.

A reddit user pointed out the previous Amass logo looked like it spelled “All Ass”

I use this custom UI called uosc with MPV and its pretty decent.

Definitely agree that mpv isn’t a jellyfin replacement though.

Would you be willing to share your config?

deleted by creator

I’m not doing this for approval.

Okay. Go away and do it then.

Yeah, the Forgejo documentation was dreadful when I last looked, it really showed its origin as a Gitea replacement for people already using (and understanding) Gitea.

That’s cool. Any reason why you went with a self-hosted GitHub runner over making the full jump to a self-hosted Gitea instance + runner?

did you find any solution for this?

This one is edgy.

• Arch Linux announcement
• Ubuntu discourse announcement
• RedHat/Fedora security alert
• Debian security announcement

I tried both Lidarr and Beets before, but their automation tended to pick matches with a “eh, close enough” attitude, so I just decided I’d do it properly myself.

I tag metadata on everything with MusicBrainz Picard, and then store it in a /{Album Artist}/{Album}/{Track} hierarchy.

Dead Products (Death Date)

• Mentioned in article:
  • Google Podcasts (Later in 2024)
  • YouTube Premium Lite (Oct 2023)
  • Gmail’s “Basic HTML” view (Jan 2024)
• Not mentioned in article:
  • Google Optimize (30 Sept 2023)
  • Google Domains (30 Sept 2023)

If you’ve never heard of this, that’s because it got a very small rollout to only Belgium, Denmark, Finland, Luxembourg, the Netherlands, Norway, and Sweden.

This is in relation to YouTube Premium Lite, and not, as this shortened article implies, Google Podcasts.

I think it’s getting down-voted purely because OP’s title is essentially “mIcRo$oFt bAd!” instead of describing the issue. It’s not getting down-voted anywhere else this article was cross-posted to, where they used the article’s actual title.

VS Code has an optional feature that can allow remote access, which could be [used/abused] to [access/breach] otherwise secure networks. Because the executable is signed by Microsoft, it won’t be flagged as malicious by antivirus/malware scanners even though it could easily be used as such. The article shows the steps the author attempted to detect and block this tunnel functionality, with limited success.

I swapped to Chrome a long time ago, probably around Firefox 7 or so, and never really looked back. I didn’t really have an issue with being part of the Google ecosystem, and they were still in their embrace phase. It’s been a while.

I have both browsers installed at the moment and under Linux/Wayland/Nvidia, Firefox definitely performs miles better (actual HW acceleration!) but Chrome still feels more practical to use, in my opinion. I think my main hang-up is that Chrome’s “Tab Groups” suit my approach to web browsing better than Firefox “Tab Containers”, even factoring in how Multi-Account Containers can make them more useful.