• paraphrand@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      1
      ·
      edit-2
      2 days ago

      Well, the point here is the deception. So, if you can find a similar link from the past from Microsoft…

    • Meron35@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      Copilot was uniquely awful at this, because up to until literally days before the switch to usage based billing there was no way for people to track token usage, despite repeated calls from the community.

      Microsoft only added a billing “projection” feature on the admin page that was meant to download a spreadsheet (which straight up didn’t work for most people) less than a week before the new billing structure.

        • Meron35@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          17 hours ago

          It was too good to be true. Microsoft had to implement additional 5 hour and week usage limits to cope with demand.

          The problem was, for the entire history of copilot, there was literally no way to even check these usage limits. All usage counted towards these limits, even those with a 0x multiplier that didn’t consume premium requests.

          It was so bad that many people couldn’t even use the premium requests they paid for the month. The only around it was to switch to auto model routing, which would tend to route to lower quality models.