Live data from Hacker News

Bye bye BetterSlack

g3rv4.com

221–230 of 392 posts

Re: Bye bye BetterSlack

#221
post #99
post #37

Earlier 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…

And by writing that way they likely underweight the PR risk to their business. It's their choice, but it sure as hell just turned me off.

Re: Bye bye BetterSlack

#222

> In order to remedy this, we ask that you please modify your product so that you are not forcing your own code into our services. We have opened a number of channels for the developer community to build tools that improve their experience with Slack. We encourage you to utilize those channels to their fullest extent. Except that these channels make it impossible to really interact with Slack, and they pulled the rug…

This. How many "Slack dark mode" haxtensions need to be made? I don't need more emoticon skin tones bloat. I need to save my eyes with hours in this productivity tool forced by my workplace. Slack Team, just listen to the market (hint: HN score!) and bring such guys like OP into a gig to improve your stuff.

This. Who the hell goes to legal and creates PR risk instead of just hiring the dude?

Re: Bye bye BetterSlack

#223
post #46

You solved on of my biggest gripes (muting spam) and a few others I didn't even know I had. Thanks for doing this. I grabbed a fork for myself. Definitely a big middle finger from Slack to the developer community and when I'm the one making the decisions, I'll be recommending people skip Slack. They mostly lost me when they killed the IRC gateway but they added another nail to the coffin with this.

Yep, dead to me too. I decide what code runs on my hardware.

Re: Bye bye BetterSlack

#224
We canceled Slack in July, let the year run out and didn't renew.

Simply wasn't worth it and frankly more of a distraction than just using Trello (and the client on Linux was just a fucking ballache).

Re: Bye bye BetterSlack

#225
post #93

Earlier quoted context omitted.

They do when you want to redistribute it with their name, which is the whole point of this discussion.

The heart of their complaint was not the name. It was the fact that the extension injects code into their site.

> the extension injects code into their site.

But it doesn't inject code into their site, right? The HTTP request is made to the server all the same, nothing modified via the browser, it's all code additive/correction in the extension?

Re: Bye bye BetterSlack

#226
post #93

Earlier quoted context omitted.

They do when you want to redistribute it with their name, which is the whole point of this discussion.

The heart of their complaint was not the name. It was the fact that the extension injects code into their site.

I'm not sure I'd say it injects code in to 'their site', as slacks site never sees the code.

It injects code into the dom model of the users browser.

Re: Bye bye BetterSlack

#227

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

I read that as "Get Even Bot." Which would be a cool slack bot service as well...

Re: Bye bye BetterSlack

#229
OP: since Slack is saying they own the execution environment running in your browser, send them a hosting bill for running their application in your computers. Multiply it times every user on your instance.

Re: Bye bye BetterSlack

#230

Earlier quoted context omitted.

This just starts a death spiral though. Slacks next step is to start detecting the objecting code and banning users from using the web interface that are found using those tools. There are a bunch of folks doing this already for ad blockers.

Try using Slack in a browser on Android. It doesn't work. I find that really objectionable. They don't (last time I asked) distribute an APK. Instead they directed me to a pirate APK site, so I don't believe it's for security.

What browser are you using and are you upto date. Many sites don't work on mobile chrome.

I find it hard to believe they would redirect you to a pirate site. Are you sure it was a pirate site and not just a third party site hosting apks

Post reply on HN