Folks, use IRC, XMPP, Matrix, etc. Using proprietary protocols is dumb .
I would like to. What is a good video conference solution? To replace zoom (which works great for us so far) for example. Thanks.
Bye bye BetterSlack
31–40 of 392 posts
Re: Bye bye BetterSlack
#32Folks, 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…
>The problem the company had was a split in comms networks.
My new team is going through this. For comms, my machine came equipped with Skype for Business, Slack, Stride and Bria. It's a fun game rolling the dice when you need to ask someone a question figuring out which comms tool that person uses.
A game I've avoided playing altogether by just sending an email.
Re: Bye bye BetterSlack
#33Earlier 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.
Its the opposite at my workplace. Mostly the developers use Slack. What do your devs use instead?
Re: Bye bye BetterSlack
#34I 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.
You won't be able to tell your lawyer "this is no different than paying you with real money" and hand over a stack of monopoly banknotes. Legal advice by analogy is unlikely to be all that useful.
Re: Bye bye BetterSlack
#35I understand the naming issue but from the look of it the extension only works locally, where's the issue with that?
they don't want people injecting javascript on their website. That's all there's to it. I'm not sending anything anywhere. I'm not storing anything. I'm not profiting from it.
But I do this already with an ad blocker…
Re: Bye bye BetterSlack
#36Earlier quoted context omitted.
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.
Could they really sue you for creating a chrome extension that modifies their webpage? That would be a very dark day for the internet. I can't imagine there's any legal basis for that, but it would be very interesting to hear a lawyer's opinion. Well done on what you have achieved, keep fighting the good fight!
I dont think they can, or all the adblockers would have been removed already.
Re: Bye bye BetterSlack
#37I 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.
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.
Re: Bye bye BetterSlack
#38Folks, use IRC, XMPP, Matrix, etc. Using proprietary protocols is dumb .
I would like to. What is a good video conference solution? To replace zoom (which works great for us so far) for example. Thanks.
I like Jitsi. Zero setup, just push go and share the link:
Open source software based on standardized browser technologies.
Re: Bye bye BetterSlack
#39Earlier 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…
>The problem the company had was a split in comms networks. My new team is going through this. For comms, my machine came equipped with Skype for Business, Slack, Stride and Bria. It's a fun game rolling the dice when you need to ask someone a question figuring out which comms tool that person uses. A game I've avoided playing altogether by just sending an email.
I thought chat was going to eliminate the need for email. ;-)
Re: Bye bye BetterSlack
#40I understand the naming issue but from the look of it the extension only works locally, where's the issue with that?
they don't want people injecting javascript on their website. That's all there's to it. I'm not sending anything anywhere. I'm not storing anything. I'm not profiting from it.
> they don't want people injecting javascript on their website
They should send an email to every extension author ever, and maybe even browser vendors for supporting such a malicious feature.