Did You Read the Quarter-Million-Line License for Your Slack App?
Posted4 months agoActive3 months ago
mastodon.mit.eduTechstoryHigh profile
heatednegative
Debate
80/100
Software BloatLicensingSlack
Key topics
Software Bloat
Licensing
Slack
The Slack app's quarter-million-line license file sparks discussion about software bloat, licensing, and the implications of using proprietary platforms.
Snapshot generated from the HN discussion
Discussion Activity
Very active discussionFirst comment
N/A
Peak period
49
0-6h
Avg / period
9.5
Comment distribution57 data points
Loading chart...
Based on 57 loaded comments
Key moments
- 01Story posted
Sep 19, 2025 at 8:30 PM EDT
4 months ago
Step 01 - 02First comment
Sep 19, 2025 at 8:30 PM EDT
0s after posting
Step 02 - 03Peak activity
49 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 22, 2025 at 9:20 PM EDT
3 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45308503Type: storyLast synced: 11/20/2025, 3:29:00 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
But I’d argue that replacing it with
or even should be enough, but IANAL too.---
In longer licenses like GPL or Apache, you are not supposed to change any copyright statement placeholders. For example, there’s this line in the GPL text:
But it’s a part of the “How to Apply These Terms to Your New Programs” section. You are supposed to copy it into your code and fill it out there instead.---
Or they could just compress the license amalgamation! I think it would be a bit bigger but pretty reasonable, and their lawyers should be happy with this arrangement.
* When we treat different versions of say, the MIT license, with different names and copyright years inserted, as different licenses.
I have to imagine the file would compress extremely well though... I'm more curious why they don't use compression.
For example: https://salsa.debian.org/debian/highlight/-/blob/94ee6559155...
* https://debian.org/doc/packaging-manuals/copyright-format/1....
As for how it got its foothold, it comes down to having an easier onboarding than the solutions it competed with. With Mumble (or Ventrilo, etc) someone has to pay for a server. Then you have to download the client, get the host and port to connect to, enter credentials, and so on. Repeat for every server you might join. With Discord, once your account is set up you just click on a link and join the server. You don't even have to use the client if you don't want; you can join from the browser just fine. I don't think the friction of using previous solutions was actually bad, but it was enough to give Discord an edge even without the integrated chat+voice angle (which is something that those other programs never did and still don't do).
Alright, I'm exaggerating but I've never had as many problems with such a popular app of that class. I'm literally locked out right now due to a known bug (confirmed by support) and this isn't even the first time. Then there were months when recording voice notes (of all things) didn't work on Android. So many other little random things. If YouTube or something behaved that way I'd be shocked. It's a ghetto in comparison.
Yeah, I get what you're saying about friction. I'm complaining as someone who's fine with Signal and IRC, so not the target audience. Someone else also mentioned that the performance may have been better early on as well. I find that hard to believe but I'll trust ya'll for now.
I have worked with people who have this attitude and I wonder how they're doing these days.
I hope they haven't ran into any problems they cannot simply dismiss as not problems that don't have solutions.
In short: all problems back than could be solved at home.
And yeah, I know that barely anybody cares _how utterly_ wasteful software has become.
https://x.com/dhh/status/1963675999012552970
https://github.com/basecamp/once-campfire
https://nitter.net/dhh/status/1963675999012552970
Explicitly mentioned is that all Zulip features are included in the free plan.
The self-hosted offering is notably described as 100% open source software in the tab heading above all the plans, paid or free. https://zulip.com/help/zulip-cloud-or-self-hosting confirms this interpretation. It’s as owned as any other open source software. https://zulip.com/self-hosting/ even confirms that the self-hosted offering is the same software as Zulip Cloud.
The mobile push notification service is also open source and can be self-hosted for free, although this requires recompiling the mobile apps with a different secret and distributing the modified apps to the desired mobile clients. Zulip has no way around this due to Google and Apple’s push notification security models.
You do have to pay for a server, but that's kind of inevitable (as in: a server is required to run most chat software, so someone will have to rent one).
I can only read this as an oxymoron
Time to rethink.