Oh no, not just my build server, Microsofts build server… Everyones’ Azure build server - (if you’re building on windows)

    • palordrolap@fedia.io
      261·
      6 days ago

      How about, I don’t know, not yanking the cord (or setting things up so the cord is yanked automatically) and pursuing the payment later?

      But then that could mean that someone might - even temporarily - get something for nothing, and they can’t be seen to promote anything even remotely similar to that.

      Perhaps this tiny company are so close to the knife edge that they can’t afford to allow it to happen. Must have constant revenue stream or else close up sho… wait, Micro-who?

    • Todd Bonzalez@lemm.ee
      243·
      6 days ago

      Imagine paying money for software designed to sabotage your business if you miss a license payment.

      • jdeath@lemm.ee
        1·
        2 days ago

        i am thinking this issue description is implying that EVERYONE using the windows build image was broken. MS probably had a hard coded license in the build image which expired. idk, could be reading it wrong

      • Carighan Maconar@lemmy.world
        78·
        6 days ago

        Uh… what do you think we do when a client doesn’t pay us for a while? We yank their access. That’s how services work, you get a few warnings that you really need to pay or you’ll lose access and then, well, you lose access.

      • IsThisAnAI@lemmy.world
        222·
        6 days ago

        Oh you mean like every commercial FoSS OS which will force you to wait or not receive certain security updates unless you are on a subscription?