I saw it yes but I am more of a “applying to 50 job places with 50 unique aliases” kind of person especially when companies consider you as cannon fodder (and MySudo doesn’t allow for that unfortunately). 
Both sentences are separate here and not related. 
Was mostly talking about the idea of adding a prefix in general and not specifically to the doctor situation.
As for my recommendation of not giving too many documents to doctors it comes from that news where a girl couldn’t opt out from his doctor oversharing while she explicitly said no.
Anyway, not saying it’s prio #1 but mostly recommending to not give away your entire life to doctor that might not care/leak it (especially if totally unrelated to a given illness).
Maybe it’s me being bitter with dutch doctors treating people here like shit idk, more distrustful as of recently for sure.
Privacy is more prio in this case yes, you misunderstood the quoted sentence from me in your response. 
For second, I do agree but somebody new to aliasing might not know better.
Anyway, not sure if it is fitting to set something custom by yourself, I personally always leave it with a random word because it doesn’t matter anyway.
For third, I just thought it would be more confusing than a random word, that’s all.
Not a concern in itself, more of a QoL for everybody to not bother with figuring out something on the go and let the random generator handle it.
You are anonymous because you don’t subscribe to a newsletter with hi@kissu.io but rather cute.sunflower32@addy.io and there is no way to trace that subscription to me directly.
Doesn’t apply to public facing accounts like a Facebook but it’s still fine and an alias can still be used there.
At least, this is how I do it for things where I don’t want my domain to be tied to any company/service. Otherwise, I can also use a regular conference@kissu.io or alike.
Given my previous paragraph, it makes sense from an anonymity POV.
If you want to build a business brand identity, sure go on and use a catch-all on a domain name.
Both are very different use cases.
Moreover, even if a catch-all is cool, you don’t really need an aliasing service for that, especially if people can just spam with gibbeish@guidesmail.com or hellothere@guidesmail.com and that all of those will land into your emailbox. This is (personally) the last thing I wanna have because you can’t really stop it no more after (and don’t recommend blocking with a regex later on
).
It comes down to need/preference tho, nothing wrong with that approach. 
But even if I don’t want to be anonymous, I honestly don’t want to have to figure out something random like facebook@guidesmail.com, I just use a random thing to keep it simple.
I’ll just add a quick description on it down the road when I have some spare time, Addy makes it very nice with its UI unlike SL…
I don’t really see the need to have a persistent account in case of a shared alias (ending in *.addy.io).
In case of a personal domain name, why not.
My personal approach is to never give anything personal tied to my domain name.
I communicate with a freelance client using a random-generated word from SL, they never had any issue with that, they don’t even care.
And I even convinced them to move to Signal to avoid any passwords to be sent in plaintext.
Works for me just right.
There are very rare cases that I could see justifying using a custom domain while sending an email somewhere tbh. But that’s my personal approach as of today (not interacting with humans no more by email, just using it for notifications/newsletters/etc) since otherwise sensitive info will leak.
Email’s UX is quite awful to begin with anyway.
I do that on my email client’s side already yes as mentioned here thanks to folders, filters and labels.
I mostly just add the alias manually to a filter, don’t want to risk it with a regex pattern. Also I don’t have 60 different places that I shop from anyway, trying to be more mindful of my footprint. 