

However gmail is a large, incredibly well known service, and many sites understand that the + on gmail specifically is for subaddresses and will deny using the same email with subaddresses different times.
Contrast that with just using dashes like Port87, and most systems don’t have anything made to parse for dashes, as it could then result in problems where an email service like Gmail, or any other provider out there, allows people to put dashes in their base email, and someone can effectively block someone else from signing up for a service by making a new account named theirname-1, signing up, then the service would think that theirname-1 is also owned by theirname, and block theirname from signing up later.
The + is a relatively well known standard for email subaddressing, but dashes are primarily used by people just inside their email addresses instead of a space, for example. Thus, most server side implementations will never be configured to understand dashes as indicating a label, specifically for your domain, they’ll just see a large volume of constantly created new emails, that act like a temporary email service, and assume you’re one.
This has the same problem as before, where you’re not large enough to justify being specially considered by login pages that will understand what your labels are, but are also not going to get to that scale if you get filtered out as a temporary email service.
I’m probably going to stop responding now, as I think that’s about all I can contribute, but I’d just say that if this is the exact mechanism by which you plan to implement subaddressing, make sure you’re frequently checking any widely used blocklists online for temporary email domains, because someone will probably end up submitting your domain there at some point based on the behavior of the service, and it’s incredibly hard to get off once you’re on. (and consider making a page on the site explaining why you’re not a temporary email service, like SimpleLogin has)
There’s only a few use cases where I’ve found I prefer it to doing things the hard way.
However, I try to avoid using it for anything that otherwise requires productive mental effort, because I find that I end up being a lot more informed and capable if I spend 5 minutes going through sites, learning about a topic, identifying wrong answers, and being able to put together better new queries in the first place, than I do if I ask a chatbot, even if it pulls from those same sources.
When you have a chatbot summarize or combine/condense information, you’ll always lose nuance and additional context, and very frequently that context will actually be helpful to your overall understanding. There’s also many cases where, for example, someone on a forum explains an issue a bit, and their profile has more related information on it that an LLM simply wouldn’t go for, only summarizing from their one response on that page. This can lead me down a rabbit hole that then leads me to finding other good sources. Maybe someone mentions that a particular site is helpful for what I’m looking for, and that then becomes something I use more frequently when I do searches for things, whereas an LLM would have just ignored that comment.