Live data from Hacker News

Show HN: Gitter – Chat for GitHub

gitter.im

51–60 of 116 posts

Re: Show HN: Gitter – Chat for GitHub

#51

Error: failed 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:10…

Yes, node node node! :) Um, thanks for pointing this out, will take a look at it, we may have blown through the rate limit.

Isnt echoing errors like that a security issue? Im not implying it necessarly is, because it's obviously conveniently useful for debugging.

Re: Show HN: Gitter – Chat for GitHub

#53
post #42

Earlier quoted context omitted.

When you perform the OAuth signup via GitHub, GitHub provides us with your name username, etc. Then, if you click the link to signup with Troupe, we create a Troupe account for you, pre-populated with your details, so that you don't need to enter them again. Hope this helps! (I'm one of the devs)

So you're pushing my information between two different services. Both of which happen to be provided by the same organization. It's kinda convenient, but still does not feel quite right :(

I concur, doesn't feel right.

I think at the very least, have a message saying "This information was shared when you did X" so it's at least explicit.

Possibly just not at all; methinks the github crowd, unlike the facebook crowd, are sufficiently privacy sentient.

Re: Show HN: Gitter – Chat for GitHub

#54
post #49

(Edit: I initially thought this was _from_ GitHub. Apparently it's not, so please disregard the nagging below. It is a cool idea, but if GitHub did this, I'd have different expectations.) I'd be all over this if it was an IRC server. Most big projects already have an IRC channel on FreeNode, so this'd be a natural fit: Provide an IRC server with a channel for each project, provide a free web client for this server wi…

I think with some hacking you could offer a bot that did some of this, perhaps together with client-side plugins.

Re: Show HN: Gitter – Chat for GitHub

#55
post #53
post #42

Earlier quoted context omitted.

So you're pushing my information between two different services. Both of which happen to be provided by the same organization. It's kinda convenient, but still does not feel quite right :(

I concur, doesn't feel right. I think at the very least, have a message saying "This information was shared when you did X" so it's at least explicit. Possibly just not at all; methinks the github crowd, unlike the facebook crowd, are sufficiently privacy sentient.

That wasn't the intention at all, it was more to save you having to type those details in again. Sorry if you felt wronged by it.

We're developers ourselves and value our privacy too/

Re: Show HN: Gitter – Chat for GitHub

#56
post #11

Beautiful, but unfortunately it wouldn't be appropriate for my non-technical teammates, so I cannot see it beating out hipchat. I love the concept though and I can see this being the tool of choice for technical teams.

Yeah, that barrier is a tough one to overcome. We've found that having an easy entry point (nothing to install, one click signup etc.) lowers the barrier a bit. Also having some kind of free tier could always be an advantage over hipchat...

HipChat also has a free tier (for teams of 5 or smaller). https://www.hipchat.com/pricing

Re: Show HN: Gitter – Chat for GitHub

#57
post #52

How long will it take to be a usable product? I might be interested and need to know if I should keep looking around or just wait a bit.

Take a look at our current product, it's not directly tied to GitHub, but has webhook integration (with BitBucket, Travis, Jenkins too).

www.trou.pe

We'll need to sweat some details on Gitter, so hard to say on the timing. We may fuse the two concepts together, so it will be more about product-related decisions than development time as we have a lot of the code already.

Feel free to give us feedback on Troupe so we can loop that into the future direction of this product.

Re: Show HN: Gitter – Chat for GitHub

#58
post #51

Earlier quoted context omitted.

Yes, node node node! :) Um, thanks for pointing this out, will take a look at it, we may have blown through the rate limit.

Isnt echoing errors like that a security issue? Im not implying it necessarly is, because it's obviously conveniently useful for debugging.

Yup, they should log / e-mail themselves the error messages when in production rather than displaying them, sensitive info might leak plus stacktrace aren't very friendly.

Looks like they might have left the connect.errorHandler() dev middleware (http://www.senchalabs.org/connect/errorHandler.html) plugged into their app.

Re: Show HN: Gitter – Chat for GitHub

#60
post #51

Earlier quoted context omitted.

Yes, node node node! :) Um, thanks for pointing this out, will take a look at it, we may have blown through the rate limit.

Isnt echoing errors like that a security issue? Im not implying it necessarly is, because it's obviously conveniently useful for debugging.

We normally don't do this, we put this little preview app together quite quickly using a slightly different infrastructure to our regular stuff.

We normally log these and just display a friendly error message to the end user.

Post reply on HN