Note that IRC supports private messaging, and there's some effort towards linking IRC authentication to slash authentication in some way. Once you have the ability to know that "example66" on IRC is the same person as "Example66" on slash, you could have a link on Example66's public profile page that would open the web-based IRC client directly into a PM to example66.
Of course, making this work asynchronously (i.e. if the recipient is not online) requires a bot to save the message, and deliver it next time they log in. Then to ensure they'd know to login to IRC and receive the message, you'd need... a new type of message in the messaging system. So this may not be simpler, but it does provide general private communications (vs. just sending an email address) without implementing yet-another-pm-system inside the slash messaging system. Maybe the right answer is both...
(Score: 3, Informative) by Foobar Bazbot on Thursday March 06 2014, @04:36AM
Note that IRC supports private messaging, and there's some effort towards linking IRC authentication to slash authentication in some way. Once you have the ability to know that "example66" on IRC is the same person as "Example66" on slash, you could have a link on Example66's public profile page that would open the web-based IRC client directly into a PM to example66.
Of course, making this work asynchronously (i.e. if the recipient is not online) requires a bot to save the message, and deliver it next time they log in. Then to ensure they'd know to login to IRC and receive the message, you'd need... a new type of message in the messaging system. So this may not be simpler, but it does provide general private communications (vs. just sending an email address) without implementing yet-another-pm-system inside the slash messaging system. Maybe the right answer is both...