Live data from Hacker News

Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

getdock.io

131–140 of 180 posts

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#131
post #7

> Free forever for teams up to 5. Unlimited search, unlimited history. I understand the strategic value of offering unlimited features to differentiate from competitors like Slack, might drive some amount of anxiety. Buyers may question long-term sustainability or fear undisclosed "shadow" caps. Since engineering limits are inevitable to prevent abuse (especially on free accounts), it might be better to set specific,…

Most people say their number one complaint is limited history. But then you offer that, and they realize it was not such a big deal. Slack still wins on so many levels that I don't see anyone willing to move any time soon.

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#132
Honest feedback: seeing the promise of 'free, forever' as a selling point on some early-adopter SaaS actually puts me off. It's a promise that is always broken. I don't buy it.

I also think that the marketing is pitched too heavily towards what Slack is, and what this product isn't. It's target towards someone who hates Slack rather than someone who wants the product for what it is, but most people who hate Slack are probably using it because their org says so, and their org doesn't think it sucks (because it has stuff like compliance and auditing and other legal what-have-yous).

Maybe I'd use it for some low-key personal thing, or maybe I'd just host an IRC server for the hell of it, but if I was running a startup I'd hold off on signing up until it matured a bit.

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#133
post #13

Unpopular opinion maybe, but 90 day memory loss is a feature, not a bug.

Sure, in some cases.

I have seen slacks for "former employees of $Company" where the house rules are that what is said should be taken as seriously and recorded as much as any remark said in a bar meetup. (i.e. not that seriously, not recorded). For these, not keeping old messages is a feature.

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#134

Earlier quoted context omitted.

> Feels like the more important question is how are you going to do all these things when Slack cuts you off I pay Slack $50k/year. They have no reason to shut me off. > or there is some new Slack policy that prevents it Prevents what exactly? The new API pricing they introduced doesn't apply to internal apps. I suppose they could apply it to internal apps. We'd have to figure out a path around it > or they increase…

> I pay Slack $50k/year. They have no reason to shut me off. They don't have to shut you off - but they've got every reason to raise the price. If they can bully you onto a $15/user/month 'Business Plus' plan, your 1000 clients would cost you $180,000 a year.

Every third party you contract with can pull the rug from under you this way, even this new startup with its 'forever free tier'.

You plan for it as a potential risk just like anything else and, if the time comes, you can work on migrating out. Companies will off board third parties all the time if the financials don't add up.

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#135
post #73

Personally if I'm going to start from scratch/square one I would want to pick something with the MS Teams model of forcing everything to be a "post" with threaded comments. Too much of Slack is wading through a mix of back-and-forth comments, proper threads, and DMs trying to piece together latest updates

we use the "chat" instead of "channel" feature precisely because forced threading makes it useless, so instead of chat channels everyone is using multi user chats... what a fucking mess

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#136
post #84

Earlier quoted context omitted.

I’m very puzzled by Google chat to be honest. It’s a massive missing piece in the Google workspace toolchest. Teams is the central place for companies on Microsoft, and arguably the most sticky part of the MS cloud productivity stack. So it can’t be lost on Google how important it is to have something here. Google slides, docs, sheets are fantastic products, but Google chat is so clunky and awkward that it seems hard…

History of Google text/voice/video chat is frankly insane, they refuse to just have a product and develop it, instead every few years the new thing pops up and the old thing gets deprecated. They should've been dominating the space for near 2 decades now. Instead they had Google Talk (that even worked over XMPP!) then replaced it with google hangouts, and then Google Chat.

And each iteration is basically worse.

XMPP should be able to be a Slack replacement.

Hangouts was a proprietary reimplementation, that had most of the features in an awkward way. Group chat in columns wasn't a great idea but was fine on mobile.

Duo/Chat was weird, separation of communication for no great benefit, and wasn't really any better than Hangouts. More like Hangouts that they had given to an intern to fix up, but forgot to tell them that it still needed to work with Hangouts.

Now we have Chat and Meet, Meet "replacing" Duo, while Duo is becoming Meet?

All I know is that after Hangouts finally was retired and replaced with Chat, they hid the chat tab in gmail, and required you to unhide it, and then appeared to disable notifications so I never knew when the last couple of people using it messaged me.

1/10. Wouldn't recommend.

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#137
post #85

Earlier quoted context omitted.

Really? Teams is the most sticky? Teams sucks. Excel and PowerPoint are the most sticky parts, and Teams just comes bundled with those.

I agree that Teams sucks, but speaking to people who are locked into the Microsoft environment, they love it.

I guess people love having a chat/videoconference tool available.

As for loving Teams ni particular compared to other solutions, I think it is far from the truth.

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#138
post #95
post #82

Earlier quoted context omitted.

If you had just downloaded Teams it would have worked fine. It isn’t Microsoft’s fault that Safari is a shit browser and the macOS people who keep it as their default won’t switch to something better.

... and that's how browser monopolies are formed. Your "something better" is certainly Chrome. But that's irellevant because the likes of teams and google chat are made for management and at best sales, while slack is made for engineers.

I ran Teams calls in Firefox on Linux for years, it worked as well as Zoom, I'd say. Other integrations, like the online office files had some issues. Didn't do chats there, though, only the meetings.

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#139
post #13

Unpopular opinion maybe, but 90 day memory loss is a feature, not a bug.

Sure, in some cases. I have seen slacks for "former employees of $Company" where the house rules are that what is said should be taken as seriously and recorded as much as any remark said in a bar meetup. (i.e. not that seriously, not recorded). For these, not keeping old messages is a feature.

I try to treat slack/teams/irc like the office water cooler. Sure, we can discuss work, make decisions or come up with solutions to problems, but it has to be recorded elsewhere, in an email or internal documentation or whatever for it to matter and for it to be official.

Nothing sucks as much as trawling through old chats to find some decision that was made ages ago.

Re: Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

#140
post #17
post #12

it seems like a product launching in this space in 2026 should have seamless and default e2ee for everything...

[dead]

it'll be exciting when someone finally demonstrates fully integrated, seamless and low-friction e2ee in a real-world application that is competitive in features and ease of use to traditional counterparts. i believe it would be challenging to get right, but is possible.
Post reply on HN