3 ms·
Personally, I use a self devised algorithm for each service. In comes the service's name, out comes a password. An example of an algorithm could be the first t
by Oculus 13y ago
Personally, I use a self devised algorithm for each service. In comes the service's name, out comes a password.
An example of an algorithm could be the first two letters, the last two letters and place those around the name of the person who created the service. This is a poor and somewhat weak algorithm, but the main idea is given the service's name you are not only able to derive the password, but each service has a unique one.
- deletes 13y agoI tried that once, but it is hard to determine what the name is actually. Especially after you forget it and have to reconstruct it. Is it? = "Hacker News", "HackerNews", "Hacker news", "ycombinator", "news.ycombinator.com"... you get the idea. Even if you have a 100% way to determine the name. Then the main problem why this doesn't work, is that the name might get changed slightly and ruin your scheme. And you can't remember the password because you didn't visit the site for 4 months. Example: Hacker News -> News for Hackers, or the domain you used for name gets slightly changed. Then what?
- Oculus 13y agoI've yet to encounter a scenario where the name of the service changes. I guess in that case you could always use something like internet archives to see what the name was previously? The approach's success is in following a set of rules unquestionably and for all services. So for example for all multi-word services, you use camel case.