extend UnsplashBridge

[langfingaz]

Thanks @nel50n for his UnsplashBridge! The commit is mainly based on his work.

As I this new bridge is based on UnsplashBridge.php, I left the MAINTAINER in line 6 to @nel50n . What do you think, shall I change this to me or leave it as is?

Signed-off-by: langfingaz [email protected]

[langfingaz]

In this bridge one can "follow" a username on https://unsplash.com receiving new images.

Here is one example of a running rss-bridge instance with this bridge enabled: https://rss.privacy1st.de/?action=display&bridge=UnsplashUser&u=h4mmiidd&m=20&w=1920&q=75&format=Html

[langfingaz]

And I'm not sure, but maybe one could merge this bridge into the already existing UnsplashBridge so that one can select if one would like to get the latest unsplas images or new images from a specific user. Help or ideas on how to do this are welcome!

[em92]

I left the MAINTAINER in line 6 to @nel50n . What do you think, shall I change this to me or leave it as is?

Generally speaking, if you are making new bridge, you should set MAINTAINER to yourself.

And I'm not sure, but maybe one could merge this bridge into the already existing UnsplashBridge

You can add param like "Filter by Username (optional)" or "Username (optional)" and defaultValue = "". Then you can change api source depending if this param is given.

[langfingaz]

You can add param like "Filter by Username (optional)" or "Username (optional)" and defaultValue = "". Then you can change api source depending if this param is given.

All right, I did some more work on the UnsplashBridge and merged my new UnsplashUserBridge into the already existing UnsplashBridge.

Generally speaking, if you are making new bridge, you should set MAINTAINER to yourself.

And I'm now added as second MAINTAINER.

---

You can test the modified UnsplashBridge here: https://rss.privacy1st.de

[em92]

Hi, @langfingaz ! Could you please rebase your PR?

I have recently fixed Travis CI. It runs some tests and linting checks.

[langfingaz]

Well, I'm sorry that I somehow failed rebasing my changes... The master branch of my forked repo is now 26 (and not 3) commits ahead of RSS-Bridge:master.

I created a branch langfingaz/unsplash which is 3 commits ahead of RSS-Bridge:master.
Probably it better to create a new pull request from within that branch and close this pull request to keep it cleaner?

Sorry for the inconvenience.