[torgard]

Yeah same. From the source code, the answer is a random 14-character string, generated on load:

    function randomPassword() {
        let letters = 'abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ';
        let digits = '0123456789';
        let punctuation = '!"#$%&\'()*+,-./:;<=>?@[\\]^_`{|}~';
        let s = letters.repeat(7) + digits.repeat(4) + punctuation.repeat(3);
        let length = 14;
        let res = Array.from({length}, (() => s[randomInt(s.length)])).join('');
        debugger; // どうぞ
        return res;
    }

[DonHopkins]

I wish it accepted a given password from a url query parameter, so this url would work:

https://rsk0315.github.io/playground/passwordle.html?passwor...

Or the way bikeshed.com lets you configure the color with the domain name, like:

https://bisque.bikeshed.com/

Then they could monetize it by selling gullible suckers NFTs of urls pointing to Passwordle games of their passwords.

[cobbal]

Even better would be to link to the hash of the password, then there would be no way to guess.

[DonHopkins]

The point is that most people gullible enough to buy NFTs won't care about having their password in the URL. Those ignorant suckers are the same ones who complain that the government should step in and enforce their precious decentralized Libertarian "ownership" of their ape jpeg when somebody "steals" it with the "Save as..." menu. They fall for NFT scams for the same reason they fall for hunter2 password scams.

[boothby]

I treated this the same way I started when solving absurdle, wordle, and hurdle: find the database, get crackin' on a decision tree. But, after estimating 1.2e17 possible passwords in the "database," it only feels fair to accept the invitation to use the debugger.