I wonder how much longer Slack’s web client is going to remain a first class product? Clearly, it was a good way to drive adoption, but seems that at this point they want ever more control.
Bye bye BetterSlack
11–20 of 392 posts
Re: Bye bye BetterSlack
#12Folks, use IRC, XMPP, Matrix, etc. Using proprietary protocols is dumb .
I wish it was so easy... I don't get to decide what tools my company uses unfortunately
Re: Bye bye BetterSlack
#13Re: Bye bye BetterSlack
#14I wonder how much longer Slack’s web client is going to remain a first class product? Clearly, it was a good way to drive adoption, but seems that at this point they want ever more control.
now that they got all that money, I wouldn't be surprised if they killed the web app and moved away from Electron to do native apps that are harder to be messed with.
Re: Bye bye BetterSlack
#15I wonder how much longer Slack’s web client is going to remain a first class product? Clearly, it was a good way to drive adoption, but seems that at this point they want ever more control.
now that they got all that money, I wouldn't be surprised if they killed the web app and moved away from Electron to do native apps that are harder to be messed with.
[deleted]
Re: Bye bye BetterSlack
#16I wonder how much longer Slack’s web client is going to remain a first class product? Clearly, it was a good way to drive adoption, but seems that at this point they want ever more control.
it's on the way: the webapp doesn't load on mobile
Re: Bye bye BetterSlack
#17Folks, use IRC, XMPP, Matrix, etc. Using proprietary protocols is dumb .
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 it's ideal, but it wasn't dumb.
Re: Bye bye BetterSlack
#18I dont see any legal reason why you can't publish the extension under a different name. Your extension is under no legal obligation to follow their acceptable use policy, only the users that use your extension.
There are two problems with this approach:
1. I don't want to get involved in that, even if I'm based in Uruguay and they'd have a hard time suing me.
2. What they could do is put resources to detect the extension and block it. We could start a mouse and cat game that they'd win... I don't have their resources to invest in it. After all, all I wanted was to solve Slack for me, and that would make it harder.
Re: Bye bye BetterSlack
#19I wonder how much longer Slack’s web client is going to remain a first class product? Clearly, it was a good way to drive adoption, but seems that at this point they want ever more control.
now that they got all that money, I wouldn't be surprised if they killed the web app and moved away from Electron to do native apps that are harder to be messed with.
Anything that moves away from Electron is a plus in my book
Re: Bye bye BetterSlack
#20I dont see any legal reason why you can't publish the extension under a different name. Your extension is under no legal obligation to follow their acceptable use policy, only the users that use your extension.
I'd love to hear more about this from someone with legal expertise.
It makes no sense for them to claim that every extension published on the Chrome store needs to comply with their acceptable use policy...
If that were true, then wouldn't 1Password and any other extension that uses a content script also be considered unacceptable?