Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Add feed of origin to inReplyTo elements?

Abierto
  • ¿Algo no está bien?
#15 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Tranquilo
Stack tecnológico
javascript
Área
backend-api-design

Línea de trabajo

No source files or tests are named. Start by reading the existing source:inReplyTo proposal and the repository's RSS 2.0 client and server handling; done requires agreement on whether and how an originating feed link should be represented, plus a defined implementation and test scope.

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

Descripción

Hi there @scripting (et al) 👋 I'm loving all this activity around rss.chat 👌

I'm working on adding support for source:inReplyTo elements in HyperTexting (https://hypertexting.com) and it occurs to me that these elements could represent a new discovery surface for RSS clients if they carried a link to the feed the source:inReplyTo item originates from.

<source:inReplyTo xmlUrl='https://example.com/rss.xml'>https://example.com/2026/05/16/hello-world.html</source:inReplyTo>

NOTE: I don't have a strong opinion about the attribute name, so I used the OPML Subscription List xmlUrl attribute name here as an example.

If I'm following the source:inReplyTo proposal correctly, source:inReplyTo elements should always point to an item in a feed, even if that item only has a GUID and not a permalink URL; in other words source:inReplyTo should never point to a URL that didn't originate from a feed (e.g. https://apple.com).

If that's true, traditional RSS reader clients that want to add support for source:inReplyTo elements could start by showing a link to open source:inReplyTo URLs in a browser (this sounds kinda clunky to me, but at least you're only one click away from the OP context), but they won't be able to do anything with source:inReplyTo elements that are isPermalink='false'. However, if source:inReplyTo elements carried a link to the originating feed, clients could fetch that feed in order to display non-permalink content (e.g. if the referenced GUID is still accessible in the feed); they could also display "follow" or "subscribe" buttons if the client is not already following the referenced feed. The latter would effectively introduce a new discovery surface for RSS which is pretty exciting!

Lenguaje dominante
JavaScript
Estrellas
37
Forks
7
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 scripting/rss.chat

Todos los issues de scripting/rss.chat

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.