Show HN: ClapChat – Instant messaging for HN users
clap.chat
clap.chat
Main features we think you'll like: - frictionless signup. You don't need to manage another login combo. Works kind of like Medium's signup, but with less steps - simple. Button next to comments, easy lookup. We wanted you to not have to think about it to use it - backwords compatible. It works with people that haven't signed up yet
Happy to go further into details on any of that if interested. We are considering open sourcing the entire project, is that something people would be interested in?
All kidding aside congrats on your launch!
Look forward to your blog posts (and maybe source) with more detail as this has been a topic of interest for me off and on over recent years.
You can add this HN conversation on the bottom of your landing page easily to show what people is saying about your project in context. Still in development though.
Biggest difference from my first impression of hnchat is that we built ours as a chrome extension and you participate directly on HackerNews instead of an external domain.
If I run an intercepting proxy and alter all instances of my username in the HTML response from HN servers to appear in every way to be logged in as 'dang'.... How would your extension detect the forgery?
I'm working on a blog post that goes into much further detail and will post soon.
You should probably also answer this on your page.
This is something I feel we can strike a balance with, open to any feedback and ideas people have.
clap.chat: myemail@example.com
Edit: spellingWe don't even want to dance the line with spam. Thanks for the feedback.
What if when you try to message a user who hasn't signed up and it opens their profile page and the user can type in the email address manually if it is available. Then we don't have to pay for mechanical turk and the user is just using ClapChat as their email client in a way. I'm convinced we can crack this nut in a way that works and doesn't bother people :)
Edit: upon thinking about it more, it might be better to randomly generate an address used for each conversation, to prevent a spammer from sending email to someone's @clapchat address
Say I want to be able to communicate with HN members via email, so I include my email address in my profile. clap.chat makes it easier for clap.chat users to send me email using the email address in my profile, though ideally they want to clap.chat with me. I don't want to use clap.chat. If I don't want to use clap.chat but am getting invitations to use clap.chat, the burden to deal with that is now on me, be it with a filter, or perhaps adding a note to my profile. Perhaps clap.chat includes a record of people who have opted-out.
All of these methods parallel the behavior and handling of spam. Whether or not there's daylight between these types of invites and spam depends on one's perspective.
If I have to sign up to your service to read or reply to the message then it would be spam.
I'm sold.
Not to be antagonistic but what difference does it make if it's not "standards based" while it works for them and does what they want it to do?
"Full Integration with you (sic) HN Account"
same section, last sentence: "Your (sic) welcome."