mruac

@Dinth I have manually merged their feature into my own branch: https://github.com/mruac/mruac-rss-bridge/tree/add-url-encryption You may be able use the Dockerfile included with the repo - though I have not tested it...

> I tried this but I think it's not the right way: (I write the desiredvalues harcoded for my tests.) You are close, you need to pass in the cookie(s)...

you can create your own that modifies an existing feed before it is served with the [`FeedExpander`](https://rss-bridge.github.io/rss-bridge/Bridge_API/FeedExpander.html) class. You'll need to host your own instance of RSS-Bridge though.

[FeedMe](https://play.google.com/store/apps/details?id=com.seazon.feedme) still in active development and dev is responsive

potentially a feature request if not implemented already

I could just do this in the bridge, but it doesn't feel right... ```php header("Location: https://www.example.com", true, 301); exit(); ``` The url could be tightened to only allow existing bridge...

proposing adding this this in `./lib/utils.php` ```php function redirectBridge($parms){ header('Location: ' . get_home_page_url() . '?' . http_build_query($parms), true, 301); exit(); } ``` A bridge can detect unsupported parameters with the...