[fterh]

No worries, thanks for the feedback (I appreciate all feedback whether positive or negative).

A catch-all email address is actually less complex to build and test, but there are a couple of reasons I chose to use this approach:

1. It seems that in the workflow you described, there is some work to be done in setting up an inbox filter/black-holing the email address too. In a way, my workflow simply shifts this work to the start?

2. I don't think it's laborious because I don't really need new email addresses that often. It's also really easy to generate a new email address imo - no logins or portals required, just email [e-mail] and you get a reply with an email address within seconds.

3. You're welcome to fork it and tweak it for personal use too if you want! :) I'd love that.

[mmcclure]

Thanks for the reply!

1. I don't really think your workflow shifts any work over the catch-all workflow, it simply adds another step. In my workflow I essentially already have that alias you create in your first step. Then, if that alias gets abused, both systems require shutting off that alias.

2. Yeah, that's definitely just a different usage pattern. I'm one of those folks that enjoys testing out different onboarding workflows, etc, so I'm constantly signing up for services, etc.

3. I'm quite happy with the alias approach, but best of luck with the project :)