Earlier quoted context omitted.
These are not terms of use but laws.
"Terms of Use" are part of the agreement between you and a service provider with regards to the service being provided. That's a civil law contract like any other.
Bye bye BetterSlack
361–370 of 392 posts
Re: Bye bye BetterSlack
#362Earlier 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…
> Slack could allow custom clients. But I'm pretty sure all major customers will require their employees not to use un-official clients for security reasons.
Is security really a client side thing? Obviously I understand stuff like key logging and such in a malicious client, but how would somebody using a custom client affect another user's security with an official client? I mean if it would, wouldn't that be a horrible situation anyway from security point of view?
Re: Bye bye BetterSlack
#363Earlier 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
Out of curiosity, how do you feel about discord?
Re: Bye bye BetterSlack
#364This situation all but confirms that Slack has well and truly become a investor-first, user-second company. Which is a shame because I only just finished listening to an episode of "How I Built This" where they interview Stuart Butterfield who founded Slack out of his failed gaming company and it was a great story. When you have Fortune 500 companies using you, you know you're not a startup or company for the common…
You know how to predict if this will happen? It's pretty easy. It will if the company's product or service is proprietary and centralized. It's just a matter of time.
Re: Bye bye BetterSlack
#365Earlier quoted context omitted.
"Terms of Use" are part of the agreement between you and a service provider with regards to the service being provided. That's a civil law contract like any other.
No that's not, and I'm not playing on semantic. Laws are above any terms of use, regardless of what they might say. And not using the product makes you not bound to the terms of use, unlike laws which you have to obey at all times.
> And not using the product makes you not bound to the terms of use, unlike laws which you have to obey at all times.
Of course not. But in this specific case, it is safe to assume that he is using the product, or more specifically: he used Slack to develop BetterSlack.
Re: Bye bye BetterSlack
#366Earlier quoted context omitted.
> I didn't know one Electron app could target the other. An Electron app consists of two parts: HTML5 (which can run Javascript, but within a browser-like sandbox), and native Javascript code, running under Node.js with no sandbox whatsoever. The native half of an Electron app can do anything to your filesystem (including the parts that contain other applications) that any other native app can do.
I'm not sure how easy that would be since you're dealing with ASAR (just a binary encoding but definitely not as easy as modifying plain JS files) and code signing.
Re: Bye bye BetterSlack
#367Earlier quoted context omitted.
> I think you can safely ignore this cease and desist Will you cover his legal costs for choosing this decision? Right matters less than resources if it's expensive to even be right. You can state your case here on HN without repercussion, not so when being sued (it costs to even state your case reasonably due to hazards of self-defense and it costs dearly if you lose).
Oh come on, I chose not to read every word and view every image on a web page -- it's my attention, not theirs. I choose not to download large images or ads -- it's my browser, they are sending me the bits. And if I choose to run my own code in my browser why not?? Who's computer is it, after all?
In your moralistic mind or in the courts? Because idealists are not immune to laws they don't like any more than the rest of us. This arm chair idealism is getting ridiculous.
Re: Bye bye BetterSlack
#368Earlier quoted context omitted.
Embrace Extend <- we are here Extinguish
MS Teams has become pretty popular, but they haven't marketed it nearly as much as Slack.
Main difference is cost. If you're already paying for Office 365 then paying for Slack Enterprise (or Plus, or whatever it's called these days) across a fast growing organisation of 170 people on top starts to look really hard to justify versus Teams. You can, of course, stick with the free version but this caused two problems for us:
- We ran out of integrations,
- We found losing message history more than a few days old was really starting to hurt us - you couldn't even go back and refer to a conversation you'd had last week.
Teams isn't perfect: it's purple theme is pretty gross (actually it has a couple of other themes, but they're both foul as well), it can be very slow/laggy, and it has a plethora of UX annoyances (like having poorly designed chat window layout and formatting that wastes loads of space) but we saved £20k/annum by switching over to it. And we now have conversation history and unlimited integrations.
Plus, I have to say, I do not approve of this move by Slack. They could have approached it much more positively by partnering with the author (as an example).
Re: Bye bye BetterSlack
#369Earlier quoted context omitted.
Oh no, we might have to use one of the thousands of other chat apps with identical or superior functionality but inferior marketing teams.
People who work at companies that use slack don’t have a choice.
We use slack and I still have to use 4+ other forms of communication at work daily (jira, confluence, outlook, github). Sometimes we use video chat services and conference calls as well. There are days where very little happens via slack, and I'm becoming increasingly convinced that anything beyond pinging for simple things (hey look at this jira ticket, have you done this?) is wasted effort.
Re: Bye bye BetterSlack
#370Earlier quoted context omitted.
Worth mentioning that github ended killing ZenHub, by introducing github projects, which is essentially copycat of the only useful feature ZenHub had.
As a daily user of ZenHub for over a year, I would strongly disagree that GitHub projects offers the same feature set. A Kanban view, yes.