Conversation
I think this has been the largest factor in my hesitation with these sorts of things in general, and I'm glad you are cognizant of it too. In a vacuum, I 100% believe that more options are better. No piece of software can ever cover everyone's workflows, but I like customization to the point that most can get what they want out of it. But like you say, it too often feels like everything ends up As this particular change stands, I think it's acceptable as is. But with the inevitability of wanting it to do more in the future, I very much welcome ideas on how to handle an ever increasing number of knobs to tweak. (After all, we all know what happens when you "give a mouse a cookie" haha!) |
|
I would also appreciate a reduction in the salt options, as they overlap somewhat. If each option were implemented separately instead of static settings, everyone could configure it themselves: These are sufficient in my opinion: |
3 participants
Hello,
hope you are doing well. I finally had a bit of free time again.
This PR should closes #36 and #38, where there are requests for a few different salt position options.
The new options allow the salt to be prefixed/affixed to a word without a separator, and inserted "as another word" (between words, or as first/last word) while using appropriate separators.
The new option in salt position:
Example generated passwords:
(numbers represent salt)
(
~is a separator)Notes:
AsSeparateWordOnce. I would prefer to insert it as another word into the array. But with the current setup, it is more trouble than it is worth. So I think this works just fine.