qupada

@qupada@kbin.social

• ⁨Comment⁩ on ⁨Teams apparently can't call when using Firefox⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  Fortunately, there's an extension that solves that: https://microsoftedge.microsoft.com/addons/detail/ajgodcbbfnpdbopgmfcgdbfhabbnilbp

• ⁨Comment⁩ on ⁨Do It Yourself⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Back when they were all the rage, one of my colleagues received one of those rubber horse masks in the mail at the office.

  Indeed, he had no memory of ordering it.

• ⁨Comment⁩ on ⁨Shitsoft Teams doesn't work on firefox⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I thought it might be sensible on Linux to use MS Edge for Teams (the PWA version).
  Nope, it's just as shit in Microsoft's own browser. There is apparently no saving it.

• ⁨Comment⁩ on ⁨Why don't laptops have proper low power states where useful stuff like downloads can run during sleep/with the lid closed?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  and the people who do still download, wouldn’t care about doing it while on battery

  Very much this; I've got a whole army of machines I can SSH into to launch a long-running download, which frequently additionaly cuts out a 2nd step of copying the file to where it needs to be after downloading it (a action which would normally cause additional battery usage on the laptop).

  And I thoroughly agree with you; I want the laptop to go to S3 sleep immediately when I shut the lid, and then pull it out of my bag a hours later with only a couple of percent of the battery consumed in the interim.

• ⁨Comment⁩ on ⁨Would the internet be significantly faster if there wasn't so much farming of metadata / cookies?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Worse still, a lot of "modern" designs don't even both including that trivial amount of content in the page, so if you've got a bad connection you get a page with some of the style and layout loaded, but nothing actually in it.

  I'm not really sure how we arrived at this point, it seems like use of lazy-loading universally makes things worse, but it's becoming more and more common.

  I've always vaguely assumed it's just a symptom of people having never tested in anything but their "perfect" local development environment; no low-throughput or high-latency connections, no packet loss, no nothing. When you're out here in the real world, on a marginal 4G connection - or frankly even just connecting to a server in another country - things get pretty grim.

  Somewhere along the way, it feels like someone just decided that pages often not loading at all was more acceptable than looking at a loading progress bar for even a second or two longer (but being largely guaranteed to have the whole page once you get there).

• ⁨Comment⁩ on ⁨Would the internet be significantly faster if there wasn't so much farming of metadata / cookies?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Worse still, a lot of "modern" designs don't even both including that trivial amount of content in the page, so if you've got a bad connection you get a page with some of the style and layout loaded, but nothing actually in it.

  I'm not really sure how we arrived at this point, it seems like use of lazy-loading universally makes things worse, but it's becoming more and more common.

  I've always vaguely assumed it's just a symptom of people having never tested in anything but their "perfect" local development environment; no low-throughput or high-latency connections, no packet loss, no nothing. When you're out here in the real world, on a marginal 4G connection - or frankly even just connecting to a server in another country - things get pretty grim.

  Somewhere along the way, it feels like someone just decided that pages often not loading at all was more acceptable than looking at a loading progress bar for even a second or two longer (but being largely guaranteed to have the whole page once you get there).