I use IRC for all sorts of purposes and audiences, there are tens ifnot hundreds of implementations that are being actively maintained, and it's been a standard for decades. How does that suck?
Edit: Oh they mention "Like IRC, but smarter", where smarter is a link. Let's see about that.
> Know who's seen any message.
Facebook does this. It more annoys me than anything else, but I can see the point. People could also simply acknowledge having read something, but again, ok I see the point.
> Edit messages after you've sent them.
Depends on the audience... On Skype (1 on 1 chat) it rocks, StackExchange's chat is generally not for 13-year-olds either so there it works as well, but in most team chats I wouldn't want this feature. Since it's aimed at Github users, I suppose this is a nice feature.
> Automatically embeds content like YouTube, pictures of cats and other stuff.
God no.
> Did we mention our smart notifications? @mentions. Batched notifications. Won't annoy you by making your phone beep on every message.
IRC, IRC and IRC.
> Awesome emotigifs.
You mean like MSN's Winks®? [1]
> Infinite chat history stored in the cloud.
trustworthiness--;
> Searchable too, naturally.
grep
> Oh, and a unified activity feed.
Hmm, what's that for? You mean like IRC clients' "last message" feature, or a way that stalks people even when your client is not running?
I believe you got this from gitter.im - that is a very similar idea (likely a ripoff of ours) which is nothing more than a concept and design. We build a rough working prototype.
While not the same concept (or scale), this comment seems awfully similar to the ones originally posted about Dropbox. People resorted on using older UNIX programs to handle what Dropbox did better and much much easier.
While some people don't exactly value aesthetic, I do, so even if it's a prettier IRC client, I'd take it. I'll also point out that "team chat" may include a whole company. From sales to support to engineering and design. It's highly unlikely that everyone would like or know how to use IRC.
Don't worry - we don't touch your repos! Unfortunately the read permissions we need are classified as "write" (or at least we couldn't find a way to specify them as "read" in our very limited time).
GitHub doesn't allow enough specificity in application permissions. They don't need write permission, but they need access to Github orgs (obviously) and GitHub lumps them together.
So, first things first: Get yourself a domain name.
Second, why do you need Write access to anything? You're team chat, with some notification power. Giving you access to write on not just my repos, but the repos of my organizations, is a pretty big "Hell no" without there being a company there, some names, or(and no offense here, Ross), someone I can properly sue if the shit really hits the fan.
This isn't so much a question of trust as much as just me trying to cover my ass. Right now we're using Campfire, and personally, I'm not a huge fan- yeah it's been integrated with everything under the sun, but interacting with it from a phone is no fun, it's hard to notice anything being said on it without a window constantly open on it, and the styling makes reading Github notifications particularly awful.
This is a longwinded way of me saying I want to give you a shot, but you either need some extremely strong justification, or you need to pull back on those requests.
Edit: I'm seeing that apparently Github doesn't separate the permissions out very much? That's pretty worrying.
We definitely plan on getting a domain once the hackathon is over and we have some time to relax and really plan this out :)
As I mentioned earlier, you have nothing to worry about - we don't touch your repos! Unfortunately the read permissions we need are classified as "write" (or at least we couldn't find a way to specify them as "read" in our very limited time).
Once everything settles down we are going to think about ways to make it easier for people to use and trust the service so that they don't need to worry about permissions or anything like that.
Thanks so much for your input, we'll definitely take it into account!
> or at least we couldn't find a way to specify them as "read" in our very limited time
You didn't miss anything - GitHub repo permissions are pretty much all-or-nothing. We've been putting up with this for two years at CircleCI :(
[For others, to read from a private repo, you need to request the "repo" scope, which actually gives read+write access to every repo in every org that you have access to. See https://circleci.com/docs/github-permissions for more details.]
i don't know what your thing does. its blocked by a login or leave forever page set.
other guys show what they have.
check your stats - how many unique come to the front page, click around aimlessly hoping to get somewhere, then never come back.
This was put together in just 48 hours - once the dust settles we'll really think of a better way to attract users to the service and better explain what we do.
Can we please reign in the standard asshole HN comments for once? These are teens showing off a project they built. At least make an effort to carefully word your criticism, or say something nice alongside it.
25 comments
[ 4.3 ms ] story [ 45.8 ms ] threadIRC?
I use IRC for all sorts of purposes and audiences, there are tens ifnot hundreds of implementations that are being actively maintained, and it's been a standard for decades. How does that suck?
Edit: Oh they mention "Like IRC, but smarter", where smarter is a link. Let's see about that.
> Know who's seen any message.
Facebook does this. It more annoys me than anything else, but I can see the point. People could also simply acknowledge having read something, but again, ok I see the point.
> Edit messages after you've sent them.
Depends on the audience... On Skype (1 on 1 chat) it rocks, StackExchange's chat is generally not for 13-year-olds either so there it works as well, but in most team chats I wouldn't want this feature. Since it's aimed at Github users, I suppose this is a nice feature.
> Automatically embeds content like YouTube, pictures of cats and other stuff.
God no.
> Did we mention our smart notifications? @mentions. Batched notifications. Won't annoy you by making your phone beep on every message.
IRC, IRC and IRC.
> Awesome emotigifs.
You mean like MSN's Winks®? [1]
> Infinite chat history stored in the cloud.
trustworthiness--;
> Searchable too, naturally.
grep
> Oh, and a unified activity feed.
Hmm, what's that for? You mean like IRC clients' "last message" feature, or a way that stalks people even when your client is not running?
[1] http://img.uptodown.net/screen/windows/bigthumb/free-msn-win...
What does your app do that a GitHub-aware IRC bot cannot?
I see. What protocol are you running anyway, proprietary and closed or can I write my own client?
While some people don't exactly value aesthetic, I do, so even if it's a prettier IRC client, I'd take it. I'll also point out that "team chat" may include a whole company. From sales to support to engineering and design. It's highly unlikely that everyone would like or know how to use IRC.
Native campfire sucks. It works, but it sucks.
Second, why do you need Write access to anything? You're team chat, with some notification power. Giving you access to write on not just my repos, but the repos of my organizations, is a pretty big "Hell no" without there being a company there, some names, or(and no offense here, Ross), someone I can properly sue if the shit really hits the fan.
This isn't so much a question of trust as much as just me trying to cover my ass. Right now we're using Campfire, and personally, I'm not a huge fan- yeah it's been integrated with everything under the sun, but interacting with it from a phone is no fun, it's hard to notice anything being said on it without a window constantly open on it, and the styling makes reading Github notifications particularly awful.
This is a longwinded way of me saying I want to give you a shot, but you either need some extremely strong justification, or you need to pull back on those requests.
Edit: I'm seeing that apparently Github doesn't separate the permissions out very much? That's pretty worrying.
As I mentioned earlier, you have nothing to worry about - we don't touch your repos! Unfortunately the read permissions we need are classified as "write" (or at least we couldn't find a way to specify them as "read" in our very limited time).
Once everything settles down we are going to think about ways to make it easier for people to use and trust the service so that they don't need to worry about permissions or anything like that.
Thanks so much for your input, we'll definitely take it into account!
You didn't miss anything - GitHub repo permissions are pretty much all-or-nothing. We've been putting up with this for two years at CircleCI :(
[For others, to read from a private repo, you need to request the "repo" scope, which actually gives read+write access to every repo in every org that you have access to. See https://circleci.com/docs/github-permissions for more details.]
I granted permissions to the app via GitHub, then I get:
Internal Server Error
Now, however, if I click on the "Sign Up" button on your homepage (http://team-name-goes-here.2013.nodeknockout.com/), it sends me to:
http://team-name-goes-here.2013.nodeknockout.com/auth/github...
and the same page simply saying:
Internal Server Error
So it seems that Github obviously granted something to your app, but now it's broken for me? It would be nice to try this out.
On another note - some screenshots on your homepage would also be nice.
Hopefully we can negotiate a way to be whitelisted by GitHub so these issues do not occur.
other guys show what they have. check your stats - how many unique come to the front page, click around aimlessly hoping to get somewhere, then never come back.
You can watch a quick video and read a description of the service at http://nodeknockout.com/teams/team-name-goes-here