bf9946d1fc
* Group common selectors * Fix indentation using tabs * Use same styles for number and text inputs * Use grid layout for parameters Introduces the grid layout for bridge parameters. All parameters are arranged in a grid to improve readability. Read more on grid layouts at - https://www.w3schools.com/css/css_grid.asp - https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout Notice: Grid layouts are not supported in very old browser versions: https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout/CSS_Grid_and_Progressive_Enhancement This is why @supports checks for browser support (not supported in IE) https://developer.mozilla.org/en-US/docs/Web/CSS/@supports#Browser_compatibility In case grid layout is not supported, the displayed form is usable but not very pretty due to <br> being removed by this commit for cosmetic reasons (breaks grid layout). Unfortunately it doesn't seem possible to insert line breaks manually via '::after { content: '\A' }' in cases where grid layout isn't supported. * Add padding to card parameters Adds padding to parameters to improve readability. For bridges without parameters (count($parameters) === 0), the parameter 'div' is no longer created. * Add colon ':' after label via CSS * Capitalize first letter of label for readability * Fix checkbox isn't aligned left Sets the size of the checkbox to 20x20 px for good measure. * Harmonize formatting * Add new style to number and select boxes References #797 * Add fallback solution for browsers without grid support |
||
---|---|---|
bridges | ||
cache | ||
caches | ||
formats | ||
lib | ||
static | ||
tests | ||
vendor | ||
.dockerignore | ||
.gitattributes | ||
.gitignore | ||
.travis.yml | ||
CHANGELOG.md | ||
config.default.ini.php | ||
CONTRIBUTING.md | ||
Dockerfile | ||
index.php | ||
phpcs.xml | ||
phpunit.xml | ||
README.md | ||
scalingo.json | ||
UNLICENSE |
rss-bridge
rss-bridge is a PHP project capable of generating ATOM feeds for websites which don't have one.
Supported sites/pages (main)
Bandcamp
: Returns last release from bandcamp for a tagCryptome
: Returns the most recent documents from Cryptome.orgDansTonChat
: Most recent quotes from danstonchat.comDuckDuckGo
: Most recent results from DuckDuckGo.comFacebook
: Returns the latest posts on a page or profile on FacebookFlickrExplore
: Latest interesting images from FlickrGooglePlus
: Most recent posts of user timelineGoogleSearch
: Most recent results from Google SearchIdenti.ca
: Identica user timeline (Should be compatible with other Pump.io instances)Instagram
: Most recent photos from an Instagram userOpenClassrooms
: Lastest tutorials from fr.openclassrooms.comPinterest
: Most recent photos from user or searchScmbBridge
: Newest stories from secouchermoinsbete.frThePirateBay
: Returns the newest indexed torrents from The Pirate Bay with keywordsTwitter
: Return keyword/hashtag search or user timelineWikipedia
: highlighted articles from Wikipedia in English, German, French or EsperantoYouTube
: YouTube user channel, playlist or search
Plus many other bridges to enable, thanks to the community
Output format
Output format can take several forms:
Atom
: ATOM Feed, for use in RSS/Feed readersHtml
: Simple html page.Json
: Json, for consumption by other applications.Mrss
: MRSS Feed, for use in RSS/Feed readersPlaintext
: raw text (php object, as returned by print_r)
Screenshot
Welcome screen:
RSS-Bridge hashtag (#rss-bridge) search on Twitter, in ATOM format (as displayed by Firefox):
Requirements
- PHP 5.6, e.g.
AddHandler application/x-httpd-php56 .php
in.htaccess
openssl
extension enabled in PHP config (php.ini
)curl
extension enabled in PHP config (php.ini
)
Enabling/Disabling bridges
By default, the script creates whitelist.txt
and adds the main bridges (see above). whitelist.txt
is ignored by git, you can edit it:
- to enable extra bridges (one bridge per line)
- to disable main bridges (remove the line)
- to enable all bridges (just one wildcard
*
as file content)
New bridges are disabled by default, so make sure to check regularly what's new and whitelist what you want!
Deploy
Authors
We are RSS Bridge Community, a group of developers continuing the project initiated by sebsauvage, webmaster of sebsauvage.net, author of Shaarli and ZeroBin.
Patch/contributors :
- Yves ASTIER (Draeli) : PHP optimizations, fixes, dynamic brigde/format list with all stuff behind and extend cache system. Mail : contact /at\ yves-astier.com
- Mitsukarenai : Initial inspiration, collaborator
- ArthurHoaro
- BoboTiG
- Astalaseven
- qwertygc
- Djuuu
- Anadrark
- Grummfy
- Polopollo
- 16mhz
- kranack
- logmanoriginal
- polo2ro
- Riduidel
- superbaillot.net
- vinzv
- teromene
- nel50n
- nyutag
- ORelio
- Pitchoule
- pit-fgfjiudghdf
- aledeg
- alexAubin
- cnlpete
- corenting
- Daiyousei
- erwang
- gsurrel
- kraoc
- lagaisse
- az5he6ch
- niawag
- JeremyRand
- mro
Licenses
Code is Public Domain.
Including PHP Simple HTML DOM Parser
under the MIT License
Technical notes
- There is a cache so that source services won't ban you even if you hammer the rss-bridge with requests. Each bridge can have a different duration for the cache. The
cache
subdirectory will be automatically created and cached objects older than 24 hours get purged. - To implement a new Bridge, follow the specifications and take a look at existing Bridges for examples.
- To enable debug mode (disabling cache and enabling error reporting), create an empty file named
DEBUG
in the root directory (next toindex.php
). - For more information refer to the Wiki
Rant
Dear so-called "social" websites.
Your catchword is "share", but you don't want us to share. You want to keep us within your walled gardens. That's why you've been removing RSS links from webpages, hiding them deep on your website, or removed feeds entirely, replacing it with crippled or demented proprietary API. FUCK YOU.
You're not social when you hamper sharing by removing feeds. You're happy to have customers creating content for your ecosystem, but you don't want this content out - a content you do not even own. Google Takeout is just a gimmick. We want our data to flow, we want RSS or ATOM feeds.
We want to share with friends, using open protocols: RSS, ATOM, XMPP, whatever. Because no one wants to have your service with your applications using your API force-feeding them. Friends must be free to choose whatever software and service they want.
We are rebuilding bridges you have wilfully destroyed.
Get your shit together: Put RSS/ATOM back in.