Unfortunately the link you just provided just died.
If you're on Linux, your best bet is likely to be attaching to each renderer process and running `generate-core-file`. Unfortunately (and very annoyingly) chrome://cache stores HTTPS-encrypted data, which you would need to have previously exported SSLKEYLOGFILE to decrypt.
Alternatively, if you still have the tab open, CTRL+S :D
Regarding your point though, if the PSP is _completely laid open_ so we can understand how it works, can't we load our own firmware into the PSP and then be confident that that's what's running?
If you're on Linux, your best bet is likely to be attaching to each renderer process and running `generate-core-file`. Unfortunately (and very annoyingly) chrome://cache stores HTTPS-encrypted data, which you would need to have previously exported SSLKEYLOGFILE to decrypt.
Alternatively, if you still have the tab open, CTRL+S :D
Regarding your point though, if the PSP is _completely laid open_ so we can understand how it works, can't we load our own firmware into the PSP and then be confident that that's what's running?