Live data from Hacker News

OpenAI should build Slack

latent.space

151–160 of 349 posts

Re: OpenAI should build Slack

#151
post #121

Google should build slack. Its a travesty how incredibly good their google workspace suite of tools is, and then google chat is what sits between it all. If it wasn't for the fact that google bungled an internal communication tool so badly, slack wouldn't even have to exist. For the life of me I cannot understand why they after a decade, has let slack and teams become basically a duopoly in this space. Source: I use…

Google Chat is definitely a product that could use more love, but it is situated in a specific internal landscape, and grows out of it. Slack is built for a very different context, and I doubt Google would build something like that. Google simply doesn't see the world the way someone who likes Slack would (and I also doubt a large co like Google could operate out of Slack).

Re: OpenAI should build Slack

#153
post #121

Google should build slack. Its a travesty how incredibly good their google workspace suite of tools is, and then google chat is what sits between it all. If it wasn't for the fact that google bungled an internal communication tool so badly, slack wouldn't even have to exist. For the life of me I cannot understand why they after a decade, has let slack and teams become basically a duopoly in this space. Source: I use…

Totally it is the biggest missing piece of their ecosystem and would complete their offering so nicely. Get a pm and 3 engineers and vibe it out

Wait

What exactly does Slack do that other chats don’t?

If you had to boil it down to 10 main features what is the point of this? Realtime chat seems to me to be distracting, and I much prefer threaded forums and issue trackers. But I’m willing to listen.

Re: OpenAI should build Slack

#154
post #121

Google should build slack. Its a travesty how incredibly good their google workspace suite of tools is, and then google chat is what sits between it all. If it wasn't for the fact that google bungled an internal communication tool so badly, slack wouldn't even have to exist. For the life of me I cannot understand why they after a decade, has let slack and teams become basically a duopoly in this space. Source: I use…

I hope I don't suffer from early onset Alzheimer's, but I seem to recall the joke pre the pandemic was that Google would constantly make new chat apps.

Google Dou, Google Chat, Google Wave, Google this, Google that. Seemingly because someone needed a promotion and the way to do that was to create a new chat app or lead the effort for the same.

Re: OpenAI should build Slack

#155
post #121

Google should build slack. Its a travesty how incredibly good their google workspace suite of tools is, and then google chat is what sits between it all. If it wasn't for the fact that google bungled an internal communication tool so badly, slack wouldn't even have to exist. For the life of me I cannot understand why they after a decade, has let slack and teams become basically a duopoly in this space. Source: I use…

Launch an internal hackathon. Everyone must use the latest Gemini coding models. Vote for the top 5 Chat/Productivity tools.

Eventually the culture will come around to: a) build new sh-- quickly with AI b) build a new productivity stack

Re: OpenAI should build Slack

#156
post #118

Earlier quoted context omitted.

You can't really do chat via rest, you need some kind of socket/sse for chat, otherwise all clients need to poll every second

It’s a good thing that Slack uses WebSockets! I think they even had the API for custom clients available, it’s only for Slack Apps now: https://docs.slack.dev/apis/events-api/using-socket-mode/ (And of course, way back then there was an official IRC interface, too)

Duh...

My comment was a response to

> Slack would be a lot better if they supported clients via rest api or similar.

Re: OpenAI should build Slack

#157
post #142

Earlier quoted context omitted.

Enterprise doesn't buy chat/meeting products without PSTN interop (dial-in dial-out to traditional phone line). Discord would probably need to double their dev team to add PSTN. Building something like Slack or Teams to the level that a F500 company would make it their primary videoconferencing solution is a multi-thousand-employee project. It's not a little skunkworks project for 15-20 people in some corner of the o…

> multi-thousand-employee project I know absolutely nothing about PSTN interop and I'm sure it's very complex to implement. However, at the end of the day, this is just software we're talking about right? Software is cheap and easy to produce these days and I doubt you need thousands of people to implement something that syncs your meeting's audio stream to a phone line especially given that it's a problem that has b…

Hardly. You're going from analog to digital and vice-versa. You probably need specialized appliances. For every country in the world. And it's "solved" but only in proprietary contexts; I don't think there's a standard. Then you need to operate it - you need SREs, bug fixes, keeping up with downstream changes etc.

Adding PSTN to Discord is absolutely a Discord-sized problem.

>Software is cheap and easy to produce these days

Yeah todo list apps

Re: OpenAI should build Slack

#158

Earlier quoted context omitted.

No one is claiming that level of productivity.

Oh yes they are. People are claiming 100x improvements, which is completely insane. But they do claim it.

OK sure, there are always lunatics on the fringe, but OP is casting that argument out as if they’re attacking a mainstream opinion.

Re: OpenAI should build Slack

#159
post #13
post #4

> Microsoft did, and Teams is by all reports a solid success. Not sure if the author has used Teams. But otherwise, I agree we need an actual good, adorable Slack clone. I thought Google might do this after not buying Slack, but I'm not hearing anything about their solution.

Teams is shovelware. Force bundled, with questionably reliable messaging, okay video calling (if your organization policies don't break it), and a fairly useless Phone System component that misbehaves often. Great for organizations that believe these forms of communication should be an afterthought that has rough edges and inconsistent reliability. The recent changes to end webhook support, kill Linux desktop support…

Direct webhooks have been removed but you can still use webhooks to send messages to Teams using PowerAutomate.

It's messier to set and maintain but it works as intended and also you can add more things to the workflow.

If you just want a URL to send json to, the new way is awful. But if you want to have more control, now you can.

Sometimes I like the PowerAutomate way, sometimes I hate it...

Post reply on HN