[supritgandhi]

Hi, I'll try to explain it as follows:

> People switch between multiple apps and channel for different purpose, ports can help to distinguish messages based on context and purpose.

> Having different types of discussion in handful of channels makes it difficult to track important messages, with multiple ports you can just focus on the important ones and ignore others.

> Users generally use apps like Slack/MS Teams for internal communication and prefer email for external communication. RelayBeam can be used for both the purposes easily.

> Again using ports, this can simplify the information management, because users can search for information in the relevant port.

> Generally email addresses are available on many sales directories websites. And your work related emails can be searched through such directories. Using different ports, you can just display certain ports publicly, and even if you don't make any of your ports publicly available, then I don't think it would be easily discovered, which should solve the spam problem to some extent.

Let me know if you'd like to know more on any of the above.

[marcus_holmes]

Thanks for the reply :)

I use the "[e-mail]" trick to filter my email. That feels like the same approach as you're describing for ports. Is it? How are ports better?

The Slack vs email thing is not because email is lacking, in particular, but that chat feels more immediate while email feels more professional and permanent. How are you going to make RelayBeam feel both professional/permanent and immediate?

I still don't see how it solves spam, though. My email address is sold, by services that I legitimately signed up for, to shitty marketing companies who then spam me. How are you going to stop the same thing happening for ports?

But hey, good luck with it. Hope it works :)

[supritgandhi]

Hi,

Regarding, [e-mail] - Yes, that is one of the feature I am trying to improve, given many people who are not that comfortable with email might find it difficult to configure it.

And for spam, a considerable amount of spam messages are automated using different tools or platforms. Sending automated messages won't be possible through RelayBeam, because marketing companies won't have any tools or APIs to do so.

This should solve the spam issue to a large extent.

Thanks for your comment!

Feel free to ask if you have any questions!

[vidarh]

> might find it difficult to configure it.

There is nothing to configure. If you want to filter it into folders, then, sure. That is an idea for a feature for e-mail clients, or an e-mail provider (*), not for a separate communications services.

> Sending automated messages won't be possible through RelayBeam, because marketing companies won't have any tools or APIs to do so.

That makes it a total non-starter, because a lot of the messages I use filters to organise are automated messages I want and/or need to receive. So now I then still need to hold onto my e-mail because the proprietary platform you're trying to push is trying to tell me how and who can and can't message me.

To me, that you can control this means it's not something I'll consider a viable option.

(*) I used to run an e-mail service where username+[folder]@domain would automatically send the message straight to the named folder, but this is also easily achieved by providing a filter.