Issues creating permalinks to playground notebooks

One issue: creating a permalink for this notebook fails. It does not seem to do with the notebook length, since even after deleting all cells permalink creation fails, the next-router-state-tree header being extremely large.

Here's the webasm link in a github gist:
https://gist.github.com/rjbudzynski/7fc7b46e2dfe8311a490fbbfbadc61dc

On the other hand, I am not having problems creating permalinks to long notebooks on Ubuntu, Google Chrome.

I copied the code from your gist and created a new notebook from it on the playground. And the permalink worked just fine: https://marimo.app/l/6z1mo2

Another issue is that old is.gd links are no longer routing to the correct notebook, like this one: Wonky indeed.

"For another example, look at https://is.gd/X512K1 - when I open this shortcut, it displays a different notebook than that link was created for. One that I made after that is.gd shortcut was created. I wonder what you will see."

when you see it "opening another notebook". it means the notebook code is either invalid or failed to load. In which case we load the notebook from your localstorage

I think the issue is that the link used to work but no longer does

that could make sense. possibly an upgrade to nextjs

That sort of makes sense. But then there's the question of what caused the (correct) notebook's code to become invalid.

BTW sorry about spreading the discussion, I was just a little jarred by the effect.

What is the content of the first cell of the notebook you get by opening that gist? Or the permalink (I assume it's the same)?

We can reproduce the issue reliably. It is related to landing on a page with a long URL — so when landing on a page with a long WASM link that encodes the notebook code (not permalink), subsequent operations fail due to internals of the frontend framework we are using. We're not sure how to get around this, so we've opened an issue with NextJS: https://github.com/vercel/next.js/discussions/75121