Animated custom emojis seem to be a common thread, animated images in general cause my CPU and memory to spike when using slack. Our network engineer loves this dancing parrot emoji but it basically pins a core on my machine and adds 20-30% of memory to slacks process.
I've switched over to using mattermost, it can be (and is) self hosted so I'm not as worried about slack getting hacked (again) and leaking our info/taking control of our systems with chatops.
The downside is; mattermost is not a strong replacement. I wrote a bot to basically do a large part of my job for me, and coding against mattermosts websocket protocol and dealing with authentication has been messy to say the least.
Slack is a joy to code against and use from a UI perspective when compared. (sadly, as I don't like it for ideological reasons)
Mattermost is also an example of how not to license software, including a promise not to enforce provisions of the license they have chosen. If one needs a promise, one has probably chosen the wrong licensing structure.
Here's a fun one: say I use the MIT binaries, then debug a problem by reading the AGPL source code. What legal position am I in? (If you have an answer for that rhetorical question, by the way, you haven't thought of the problem long enough.)
They launched exclusively AGPL and then made MIT as a concession after discovering that a number of companies outright ban AGPL and won't pay for it unlike MongoDB, but licensing binaries differently than source code is not something you come across often.
I must be slow because I'm not seeing the issue. Can you explain it how reading the source code affects your relationship with a binary you didn't build?
I wouldn't call that history. I only encountered a variant of this gif once, on a discord channel having the face of one of the two streamers. This site just shows me a lot of very similar gifs.