tiny-unique-id-generator
blame.email
| tiny-unique-id-generator | blame.email | |
|---|---|---|
| 1 | 8 | |
| 0 | 11 | |
| - | - | |
| 10.0 | 0.0 | |
| about 2 years ago | almost 2 years ago | |
| JavaScript | JavaScript | |
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tiny-unique-id-generator
blame.email
-
Stalwart mail server (self-hosted all-in-one mail server) now as an admin webui
https://blame.email/ is a website that does this. I wrote a Lua checker for rspamd that bypasses the spam filter if the address is "signed". I also have a bookmarklet that generates a signed address and inserts it into the current text field.
-
Email obfuscation: What still works in 2023?
While it doesn't stop spam, I have been using a catch-all email system for a while now.
The benefit is that I know where someone got my email from, and I can then try to figure out whether the place has been compromised, or whether they're selling my email, etc. And I can just blacklist that particular address forever as well.
Previously, I just did [email protected], but I've switched to something similar to blame.email [1].
This makes my emails look a little weirder, but it has stopped the weird looks I'd get when walking into a physical place, like my doctor, and telling them "Yeah, email me at @.com".
It also makes it less obvious that its effectively a throwaway email, particularly combined with my domain; it looks fitting. And since each address is salted and hashed, it pretty much eliminates the risk of someone successfullying trying to phish me by sending me an email to something like `[email protected]`.
Lastly, on my HN profile and elsewhere, I've got my "email", but despite them being unique, I still don't want to have to rotate it if it gets picked up by a spambot, so I've tried to do some plaintext simple "obfuscation" like in the article.
I went for
~АТ~ . -- with the "AT" being Cyrillic rather than Latin - I figure at least some will get tripped up by not being able to use purely English regex.So far, I have yet to receive any spam with that strategy. Maybe I'm lucky or just not getting indexed, or maybe it's working a little.
[1]: https://news.ycombinator.com/item?id=31820502 / https://blame.email/
-
FYI Namecheap is selling your e-mail or is compromised.
Just tossing this here for reference: https://blame.email/
- For anyone new getting into IT, avoid giving out your personal or work phone number as long as possible. As once you do your job will get much more annoying
-
How to use the Bitwarden username generator and why you should
id love to potentially also see something like https://blame.email/ implemented as an option for the above 2, so you can always work out the source.
-
blame.email - client-side one-way email generator
Next time I ping you I'll have it fully implemented at https://blame.email :)
What are some alternatives?
zeptoid - A tiny isomorphic fast function for generating a cryptographically random hex string.
uuid-readable - Generate Easy to Remember, Readable UUIDs, that are Shakespearean and Grammatically Correct Sentences 🥳
uuid-mongodb - 📇 Generates and parses MongoDB BSON UUIDs
urid - Generate Unique/Random ID. No dependency. Less than <1kb