(Please correct me if I am wrong…)
Vanity addresses are popular in bitcoin, but difficulty rises exponentially with each character. Most people don't want crunch random numbers for 6 months. The solution to 3rd party key generation is split keys.
Essentially the addition of keys to get the desired final key.
Generate key X, give X public address to cloud provider, they search for key Y so that X + Y == YourVanityAddress, when found they send you private Y. Private X + Y is your vanity private key.
Vanity address generated by 3rd party in a trustless environment.
That said you could use an Amazon GPU instance for a handful of cents an hour and run scallion there.
facebook, scryptmail, one bitcoin exchange, one bitcoin walled, dozes on blogs and chans, there is GoG instance in Tor as well as GitLab.
When you have a very small subset of users who will go through the trouble of trying out Facebook's onion address, it is much easier to be successful with surveillance tools on that small sample.
The GNU Name System gets this sort of thing correct though.
This assumes that users aren't ignoring the address anyway. There is a near 100% success rate in tricking users into visiting fake URLs in laboratory conditions. While trying to explain my research to a tenured professor, she literally typed each domain I was spelling out into Firefox's search box instead of punching it in manually.
And for those who think Protonmail are the only service with a custom address, think again, because Facebook has one too: https://facebookcorewwwi.onion/
You can find a tonne more at this list:
https://github.com/chris-barry/darkweb-everywhere/tree/maste...
And staying on topic, Mailpile has their own .onion
https://raw.githubusercontent.com/chris-barry/darkweb-everyw...