41–50 of 222 posts
Earlier quoted context omitted.
This is my biggest problem with Slack. It's a cool product that could have been built over IRC . But no, they had to create their own walled garden.
Whilst I take your point, worth noting that Slack does offer an IRC gateway to allow for use via an IRC client. Not quite the same thing as basing everything on IRC, but better than nothing?
Earlier quoted context omitted.
I don't understand you reasoning at all. What could be the problem with using a chat software that is released under AGPL?
Because almost certainly engineers will want to integrate an on-premises system into their existing system, and that will trigger the AGPL for all the systems that are network-connected to the AGPL system. Unless you are sure that your engineers will know to not try to integrate the AGPL software with any of your existing systems, I agree that people should just stay away.
Are Tinfoil hats on sale or something?
I don't really get why there is so many Slack alternatives coming up these days. On every post like this there is tons of comment linking to other Slack alternatives, it's not like this is gonna be _the_ Slack-alternative. Here is a non exhaustive list : RocketChat : https://news.ycombinator.com/item?id=9624737 Let's Chat : https://news.ycombinator.com/item?id=9040841 Friends : https://news.ycombinator.com/item?id=94…
> We’re a YC-backed indie video game company releasing an open source alternative to Slack. Don't want to troll you guys here, but if you're a video game company why are you spending so much time building a Slack clone? I was expecting some short of explanation in your blog post like "we did this because this serves as a core piece of our company for X reason and Slack didn't fit our use case for Y reason".
Earlier quoted context omitted.
Because almost certainly engineers will want to integrate an on-premises system into their existing system, and that will trigger the AGPL for all the systems that are network-connected to the AGPL system. Unless you are sure that your engineers will know to not try to integrate the AGPL software with any of your existing systems, I agree that people should just stay away.
No it won't... It will at most trigger the AGPL for the integration off that system... which is it's proprietary no one will ever want... hence no one will ever sue you to release it. Are Tinfoil hats on sale or something?
Just to communicate the impact here, getting compliance wrong can result in significant legal liability. You and I are both unqualified to dismiss it or discuss it.
> We’re a YC-backed indie video game company releasing an open source alternative to Slack. Don't want to troll you guys here, but if you're a video game company why are you spending so much time building a Slack clone? I was expecting some short of explanation in your blog post like "we did this because this serves as a core piece of our company for X reason and Slack didn't fit our use case for Y reason".
Earlier quoted context omitted.
I don't understand you reasoning at all. What could be the problem with using a chat software that is released under AGPL?
Because almost certainly engineers will want to integrate an on-premises system into their existing system, and that will trigger the AGPL for all the systems that are network-connected to the AGPL system. Unless you are sure that your engineers will know to not try to integrate the AGPL software with any of your existing systems, I agree that people should just stay away.
That's the FUD version.
The real version is that unless you are changing the source code (hint: not just writing a plugin using an externally facing API) and deploying it, you don't have to do shit.
> We’re a YC-backed indie video game company releasing an open source alternative to Slack. Don't want to troll you guys here, but if you're a video game company why are you spending so much time building a Slack clone? I was expecting some short of explanation in your blog post like "we did this because this serves as a core piece of our company for X reason and Slack didn't fit our use case for Y reason".
> We’re a YC-backed indie video game company releasing an open source alternative to Slack. Don't want to troll you guys here, but if you're a video game company why are you spending so much time building a Slack clone? I was expecting some short of explanation in your blog post like "we did this because this serves as a core piece of our company for X reason and Slack didn't fit our use case for Y reason".
I can't tell if you're aware of the coincidence, but did you know that Slack was a pivot from game development just like Stewart Butterfield's previous unicorn Flickr?
I don't really get why there is so many Slack alternatives coming up these days. On every post like this there is tons of comment linking to other Slack alternatives, it's not like this is gonna be _the_ Slack-alternative. Here is a non exhaustive list : RocketChat : https://news.ycombinator.com/item?id=9624737 Let's Chat : https://news.ycombinator.com/item?id=9040841 Friends : https://news.ycombinator.com/item?id=94…
So many slack alternatives are coming up because slack is really good. It's that simple.