Hacker News new | ask | show | jobs
by phs318u 628 days 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).
2 comments
supritgandhi 628 days ago
> Now they must remember which address to use for what.

I will be introducing the address/contact book feature for each user, wherein users can save the port address with whatever name they feel comfortable. So, users just need to send a message to someone from the address book (if already added), this way users don't need to remember exact port address, rather just refer the address book.

> this solution requires all users to use the same platform

I think except email, most of the solutions will require all users to use specific platforms.

link
phs318u 628 days ago
> I think except email, most of the solutions will require all users to use specific platforms.

You'll find that, while not perfect, most tools like Slack, Teams, Confluence, Jira have integrations that allow various degrees of notification, activity monitoring and message transfer - either natively or via third-party solutions such as Mio [0] which creates "universal channels" that bridge Teams and Slack channels so that messages posted on one platform are visible on both and can be responded to natively.

[0] https://techcommunity.microsoft.com/t5/microsoft-teams-commu...

link
from-nibly 628 days ago
The problem isnt remembering the contact. Its remembering which port should be used. If I have a hospital and a church port for John and there's a church sponsored blood drive that John is leading should I send it to his church port or his hospital port?
link
retropragma 628 days ago
Send it to both?
link
from-nibly 628 days ago
Ahhhhhhhhhhhhhhhhhhhhhhhh
link
irfn 628 days ago
my thoughts exactly. too much focus on "Ports" while not being able to differentiate in any way
link
supritgandhi 628 days ago
Hi, I think using "Ports" is the unique and differentiating way of messaging here.

Do you have suggestion on any additional features? I'd be happy to discuss.

link