I don't remember ever having seen this before. It appears when you add '?debugProgressUpdates' to the end of your desmos url and type in a function that takes a long time to load. The example shown in the video: http://www.desmos.com/calculator/trjxkyj468?debugProgressUpdates
LINK: https://www.desmos.com/calculator/jdenpfd5sd
Winner of Day 1: u/Desmos-Girl
This is Day 1 of a little challange I set up, inspired by u/Desmos-Girl 's recent post. The goal is very simple: Get all the given errors. I try to make the challenge harder every day. Have fun :)
LINK: https://www.desmos.com/calculator/caygjto58p
btw: independently of me, u/Mandelbrot4207 just posted a list of many many errors and how to get them. Please don't cheat, try for yourself
I made a graph to compute the nth prime number using an advanced prime counting algorithm. While the natural bound set by desmos list limit is roughly n=5.762*10^6 , I accomplished to compute the 10 millionth prime in 450-500 ms, using the "godmode script" to extend the bound. If you want to understand the algorithm: Link