[FEATURE]: Hybrid Dynamic Trending Topics Engine

Abierto
#166 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
fastapi, next.js, python, redis, typescript
Área
ai, api, backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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
Lenguaje dominante
TypeScript
Estrellas
58
Forks
90
Merge medio
11 h 51 min
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AOSSIE-Org/Perspective

Todos los issues de AOSSIE-Org/Perspective

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.