A hard-coded IV with AES-GCM is bad only if you're encrypting content with the same key. Since you're deriving keys via a password, that would mean that two Li

A hard-coded IV with AES-GCM is bad only if you're encrypting content with the same key. Since you're deriving keys via a password, that would mean that two Link-Lock URL's protected with the same password _and_ using the same hard-coded IV would be vulnerable. It's likely an infeasible attack, but definitely worth giving a warning to those who really want to cut back on those 20-25 characters. Though since the URL fragment has _encrypted_ content, I think the users should understand up-front that the URL's will be long; it's impossible not to.