Earlier quoted context omitted.
Are you serious? Did you miss the obvious subtext? >Please respond to this message to acknowledge that you have received it. If you can resolve the matters specified above in the next seven days, that would be excellent. If you anticipate that it will take longer, please let us know. I’ve cc’d our Legal alias so that in the event that I am unable to respond, one of our product counsels will be able to provide any nec…
I guess the person you're replying to's point was to take it to the next step. Let them initiate legal proceedings (and pay lawyers) to do something. Maybe it's foolish, maybe it's not, but this email cost Slack the salary of the person for the time it took him/her to write it. At least make them also pay for an hour or two of legal fees to have this taken down.
Bye bye BetterSlack
301–310 of 392 posts
Re: Bye bye BetterSlack
#302Slack has really jumped the shark. Between this and their cutting off their IRC gateway, I don't really see the point of using it. You can't be openly hostile to people who create "hacks" like this if you're claiming to be a communication medium for "hackers."
Slack is no longer for "hackers". It's mainstream now. My company of 500 with only 30 devs uses it. These are power moves by Slack. They want to have greater control over the communication medium and presentation If you thought they were ever going to support extensions of their IRC gateway for long, then you misunderstood their product and who their market was or rather who their market became
Re: Bye bye BetterSlack
#303Earlier quoted context omitted.
For one thing, the extension author is not an active participant and cannot be considered to be trespassing. A user, maybe. But I don't think we'll see Slack banning users anytime soon.
The intent is clear. I don't know the details of those decisions but Blizzard has won cases and stopped people from distributing tools that access their services in ways they don't approve of.
Re: Bye bye BetterSlack
#304Earlier quoted context omitted.
You don't have to literally sign something to be bound by an agreement.
> You don't have to literally sign something to be bound by an agreement. That's only in the US as far as I know, everywhere else you can't be bound by an agreement without signing anything.
So thats not true.
Re: Bye bye BetterSlack
#305Re: Bye bye BetterSlack
#306Earlier quoted context omitted.
Slack is no longer for "hackers". It's mainstream now. My company of 500 with only 30 devs uses it. These are power moves by Slack. They want to have greater control over the communication medium and presentation If you thought they were ever going to support extensions of their IRC gateway for long, then you misunderstood their product and who their market was or rather who their market became
> My company of 500 with only 30 devs uses it. Same at my workplace. Slack is mostly used by the managers, all the devs avoid it. Even if you don't mind the proprietory protocol, the performance even on beefy machines is an absolute dumpster fire, that nobody wants to touch the app with a ten foot pole.
Or are you referring to audio calls and video calls?
Re: Bye bye BetterSlack
#307…or maybe just stop trying to play with the cat tail if you don't want to get scratched. There is plenty of solutions out there to do chat messaging "kinda like" or maybe better than Slack. I'm using Slack daily and I can't find what this platform has something so magical about it. I am personally building a communication client that can do IM, video-conferencing, file sharing, posting articles… all based on XMPP. It…
I’d really like to give zulip a try... unfortunately, I don’t have voice or vote over that decision on my company. Also, I love the company too much to resign over a such a small thing that can be fixed with a 20kb extension.
1. They do not support self-hosting the code on a system with anything else hosted on it. You are strongly recommended to dedicate a server (VPS, Docker, whatever) to your Zulip installation. You can try to install it on an existing server, but it is far from trivial, and doing so is unsupported.
2. As part of the installation script(s), they blindly wget code and execute it with bash. https://github.com/zulip/zulip/blob/eb676e8e508df0349662addd...
Re: Bye bye BetterSlack
#308Also reverse engineering for the purposes of compatibility is nominally legal in the USA, but like every other so-called right it's pay to play.
Re: Bye bye BetterSlack
#309OTOH, like someone else said, please contribute to improving riot/matrix instead.
Re: Bye bye BetterSlack
#310At GitHub, we faced the same issue when ZenHub [1] came out with their chrome extension. While, Slack is well within their rights to _ask_ you not to modify their user experience, it's short sighted of them to do so. With ZenHub, we worked with them even closer because we saw that our users were happier using GitHub + ZenHub. We made it super clear that UI changes would likely break their app but that would be a risk…