Why is Slack allowed to get away with lying?
The article discusses concerns about Slack's uptime claims and their accuracy. It contrasts Slack's server-first approach with Ano's local-first design, which aims for better performance and reliability. The author advocates for more transparency regarding uptime metrics.
- ▪Slack's uptime claims have been criticized for not being accurate.
- ▪Ano is designed with a local-first approach to improve performance.
- ▪The author calls for greater transparency in uptime reporting.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Ycombinator |
| Canonical URL | https://news.ycombinator.com/item?id=48301850 |
| Publication time | Wed, 27 May 2026 22:52:05 +0000 |
| Retrieval time | 2026-05-27T23:08:06.186Z |
| Last seen | 2026-05-27T23:08:06.186Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | W0-QGQYN8pmR |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Agree, it's not really a true representation for most of us - Slack uptime. Since Slack is server-first, it becomes apparent if the server serving you is down.When we built Ano (https://ano.chat), we focused on local-first, meaning only mutations are streamed to the client - less data, optimistic writing and faster all around.I vote for transparent uptimes!
Excerpt limited to ~120 words for fair-use compliance. The full article is at Ycombinator.