Changes to the Kubernetes Slack(kubernetes.dev) |
Changes to the Kubernetes Slack(kubernetes.dev) |
Gotta be some way to split the difference and make money with online community chat without paying north of $8 per user.
If anyone reading this wants to talk, hit me up at matthew at element.io (or @matthew:matrix.org on Matrix)
But in the end, I never really relied on it for finding information, and am kind of sad that people keep creating chat communities instead of searchable forums.
I also think people overrate chat for actual learning or resolving issues. Even back in the IRC days, asking a question almost never yielded an immediate reply—-quite often you’d have to come back the day after and ask again, or check your DMs on screen overnight.
Forums let you ask and check for replies later, or search for similar questions, or even (shudder) get an e-mail reply, and Discord does exactly none of those things in a way that I find effective or productive.
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.
does sound like it's causing issues that they don't want to deal with if it's not earning them money
> Slack, a Salesforce-owned workplace messaging app, recently blocked other software firms from searching or storing Slack messages, The Information reported on Tuesday, citing a public disclosure.
https://www.reuters.com/business/salesforce-blocks-ai-rivals...
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.
Owning its own tools helps the community own its own destiny.
“Normie focussed multi platform api-driven rich text media chat system” is 100x that work and unrelated to k8s’ existing ocean boiling.
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.
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.
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.