Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Changes to the Kubernetes Slack

kubernetes.dev

Post reply on HN
Print view View original

21–30 of 31 posts

Re: Changes to the Kubernetes Slack

#21

Post by dijit »

teeray wrote: post #5

How is IRCv3 doing these days? I remember it was supposed to address all the pain-points people had that made them want to use Slack, but I haven’t heard of anyone using it in years. Seems support for its feature-set is pretty decent: https://ircv3.net/software/clients

It works pretty well, but there's no money in IRC - and the people who like it the most have no desire to upgrade clients.

So, the "best" experience remains with either "The Lounge", or weechat. Neither of which are comparable to Zulip for UX or Slack/Discord for UI.

Re: Changes to the Kubernetes Slack

#22

Post by dijit »

croemer wrote: post #10
mikeortman wrote: post #7

Earlier quoted context omitted.

I think technically they can. It’s because they’re downgrading them to a free service. I’m going to venture to say that it’s a money grab on a previously generous gift by slack.

No money gained because they move off from Slack.

On the contrary, not hosting them means they're not losing money either.

It's win-win for them. Either they pay (they won't/can't), negotiate to pay ($$$ at least)- or they move away, all of which increase the amount of available resources for Salesforce.

Re: Changes to the Kubernetes Slack

#23

Post by dijit »

robertlagrant wrote: post #19
kondu wrote: post #9

Earlier quoted context omitted.

I'm sure they considered hosting matrix or zulip, I wonder what the estimated monthly cost of that would be for a community of their size

Yeah but what scaling/deployment layer should they deploy it on? I vote for Azure Service Fabric.

at 250.000 users they're going to hit specific limits very quickly, and frustratingly, proper sysadmin skills are (I think) nearly completely eroded from our industry.

This leaves us with expensive offerings despite a pretty static load (a-la; cloud).

Back in the day, burgeoning sysadmins would have cut their teeth on projects like this, but sadly they'd need someone quite senior at this point to avoid major pitfalls.

I'm not even sure myself how I would prevent the abuse of uploaded images; both in terms of rate limiting new accounts and the potential harmful material that might be shared. -- And I am one of the sysadmin types who cut their teeth on problems like these.

Re: Changes to the Kubernetes Slack

#24

Post by croemer »

croemer wrote: post #12

4 days notice period to archive everything? Not a good look for Slack and/or the k8s working group (if they had known earlier already).

Turns out there was no notice. So it's Slack pulling the rug in an aggressive way: https://github.com/kubernetes/community/issues/8490#issuecom...

Re: Changes to the Kubernetes Slack

#25

Post by raesene9 »

kondu wrote: post #9
daft_pink wrote: post #3

Just isn’t practical to use Slack for open communities based on it’s pricing structure, but isn’t practical for Discord to exist based on it’s Profit and Loss statement. Gotta be some way to split the difference and make money with online community chat without paying north of $8 per user.

I'm sure they considered hosting matrix or zulip, I wonder what the estimated monthly cost of that would be for a community of their size

I think consideration may have been limited by the fact that (AFAIK) Slack only provided a week's notice of this change, which has left the Kubernetes volunteers trying to act quickly to avoid losing data which isn't easily archived (private channels and DMs)

Re: Changes to the Kubernetes Slack

#26

Post by [deleted] »

daft_pink wrote: post #3

Just isn’t practical to use Slack for open communities based on it’s pricing structure, but isn’t practical for Discord to exist based on it’s Profit and Loss statement. Gotta be some way to split the difference and make money with online community chat without paying north of $8 per user.

[deleted]

Re: Changes to the Kubernetes Slack

#27

Post by Arathorn »

kondu wrote: post #9
daft_pink wrote: post #3

Just isn’t practical to use Slack for open communities based on it’s pricing structure, but isn’t practical for Discord to exist based on it’s Profit and Loss statement. Gotta be some way to split the difference and make money with online community chat without paying north of $8 per user.

I'm sure they considered hosting matrix or zulip, I wonder what the estimated monthly cost of that would be for a community of their size

For Element, I suspect they'd be best off using Element Server Suite (https://element.io/server-suite) which are the official helm charts for Element, Synapse and the various component parts. To scale elastically they'd need the Pro version, but we could provide them with a discounted license of some kind (but not free, given Element isn't profitable yet and we need the $ to actually work on Matrix...)

If anyone reading this wants to talk, hit me up at matthew at element.io (or @matthew:matrix.org on Matrix)

Re: Changes to the Kubernetes Slack

#28

Post by cadamsdotcom »

bananapub wrote: post #16
cadamsdotcom wrote: post #13

Perhaps k8s could roll its own Slack replacement. Sound crazy? Consider git: born of specific needs of Linux kernel plus a struggle to use commercially available tools. If you squint there are similarities to the situation that led Linus Torvalds down the build-it-yourself path. What a tool like Slack “is” is pretty well defined, and they’re not being evil but are just unable to support a very unique community in k8s…

git was a tiny crappy content tracker linus, one of the most prolific C hackers in history, did in a couple of weeks. it wasn’t even a version control system nor intended to be used directly, merely to make his personal life easier after tridge enraged larry. “Normie focussed multi platform api-driven rich text media chat system” is 100x that work and unrelated to k8s’ existing ocean boiling.

I’m not saying they should; only that they could.

Nothing about it needs to be normie focused.

“merely to make his personal life easier” is the key. What made it what it is today is - after the first barebones release, it was worked on until it was useful enough to be worked on by more people; pretty soon there were a few folks using it, and eventually the snowball effect led to it being maintained by a motivated group of folks, which eventually leads us to today.

A collab tool doesn’t need to be built from scratch. Existing options include IRC, Matrix, Zulip... Maybe one fits the bill already.

Re: Changes to the Kubernetes Slack

#29

Post by crb »

kondu wrote: post #9
daft_pink wrote: post #3

Just isn’t practical to use Slack for open communities based on it’s pricing structure, but isn’t practical for Discord to exist based on it’s Profit and Loss statement. Gotta be some way to split the difference and make money with online community chat without paying north of $8 per user.

I'm sure they considered hosting matrix or zulip, I wonder what the estimated monthly cost of that would be for a community of their size

They haven't considered that, because until this week they didn't need to. Some Linux Foundation projects use Zulip, and the team behind the project seem willing to host for free.
Post reply on HN