An LLM-Turbocharged Community Calendar Reboot (2024)
Back in the 2010s I created a system to aggregate public calendars for cities and towns. The Elm City project, as it was called, never gained traction, but the problem it addressed remains unsolved. Calendars of public events are information silos; there’s still no good way to combine them.
- ▪Back in the 2010s I created a system to aggregate public calendars for cities and towns.
- ▪The Elm City project, as it was called, never gained traction, but the problem it addressed remains unsolved.
- ▪Calendars of public events are information silos; there’s still no good way to combine them.
Hacker News (AI / LLM) files mainly under ai. We currently carry 5,143 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 | The New Stack |
| Canonical URL | https://thenewstack.io/an-llm-turbocharged-community-calendar-reboot/ |
| Publication time | Wed, 16 Sep 2026 11:13:12 +0000 |
| Retrieval time | 2026-09-16T11:18:41.532Z |
| Last seen | 2026-09-16T11:18:41.532Z |
| 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 | XoU2k8JqxPoV · 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
Back in the 2010s I created a system to aggregate public calendars for cities and towns. The Elm City project, as it was called, never gained traction, but the problem it addressed remains unsolved. Calendars of public events are information silos; there’s still no good way to combine them. I wondered how effectively my team of LLM assistants could help me reboot that community-scale calendar aggregator. It turned out to be a shockingly fast speed run; here are the highlights. RSS for Calendars The inspiration for the original project was the blogosphere: a network of RSS publishers, readers, and aggregators. Why not build an analogous network where publishers, readers, and aggregators exchange iCalendar feeds? The poster child for this idea was Google Calendar.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The New Stack.
Discussion
0 commentsMore from The New Stack
