RSS-Bridge / RSS-Bridge/rss-bridge
Bridge request for xcancel.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://xcancel.com/- It's a foss front-end alternative to X/Twitter (most stable public instance of Nitter with 99.99% uptime https://github.com/zedeus/nitter)
- So for instance, to have the X account of CNN you'd use the X/Twitter handle of CNN which is @cnn and you would simply type https://xcancel.com/CNN compared to the regular url on X https://x.com/CNN
- Syntax: You replace x.com -> xcancel.com with everything else being equal
- The input/option settings for that bridge would be exactly the same as the existing RSS Bridge for Twitter.
-
Which information would you like to see? This is a foss instance of twitter/X so the usual X posts
- Title
- URI (link to the original article)
- Author
- Timestamp
- Content (the content of the article)
- Enclosures (pictures, videos, etc...)
- Categories (categories, tags, etc...)
-
How should the information be displayed/formatted?
Same as the Twitter/X posts (see above) -
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 : 24 hours
- Balance requests (RSS-Bridge uses cached versions to reduce bandwith usage)
- Timeout (default = 5 minutes): 5 minutes
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 comparing the existing RSS Bridge for Twitter with xcancel.com and its profile URL format. Confirm how the requested post fields and options map to the existing Twitter bridge, then verify that the new bridge produces the expected feed for an xcancel profile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100