Feedback on landing page for fosbury.ai (Team Chat)?
Introducing Fosbury The more enjoyable, more efficient way for product teams to communicate. How a team communicates decides how fast it moves and whether the work is any good. Yet the leading tools were designed over a decade ago, for an office where everyone sat in the same room on the same clock — one endless stream, everyone present, newest at the bottom.
- ▪Introducing Fosbury The more enjoyable, more efficient way for product teams to communicate.
- ▪How a team communicates decides how fast it moves and whether the work is any good.
- ▪Yet the leading tools were designed over a decade ago, for an office where everyone sat in the same room on the same clock — one endless stream, everyone present, newest at the bottom.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,495 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 | Fosbury |
| Canonical URL | https://fosbury.ai/ |
| Publication time | Tue, 11 Aug 2026 16:53:00 +0000 |
| Retrieval time | 2026-08-11T17:10:44.258Z |
| Last seen | 2026-08-11T17:10:44.258Z |
| 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 | T2J25nEGlJhQ · 1 stories |
| 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
Introducing Fosbury The more enjoyable, more efficient way for product teams to communicate. How a team communicates decides how fast it moves and whether the work is any good. Yet the leading tools were designed over a decade ago, for an office where everyone sat in the same room on the same clock — one endless stream, everyone present, newest at the bottom. It is rare to find a top product company that truly works asynchronously, yet nearly all of them describe themselves that way. The app is still open all day and the pings still arrive. 01Speed and zero friction. Keyboard-first, and instant. 02Structure by default. Every thread has an owner, a state and an end. 03Async by default. Nothing rewards you for being online. The name is borrowed.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Fosbury.
Discussion
0 commentsMore from Fosbury
