blame.email VS riot

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.

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/

Just tossing this here for reference: https://blame.email/

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.

Next time I ping you I'll have it fully implemented at https://blame.email :)

These articles form a series focusing on RiotJS paired with BeerCSS, designed to guide you through creating components and mastering best practices for building production-ready applications. I assume you have a foundational understanding of Riot; however, feel free to refer to the documentation if needed: https://riot.js.org/documentation/

This article covers how to create an Riot input component, using the Material Design CSS BeerCSS. Before starting, make sure you have a base application running, or read my previous article Setup Riot + BeerCSS + Vite.

However, Riot is my first choice when creating a front-end, here is why:

Riot.js is designed to be lightweight and easy to learn, making it a good choice for developers who are familiar with HTML and JavaScript — without requiring them to learn the rigors of coding with a specific framework. Riot.js emphasizes simplicity, performance, and modularity, its ecosystem allows for easy integration of third-party libraries and components, making it suitable for both small-scale and large-scale projects.

how about getting a hold of your sanity and allowing yourself a few hours to learn https://riot.js.org/ - almost no learning curve, only pure awesomeness. even if you won't use it in the enterprise (because policies, bla bla), it is still worth knowing things can be done differently - in a good way.

Riot.js prides itself as a light and simple UI library that helps developers hit the ground running when creating elegant UIs for their applications.

Thanks! Glad you like it. I'm the original author of Riot (https://riot.js.org/) so that's the style of frontend development I'm most comfortable with. We're using our own flavour of the library, which has the original super-mimimalistic feel on it.