Yeah and as long as we reduce our fossil fuels by 2015 climate change won’t be a problem.

I don’t kink shame unless they’re into snaps.

As for the “Sound Connect App” that’s unfortunately the core of the problem. That app doesn’t exist for Linux. If the hardware relies on that app to set up or manage profiles, it creates an unavoidable roadblock for desktop Linux users.

The app runs on your phone (Android or iOS), and then you use the phone to manage Bluetooth connections for the earbuds. IMO you shouldn’t need a second device, but I guess they just assume 99% of people are connecting to a smartphone.

It just seems to be a non-standard implementation from Sony that doesn’t play well with the standard Linux audio stack.

I think the issue is that the actual Bluetooth connection is obfuscated behind a proprietary connection to the app, and the app exposes the protocol.

I agree it’s a stupid implementation, prioritizing a UI for pairing over literally everything else, but you still might be able to get it to work. I’ve successfully paired my WF-1000XM4 earbuds with my EndeavourOS (KDE) desktop.

Drivers (other than your Bluetooth chipset) generally shouldn’t matter. AFAIK Bluetooth audio device protocol is generic.

How are you pairing the headphones? Are you adding your PC as a device using the Sound Connect App? I have different SONY earbuds, but they can pair with 2 different devices and switch between them with the app. Perhaps they still have another device (like a phone) selected for output?

I’m getting an HTTP 522 from that link. What’s Polyproto?

Also, is there a reason you’re not considering Matrix?

This seems like a cool project. I especially love the UI’s similarity to Discord, but it still has a long road ahead to be a viable chat platform IMO.

I’ve been periodically checking in with Revolt Stoat for about a year now, and personally, the two things that I’m waiting for are:

1. Voice chat - It seems like this is coming, but they had to clean up a bunch or tech debt first
2. Federation - Self-hosted chat is great, but not being able to talk to other servers is incredibly limiting for a social tool. AFAIK they’re not planning on implementing this. This is likely a deal-breaker for a lot of folks.

I’m currently running Matrix synapse, and while matrix is kinda a messy ecosystem, it’s really hard to compete with its maturity and adoption in the FOSS / Self-Hosted space.

Also, not super important, but this blog post reads like it’s AI generated.

Import our Postman library. ❌
Clone our curl repo. ✅

A house that needs the internet to function is not a “smart home”, it’s a “dependent home”.

A frustrating number of devices rely on cloud connectivity for astoundingly rudimentary tasks.

I was once at a friend’s house for a game night and it was really cold; everyone was under blankets. I asked to turn up the heat and they said, “The internet is down, so the heat doesn’t work.” 🤯

How could we tell you about an IP inside your own network? Look at the host using that IP and see what’s running on it.

Ew.

That’s good, it means you’re on the right track.

There is a mind-blowing amount of variety on both TikTok and YouTube. Just because these “someones” to which you refer are posting brainrot garbage doesn’t mean the entire platform is like that.

I really hope this was just a joke.

In that case, why self-host? A cloud-based solution would accomplish this very easily.

If avoiding downtime is your number one priority and you’re willing to take on a lot of complexity to achieve it, then Kubernetes is probably the way to go. There are various chat platforms that can be distributed, but keeping a game server state synced between nodes isn’t an easy task. There’s a reason most multiplayer games are instanced.

I do find it a little odd that you’re so concerned about uptime with a casual gaming server, but to each their own.

Total time delta 🐱

You jest, but I’m currently running 13 containers on one of my Pi’s and using ~34% of the RAM.

IMO containers should be fairly small. If they’re too large, it’s probably time to look into breaking up that app into micro-services.

I guess you took “friction” in the title literally.