Feeds get new URLs
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- aws, javascript, sql
- Domain
- backend, databases, documentation
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- JavaScript
- Stars
- 37
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scripting/rss.chat
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in scripting/rss.chat
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
avniproject/avni-client#2135 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
babalae/bettergi-scripts-list#3674 ·
-
A-Release-Notes C-Editing D-Modest S-Ready-For-Implementation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bevyengine/bevy-website#2595 ·
-
ecosystem wording
Difficulty 1/5 Under an hour Newbie friendliness 90/100
matrix-org/matrix.org#3649 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vadimdemedes/ink#1029 ·