

They said this in the linked blog post:
A while ago, we discovered a way to scrape Spotify at scale.
Seems like reason enough to choose to scrape Spotify to me.


They said this in the linked blog post:
A while ago, we discovered a way to scrape Spotify at scale.
Seems like reason enough to choose to scrape Spotify to me.
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.


When I tried this, it just gave me a vague error code when trying to log in.
Would you be willing to share your config?


deleted by creator
I just seen a post from the Arch Linux Fosstodon account explaining that it’s down “due to cloud node outage” and not related to the ongoing waves of DDoS they’ve been dealing with.


I’ve had no issues with Dash to Dock, this looks more like an ArcMenu issue to me based on your screenshot.
In the description for ArcMenu they say:
Requires GMenu package:
- Depending on your distro you may need to install ‘gir1.2-gmenu-3.0’, ‘gnome-menus’, or ‘libgnome-menu-3-0’
Have you got that dependency covered?
What other extensions do you have installed? What versions of Ubuntu and GNOME are you using?


I’m not doing this for approval.
Okay. Go away and do it then.
My monitors.xml has two <configuration> blocks, with the only real difference being that one has <layoutmode>physical</layoutmode> and the second has <layoutmode>logical</layoutmode>. I don’t really think that’d be the issue here though, because if the dummy plug is listed as disabled it shouldn’t be trying to use it anyway…?
I think you’re right in reporting it to the GDM repo, at a minimum someone there will know where to point you towards figuring this out. Maybe the GNOME Mutter repo might be a related stop for this too, seeing that’s the part generating the monitors.xml…
The things that are supposed to be simple are always the bits that suck the most!
Yeah, seems like it should just be working…
You’ve probably already got this covered, but when you created your user monitors.xml config, did you have the dummy plug connected and disabled?
Maybe the config:
When you copy over your monitor config, are you correcting the ownership/permissions?
The little scriptlet I made to combat a previous nvidia/wayland multi-monitor headache boils down to:
sudo cp $HOME/.config/monitors.xml /var/lib/gdm/.config/
sudo chown gdm:gdm /var/lib/gdm/.config/monitors.xml
Maybe double check if GDM is ignoring wayland as well, I’ve definitely had that happen in the past too.


Yeah, this is probably what OP noticed.
Adwaita Sans is a tweaked version of Inter (the main change was to make lowercase I and L look less similar, IIRC) and then Adwaita Mono is basically Iosevka tweaked to match with Inter.
I use Tauon Music Box on Linux, I think it’s pretty decent, but it is kinda playlist focused.


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?
Maybe Linux just isn’t for you, and that’s okay. Go use Windows or Mac and enjoy your “just works” setup and lack of involuntary learning.
An alternate world where where BOMDAS failed us all.