svde

Thanks for the feedback!

Regarding the issue I fully agree with the answer of luckylion.

Q1: Since it almost has to be used in combination with some sort of password manager, you could compare the hash with the service you signed up for. But that's a bit inconvenient. Since you receive a mail for each new signup, maybe set up a mail filter, that gathers all first mail to a hash in a dedicated folder. This way you can compare the sender with the first mail for specific hash when receiving new mails. This would have the benefit to have the data right inside your mail app of choice.

Q2: Just ported to firefox thanks to your suggestion: https://addons.mozilla.org/de/firefox/addon/mail-hash/

Op here.

Mail Hash is a little Chrome Extension to add a random string to an email address as an attempt prevent reusability for automated attacks in case a service get's hacked. Targeted attacks at specific addresses should be more difficult aswell, since an attacker would need to guess the random string you used for other services.

You can use plus addressing for providers that support it, e.g. your.name@gmail.com --> your.name+ha7s6@gmail.com

Or use a custom domain with catch-all filter, e.g. example.com --> ZpGM5rrfZ6@example.com

Code lives on GitHub[0] and the extension can be downloaded at the Chrome Web Store[1].

I'm happy about any kind of feedback.

[0]: https://github.com/jsvde/Mail-Hash [1]: https://chrome.google.com/webstore/detail/mail-hash/njjpbfib...

The license explainer is a very neat idea! I think I'll link to tldrlegal[1] for that. Bin and similar information, that can be extracted directly from the package.json without extra request will be provided at the top of the page soon. Just updated the no dependency message with your suggestion!

Thanks for your feedback!

[0]: https://tldrlegal.com

This looks exactly like what I was looking for. Thank you.

>Animation transition between pages is still being worked on

check out react-overdrive[1], which is also referenced in issue#88 but deserves to be mentioned here imo. The author provides an example[2] what overdrive looks like based on the instagram example[3] from next.js.

[1] https://github.com/berzniz/react-overdrive

[2] https://nextgram-overdrive.now.sh/

[3] https://nextgram.now.sh/