[FEATURE]: Hybrid Dynamic Trending Topics Engine

Aperta
#166 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
fastapi, next.js, python, redis, typescript
Ambito
ai, api, backend

Direzione di ricerca

Start by reviewing the Next.js 15 / Python 3.13 overhaul in PR #158 and the existing preset-topics.ts. The proposal outlines RSS ingestion, Groq evaluation, caching, and a /api/trending endpoint, but leaves prompt design, error handling, dependencies, and implementation details undecided. Done would require an agreed architecture and working live topics with a static fallback.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement
Feature and its Use Cases
Context

Following up on the Future Scope roadmap laid out in the recent Next.js 15 / Python 3.13 overhaul (PR #158). I am proposing the initial architecture to build the Hybrid Dynamic Trending Topics Engine to replace the static preset-topics.ts.

Proposed High-Level Architecture
  1. Ingestion Layer (FastAPI Background Task):
    Set up an autonomous scheduled job to fetch live RSS news feeds (Reuters, AP, Al Jazeera, etc.) periodically.
  2. Evaluation Pipeline (Groq LLM):
    Route fetched articles through a Groq-powered filtering prompt to evaluate editorial balance, controversy index, and relevance score.
  3. Caching Layer:
    Store the validated trending debate cards in-memory (or Redis) to ensure fast frontend retrieval without hitting the LLM on every page load.
  4. API Endpoint (/api/trending):
    Serve the cached topics to the Next.js frontend, with an automatic fallback to the static preset-topics.ts if the live feed fails.
Next Steps

This is a high-level architectural draft. Once assigned, I will dive deep and flesh this out into the best possible architecture, mapping out the exact prompt structures, error handling, and dependency requirements for the RSS parser.

I would love to take ownership of this feature for GSoC 2027. If the maintainers approve of this general direction, please assign this to me and I will start pushing the initial backend scaffolding!

Additional Context

No response

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Lingua principale
TypeScript
Stelle
58
Fork
90
Merge medio
11h 51m
PR unite (30g)
3

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AOSSIE-Org/Perspective

Tutte le issue di AOSSIE-Org/Perspective

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.