I’ve been using Pipewire for a while, it was great because I could use my Bluetooth headset with a better audio Codec than in Pulseaudio. Unfortunately, my headset stopped working one day suddenly with Pipewire. (maybe after a dist-upgrade?) No amount of disconnecting, unbonding etc. would work. Went back to Pulseaudio as a sound server. Sad.

Neither Pulseaudio nor Pipewire remember to use by screen speakers (hdmi) as default, though. It always switches back to the internal sound card.

Oh my god, the whiskers! They’re fantastic!

well acshully…

I can imagine this could happen if sites change the implementation, e.g. their password hashing algorithm, in a way that require a password reset. (e.g. the site still used md5 or sha1 for password hashing). They won’t allow login with the broken hash. But they still check if the new password is the old one, since the old one could be compromised.

Oh? Another embedded programmer? This behavior pains me as well.