This version -- where a short random string somehow carries the necessary information, rather than encoding it directly in the URL -- requires using a database to map that short random string to the relevant information. We could go that way in the future, but we don't believe the extra implementation and deployment complexity is worth it to give people an easier-to-copy URL. Obviously we can revisit that idea in the future, but this stateless system carries a lot of value for us right now, so we plan to keep the JWK essentially as-is.