Just 55 minutes ago as I’m typing this, I was in the middle of trying to start a therapy session with my therapist. And, the link she gave me worked, it detected my webcam and seemingly the microphone. I had done a test 30 minutes prior to make sure things were working.

And by the time therapy started, the video worked, the microphone didn’t. So I went into system settings, verified that Google Chrome was pointed directly to my headset and the webcam, no cross-interfering with mics and audio. Went into Chrome itself, verified to settings that they were set to point exactly as to where they should be, correspondingly.

This thrust me into a 15 minute infuriating experience where, rebooting the browser and rebooting the machine now seemed to have made it so the site suddenly couldn’t fucking detect the webcam and microphone. For reasons, I don’t fucking know.

We had to do our session through my phone via Google Voice.

So the point of the matter is, is that shit decided to stop fucking working for WHATEVER reason, despite it working fine previously.

Fucking garbage. I destroyed the webcam out of frustration and filed an angry ticket to the site operator about how their fucking site couldn’t be bothered to detect my equipment after that.

  • pyrinix@kbin.melroy.orgOP
    4·
    3 days ago

    Windows 8 being released as it was, was the death knoll period for how things are treated based on what platform. It was obvious where the focus shifted. Since then, websites started being designed with mobile in mind, that barely worked. We’re having all of these dumb virtual services that work optimally - on phone. We have apps that would’ve been great to also have desktop only work on - you guessed it - phones.

    Programs are now called Apps. I think troubleshooting on mobile is perhaps one of the most frustrating and hopeless experiences one can have. When something just breaks, it could very well be anything and your phone is faster to being obsolete than your desktop would.

    Where the hell did we go wrong?