Feeds get new URLs
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Documentación
- Claridad
- Necesita aclaración
- Estado de actividad
- Tranquilo
- Stack tecnológico
- aws, javascript, sql
- Área
- backend, databases, documentation
Línea de trabajo
Start with server/docs/install.md and the old and new feed URLs listed in this issue. Verify how feed storage, serving, and redirects are documented; done means the installation guidance reflects the SQL-backed URLs and explains the old-URL polling behavior.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
On both rss.chat and demo.rss.chat we changed how we save and serve RSS 2.0 feeds and the OPML list of all users and their feeds.
- If you haven't subscribed to a feed, there's nothing you need to do.
- We used to use Amazon S3, now we store them in a new table in the SQL database.
- Serving should be just as fast.
- We made this change because it eliminates a complex step in the process of starting a new instance. We want to make it as easy as possible and this was one of the hardest things on the list. And we felt we had to do this ASAP, it becomes a more difficult transition as we go forward.
- We redirected from the old URLs to the new ones. So the old ones still work, but you won't get the instant rssCloud-based update this way. Your reader app will have to poll to get the update.
Example 1
Example of an old URL: https://users.rss.network/rss.xml (the everyone feed, contains every person's posts)
Example of the new URL: https://rss.chat/users/rss.xml
What you should do: Unsub from the old URL and subscribe to the new one.
Example 2
Example of an old URL: https://users.rss.network/dave/rss.xml (the feed for my posts only)
Example of the new URL: https://rss.chat/users/dave/rss.xml
What you should do: Unsub from the old URL and subscribe to the new one.
If you have questions please post them here.
- Lenguaje dominante
- JavaScript
- Estrellas
- 37
- Forks
- 7
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de scripting/rss.chat
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 84/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
Todos los issues de scripting/rss.chat
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
avniproject/avni-client#2135 ·
-
automated broken-link
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
-
agent/security hive/hosted-available-lke648397-260827-5n31 security
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
bevyengine/bevy-website#2595 ·