[saintfire]

I solve this problem the exact same way using emails.

e.g. [e-mail], [e-mail], [e-mail]

RelayBeam essentially flipped the email address to make the domain into the username. Except, it seems less robust.

In an example it says John is a doctor and uses the john@hospital and john@home.

Incidentally John is a popular name. I don't really trust JohnK1984@hospital over the email equivalent [e-mail]

The hospital can also have an info@..., support@..., noreply@... How does a business do that with relaybeam? It's going to be hard to have work related comms on a system that is managed by the employee.

[supritgandhi]

Hi, thanks for your comment!

You have exactly pointed out why I am building RelayBeam. You mentioned that you create multiple emails for different purpose, with RelayBeam you don't need to create multiple emails.

Now for naming, I can easily create a verification service, where certain port addresses can get verified, and if the port address gets verified, I can just share 'Verified' badge next to port address, and this badge will have all the details like which organization is this person related and so on.

And once you have the port address, you can save it to your address book with any name you feel comfortable. (Will be developing this address book feature)

Do let me know what other ideas do you have to solve this problem? Let's chat!

[vidarh]

I don't need to create multiple emails. I have infinite e-mails:

If you e-mail vidar+[any string]@hokstad.com it works, and I can filter that however I want.

That has worked with multiple providers for 25+ years (both Gmail and Fastmail supports this; my own e-mail service used to support it back in the day, and if there was a corresponding folder it'd deliver straight to that folder), and doesn't require me to explain a new service to people.