I hate these emails. Why do corporations have to be so heavy handed? How about just a nice message explaining the problem and possible solutions. Love to read about something like that! I now hope someone keeps slack’s legal department busy. The product sucks anyways. It was down yesterday and it’s a poor excuse for a reliable chat platform.
Bye bye BetterSlack
101–110 of 392 posts
Re: Bye bye BetterSlack
#102Earlier quoted context omitted.
He should talk to a lawyer, especially if he accepted a binding agreement by using Slack that forbids any of the research he did to figure out how to get his integrations to work.
A binding agreement? Why would he sign one of those?
You don't have to literally sign something to be bound by an agreement.
Re: Bye bye BetterSlack
#103So it lasted 3 days? https://g3rv4.com/2018/08/betterslack From that post: > I may build an Electron app that patches the Electron app… so far, that’s what makes the most sense to me. But we’ll see. Even if this was against the ToS, could it be stopped? I didn't know one Electron app could target the other.
> I didn't know one Electron app could target the other.
A year ago or so, I was able to start desktop Slack with a param to open the dev tools port open and use something like puppeteer to control it (at the least, I opened dev tools inside of Slack's Electron app). Not sure if that is still the case.
Re: Bye bye BetterSlack
#104Earlier quoted context omitted.
He should talk to a lawyer, especially if he accepted a binding agreement by using Slack that forbids any of the research he did to figure out how to get his integrations to work.
A binding agreement? Why would he sign one of those?
I think what tptacek means is that when we sign up for a service, we agree to terms of use. Even if we don't sign it, it might be legally undecided as to whether that counts as
a binding contract, nor whether "terminate the user's service" is the only recourse the service provider has.
Re: Bye bye BetterSlack
#105Earlier quoted context omitted.
Because... I have lots of things to work on, lots of things I want to build, lots of people I want to talk with. None of them involve talking with a lawyer in a different country over something that's really not that important in my life.
I got a cease and desist for a extension that improved the look of Craigslist. I just ignored it, I've never had to talk to a lawyer or anything. But that's my situation, I understand that other people may feel differently. EFF offered to review my case, but I didn't wind up following up with that either. Might be an option for you.
Craigslist sued another company that extended its listings with their own code and, as I recall, won.
Re: Bye bye BetterSlack
#106This is a threat of violence. Nothing less.
Re: Bye bye BetterSlack
#107Earlier quoted context omitted.
I worked at a medium-sized company during the transition from IRC to Slack. The problem the company had was a split in comms networks. There was a lack of will on the part of engineers to move to GChat, and non-engineers were unwilling to respond/engage on IRC. Marketing, Sales, and Admin were using GChat, while engineering used IRC. Getting everyone on the same comms platform was a major improvement. I'm not saying…
No, it was dumb, and I didn't stutter. It's an extraordinarily short-sighted move to switch to Slack. IRC may not be for everyone, but clients like The Lounge and alternatives like Matrix are quite friendly to non-engineers.
I've been contemplating putting The Lounge in front of my IRC servers. How well does it scale? i.e. how many web users can you support with {n} amount of memory/cpu?
I've used cgiirc, but it isn't pretty and some people want pretty and client-less.
Re: Bye bye BetterSlack
#108Earlier 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.
I see your 500:30 and raise you with 30:5 at my company. It's complete overkill.
Re: Bye bye BetterSlack
#109If you want to make a better version of Slack, go all the way.
Re: Bye bye BetterSlack
#110Earlier quoted context omitted.
this was a bunch of Tampermonkey scripts... but I don't want to ignore their cease and desist. I... just don't do it. changing the name is not an issue... however, if I have to take it down, that's moot.
@g3rv4, I understand it really sucks and feels terrible. But I also understand their reaction. Don't be surprised about legal writing. He/She as a legal person is responsible for writing in a very clear and explicit way since any misunderstanding might cost the reader or themselves in the future. It just shows their accountability. You don't want a misunderstanding cost you trouble. I have colleagues working in the l…
I get it... but literally, there are THOUSAND extensions already injecting javascript on their site.
are they going after all of them? if that's the case, I'd understand.