Looks really interesting, you guys should take a look at www.surfly.com. With Surfly in the mix you would not just be able to chat about things but also show people around. Also, I couldn't find any contact info. :(
Show HN: Gitter – Chat for GitHub
21–30 of 116 posts
Re: Show HN: Gitter – Chat for GitHub
#22Re: Show HN: Gitter – Chat for GitHub
#23I don't really like the idea of signing up with my github account. But I like the idea of Gitter. One small improvement: Link the "@GitChat" on the confirmation page to the twitter account ;)
Re: Show HN: Gitter – Chat for GitHub
#24Very clever way to make signups easy, relevant to the interest you're trying to gauge, and gather far more information about me than just my e-mail address (eg. my activity level on GitHub, the type of projects I'm involved in).
Re: Show HN: Gitter – Chat for GitHub
#25At any rate, best of luck! Amazing effort.
Re: Show HN: Gitter – Chat for GitHub
#26Not directly related to your product, but I always wonder why, with soft launches like this where you gauge interest, why not make the "interest" count public? How many people have you captured? That being said, I've wanted this idea for a while, so I signed up straight away.
Re: Show HN: Gitter – Chat for GitHub
#27Re: Show HN: Gitter – Chat for GitHub
#28failed to fetch user profile (status: 403 data: {"message":"Maximum number of login attempts exceeded","documentation_url":"http://developer.github.com/v3"}) at Strategy.userProfile (/opt/gitter/landing-app/node_modules/passport-github/lib/passport-github/strategy.js:90:28) at passBackControl (/opt/gitter/landing-app/node_modules/passport-github/node_modules/passport-oauth/node_modules/oauth/lib/oauth2.js:105:9) at IncomingMessage.exports.OAuth2._executeRequest.request.on.callbackCalled (/opt/gitter/landing-app/node_modules/passport-github/node_modules/passport-oauth/node_modules/oauth/lib/oauth2.js:124:7) at IncomingMessage.EventEmitter.emit (events.js:126:20) at IncomingMessage._emitEnd (http.js:366:10) at HTTPParser.parserOnMessageComplete [as onMessageComplete] (http.js:149:23) at CleartextStream.socketOnData [as ondata] (http.js:1472:20) at CleartextStream.CryptoStream._push (tls.js:544:27) at SecurePair.cycle (tls.js:898:20) at EncryptedStream.CryptoStream.write (tls.js:285:13) at Socket.ondata (stream.js:38:26)
Guess it's built with node ;)
After pressing the button again, it gave me the confirmation message.