Live data from Hacker News

Bye bye BetterSlack

g3rv4.com

391–392 of 392 posts

Re: Bye bye BetterSlack

#391
post #147

Earlier quoted context omitted.

In any case, it probably is not worth likely legal costs and effort should the other party take legal action. It is one thing to theorize about legal implications, quite another to risk livelihood etc to put it to test. Defending against action takes time and money which amounts to loss in many cases even when you are successful in court.

There is almost zero chance slack would win this case and I doubt they would even try. Adblockers inject code into sites. So do password keepers. If sites could sue adblockers because it breaks their terms of service, don't you think they would? You are not bound by the slack terms of service except in the scope of your slack account or an API connection of some type. Someone else can use my software all day long to…

This is the difference between fantasizing about the likelihood of outcomes when you have no skin in the game and being on the other side of a well funded adversary that is threatening a lawsuit. Put yourself in the POV of the one with skin in the game and consider that it may take years and insane expense (time/money/energy) to prevail against even a poorly founded lawsuit.

Being "right", sometimes, is not worth the fight.

Re: Bye bye BetterSlack

#392
post #388
post #62

Here's a spiffy new fork: https://github.com/betterlimp/betterlimp

I see you've taken it down. Also bullied?

No -- the original author is continuing to maintain BetterSlack as BitterSweet, albeit without publishing to the Chrome store.

https://github.com/g3rv4/BitterSweet

I felt it was better to unpublish my (likely to be unmaintained) fork. Probably should have left up a note to redirect folks.

Post reply on HN