this post was submitted on 23 May 2026
58 points (96.8% liked)

Selfhosted

59435 readers
947 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

For the past few years I’ve been building and maintaining website/blog at www.pragmaticcoding.ca. It has mostly about programming, and more specifically it’s ended up having a lot of content about JavaFX with Kotlin.
Lately, I’ve been spending all of my time building out my own homelab and self-hosting the services that I need. I’ve got a little stack of M910Q’s running in a Proxmox cluster with an HP T740 running OPNSense. One of my big successes so far has been to replace my Google Home devices streaming music all over the house with a SnapCast network using RaspberryPi Zeros as the streaming clients. I've been working on documenting how to do this, and the result is a three part series that explains what SnapCast is, how it works and how to combine it with Mopidy to stream music around the house. I have to admit that this one got away from me. It was all one article until I noticed that Jekyll was estimating it at oven 1/2 hour to read, which is way, way too long. So it became three parts, which also gives me the opportunity to release it over time, and make sure that each part is nice and clean before I post it live. Part I is an introduction to SnapCast and explains how it works and how to set up a SnapCast server in Proxmox.
If you're interested, take a read and let me know what you think.

you are viewing a single comment's thread
view the rest of the comments
[–] Cyber@feddit.uk 1 points 16 hours ago (2 children)

Ooh, didn't know about this one. Have you used it?

This seems like an end to Snapcast: https://github.com/orgs/music-assistant/discussions/3883

[–] fonix232@fedia.io 2 points 15 hours ago

I am using it on a handful of devices (mainly voice interfaces), and it's quite seamless, even in the beta stage.

Not up to Sonos level controls yet, but it's getting there slowly. Music Assistant is gaining a lot of UX improvements recently, so it will be soon a viable alternative to not just SnapCast but Sonos too.

[–] HamsterRage@lemmy.ca 1 points 15 hours ago

Yes, I saw that comment. I wasn't sure what "But... it has so many downsides...." meant, and the comment doesn't clarify.

To me, the big question is how the "improvements" they are going to make would my installation better. I suspect that most of the improvements are ones that allow them to make Music Assistant better, or allow them to add tighter integration with Music Assistant.

As far as I know, they haven't rolled it out yet. But that thread is almost a year old now.

I would be interested to see what they've done.