same, but hopefully not for too much longer! also, that hack is awesome...

I'm at eli[at]desmos.com if we can help with the update. It's worth it, I hope - lots of improvements and no extra cost. More here: www.desmos.com/api/changelog

Quick follow up here - we updated the message to be less garish (standard console.warn now). Very sorry + grateful for bringing that to my attention. We also should only be showing this if 3 or more major releases (so 3+ years) out of date. please let me know if it's showing when it shouldn't!

Again though, frustration heard. We always try to keep in close contact with partners to make sure we don't get out of sync like this, and it sounds like we missed the mark here. I'm eli[at]desmos.com if I can help with this (or anything else, at any point).

(3) we only do this console if it's more than a year out of date (fwiw: our contracts always include a commitment to upgrade within a few months of each release. We don't enforce that, obviously, but it is a commitment for the above reasons)

(2) One reason for all of this is that we're constantly fixing small browser-compatibility things, improving accessibility, etc, and our team is way too small to support backports to arbitrarily old API versions. We commit to support the current and one prior, but further back than that is tough.

A few small details that might help: (1) updating should just be switching a v1.* to v1.11 somewhere. We work really hard at backwards compatibility so it should take no work past that, and there's no cost to upgrade to our latest version.

So sorry about the nuisance here, Chris! Which company are you with? I'm happy to help update however I can, and feedback received that a console warning feels unfriendly (we didn't want anything user facing).

Naomi Bethune (an incredible up-and-coming writing fellow at @prospect.org), wrote about this last year: prospect.org/2025/06/24/2...

If you want to help, these funds will directly help families in Minneapolis pay rent. bit.ly/singMSPrent

I love this broken calc puzzles idea 😍. I think that turning off functions should be kind of straightforward, but turning off numbers and operations could be tricky... I imagine if "2" is broken you couldn't type "12" also, but what about if * is broken, should we break implicit multiplication too?

We've been talking about this one! Very hard to implement the general case in a way that'll work performantly with the rest of our system, but we're going to see what we can do.

wow I've never seen it presented like that. that's gorgeous.

Love this idea! It's a tricky one to do in general because to render arbitrary opacities can be a performance nightmare (the leading technique, depth peeling, can be incredibly computationally intensive with many layers of low opacity surfaces). But we're working on it :)

There was so much confusion of people thinking that Desmos was all part of Amplify, sending us support requests about parts that we don't have any control over etc, and it was actually making things kind of hard for Desmos Studio (and I imagine for Amplify as well on the other side)

I wasn't involved in that decision, but one benefit is that it's now so much clearer which parts are Desmos (e.g. the calculators and everything else at desmos.com) and which parts are Amplify (e.g. activity builder etc, now at classroom.amplify.com)

not sure why it's suggesting those... the syntax for domain restrictions in Desmos is { condition }, e.g.: www.desmos.com/calculator/j...

Fun fact: Desmos was _not_ bought by Amplify! We sold our curriculum business to Amplify, but Desmos Studio PBC (which runs the calculators) is separate. See more here: blog.desmos.com/articles/des...