phs318u an hour ago

"Ports" seems to just be "tags" as channels/filters? The problems with all such schemes (channels or tags) when used for more than personal organisation, is discoverability by the other party. This is addressed by RelayBeam through the first party disseminating their per-port address. But this merely shifts the burden of organisation to the sending party when they have multiple relationships (and therefore multiple port addresses) with you. Now they must remember which address to use for what. This problem is multiplied as each person they interact with has their own set of port "schemes".

I admire the attempt to solve the communication organisation problem, but leaving aside any functional attempts to solve the problem (which I suspect will be readily solvable through 'message aggregator AIs'), the fact that this solution requires all users to use the same platform, makes this effectively DoA (excepting organisations that might mandate a move to such platform).

marcus_holmes 41 minutes ago

I don't see how this solves any of the problems listed:

> With multiple channels and threads, users struggle to maintain context, often jumping between discussions.

> Channel clutter and disorganized conversations making it hard to follow important discussions.

> Limited external communication capabilities compared to internal use. (Applies to other messaging platforms)

> The flood of notifications from various channels can overwhelm users, causing distractions and stress.

> Time-consuming management of overflowing inboxes.

> Susceptibility to spam and security risks like phishing attacks.

Literally none of these problems seem to be solved by adding what appears to be the same thing as inbox filters. And the page doesn't explain how they think it does.

The big one being spam - how does RelayBeam stop unwanted commercial messaging?

  • supritgandhi 21 minutes ago

    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.

emacsen 2 hours ago

I'm confused at the problem this is meant to solve.

The about page talks about fragmented communication leading to overload and complexity, but it seems this communication platform sits alongside others, not interfacing to them.

That means everyone needs to use RelayBeam to communicate?

And it also seems like the name doesn't reflect what it does, as it's not relaying message?

Also, ports aren't dynamic. You can have joe@work but if the boss messages you about a specific project, you're still stuck looking at all the messages in the @work port?

If so, I'm not sure what this will solve.

  • supritgandhi an hour ago

    Thanks for your comment! Fragmented communication as in, users need to jump across multiple apps or platforms for different context, simple example, people generally use platforms like Slack/Teams for internal communication and prefer email for external communication. With RelayBeam you can have single platform for both the purpose.

    You can create project specific ports as well, as it can can segregate the messages as per the context. Another example: if joe is in sales & marketing department, then joe can have joe@sales and joe@marketing, which can be helpful in prioritizing the messages.

    Do you have any suggestions for further improvements?

    • dismalpedigree an hour ago

      So everyone needs to use RelayBeam in order to communicate? Selling all my contacts on yet another communication tool is difficult.

      • supritgandhi an hour ago

        You can start using RelayBeam whenever you think ports can help you organize the conversations. This can be done in a staged approach.