RSS-Bridge / RSS-Bridge/rss-bridge
Platinmods.com
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 9.2k
- Forks
- 1.2k
- Avg merge
- 12h 45m
- Merged PRs (30d)
- 2
Description
Bridge request
General information
-
Host URI for the bridge (i.e.
https://github.com): https://platinmods.com -
Which information would you like to see?
I would like to be able to see the list of last tested apps here:
https://platinmods.com/advancedsearch/advancedsearch-results?type=thread&keywords=&posted_by=&search_forums%5B%5D=156 -
How should the information be displayed/formatted?
Formated like in the result on the site -
Which of the following parameters do you expect?
- Title
- URI (link to the original article)
- Author
- Timestamp
- Content (the content of the article)
- Enclosures (pictures, videos, etc...)
- Categories (categories, tags, etc...)
Options
- Limit number of returned items
- Default limit: 5
- Load full articles
- Cache articles (articles are stored in a local cache on first request): yes
- Cache timeout (max = 24 hours): 24 hours
- Balance requests (RSS-Bridge uses cached versions to reduce bandwith usage)
- Timeout (default = 5 minutes, max = 24 hours): 5 minutes
Of course It would be even better to be able to enter search parameters but for the moment this is what I need.
Contributor guide
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.
Research direction
Start by inspecting the requested Platinmods.com advanced-search URL and review existing RSS-Bridge implementations for similar forum listings. The bridge should expose the requested results with title, original URI, author, timestamp, content, and categories, while balancing requests with the stated five-minute timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100