Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add feed of origin to inReplyTo elements?

Aperta
#15 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
35/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Tranquilla
Stack tecnologico
javascript
Ambito
backend-api-design

Direzione di ricerca

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.

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

Descrizione

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!

Lingua principale
JavaScript
Stelle
37
Fork
7
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

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

Tutte le issue di scripting/rss.chat

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.