Yeah that’s more or less how it works. You generate it deterministically every time.

what are the pros and cons?

Not really sure of the cons aside from the fact that you get significant “vendor”/algo lock-in. You need the exact same algo this app uses to get your password back out (good thing it’s GPL).

Do you get a different output from different variations of the same URL, like including a “/”.

Yeah an extra slash at the end means a whole new password. The “name” is not really a “URL” per se. It can be any string.

So for example “lemmy.dbzer0.com”, “[email protected]”, and “lemmy.dbzer0.com 2” are valid site names and will give different passwords.

That being said I could see omitting some special trailing chars, protocol strings etc.

What does saving the bookmark actually do, like pre-fill the URL field?

Basically every parameter of the password generator is codified into the URL. So bookmarking a URL allows you to load a page with prefilled data like:

• Special chars
• Length
• Revision number
• Algorithm
• etc

These parameters are all required to be the same each time you need to generate the password. So it can help you avoid filling these forms each time + act as a reminder of what you used.

Given that autofilling is supposed to be more secure than copy/pasting, is there some way to make this do that?

It will auto-fill your master passphrase but if you mean auto-filling your credentials into sites, it would need to be made into a browser plugin to do that.