241–250 of 392 posts
Earlier quoted context omitted.
> 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.
Its the opposite at my workplace. Mostly the developers use Slack. What do your devs use instead?
Folks, use IRC, XMPP, Matrix, etc. Using proprietary protocols is dumb .
I was responsible for getting several development teams on Slack. You see, nowadays few people outside of us hardcore geeks will want to use IRC (my first option). And there are things that "modern" chat clients do better. For instance, our monitoring system can post messages to slack with links to images to allow us to display graphs inline, links to runbooks, and even buttons to take actions. IRC won't do that. Sec…
Depends on the client. The Lounge does this.
Earlier quoted context omitted.
It's our right as developers to modify and upgrade the tools we use. It's important to ensure that this remains true both today and in the future. I wanted to give you a moral boost, in case you were looking for a reason to take a stand. But if you don't want to, that's entirely valid.
Ok Stallman, now back to reality where people do own software, they do have legal restrictions on its use, and it's not a human right to circumvent it.
At 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…
I just reached out to joe (of this post) and I now recommend geteventbot to everyone. Small businesses run by responsive leaders like that deserve our $$$s
Earlier quoted context omitted.
I just reached out to joe (of this post) and I now recommend geteventbot to everyone. Small businesses run by responsive leaders like that deserve our $$$s
I read that as "Get Even Bot." Which would be a cool slack bot service as well...
I think you can safely ignore this cease and desist. Just change the name and add a disclaimer so your users know that by using your extension they are violating their acceptable use policy. This is no different than any user writing a Tampermonkey script to modify any website they want to modify. Even further, this is no different than a user opening the Dev Tools console and modifying things there.
In that case, there would be no "contractual privity" between Slack and the dev, and Slack would have to go after him for inducing breach of contract or some such thing.
I have been on a couple of projects that used Slack and AFAICT there is nothing in their service that accounts for them being a hugely successful business.
From something I wrote in January 2016 (just one concern of many): "Reasons Not to Use Slack for Free Software Development" https://pdfernhout.net/reasons-not-to-use-slack-for-free-sof... "Slack requires signing up and agreeing with a long Terms of Service (TOS); the TOS can be changed at any time, and historically such TOS have changed for the worse over time for other services once a lot of users adopt the service…
That, data mining, must be part of the business case. Especially the friend maps they can generate.
Earlier 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).
There isn't even a threat to sue yet. I'd at least wait until they escalate and post everything publicly as we go.
>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 necessary assistance.
tl;dr: respond and desist or they will escalate to the next step. Legal action is heavily implied, and it's outright foolish for you to read that and somehow think there's no threat to sue, whether implicit or not