https://bugs.kde.org/show_bug.cgi?id=471526
Julius <julius.ber...@posteo.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |julius.ber...@posteo.de
--- Comment #2 from Julius <julius.ber...@posteo.de> ---
(In reply to Fushan Wen from comment #1)
> Git commit 2dc3455ad624f2e963b2d61405f38e770116dba4 by Fushan Wen.
> Committed on 28/06/2023 at 16:46.
> Pushed by fusionfuture into branch 'master'.
>
> wallpapers/potd: remove unsplash provider
>
> https://source.unsplash.com has been deprecated and doesn't work
> anymore. To use Unslash in needs a developer access key and use
> the https://api.unsplash.com
> FIXED-IN: 5.27.7
>
> M +0 -4 wallpapers/potd/package/contents/config/main.xml
> M +1 -149 wallpapers/potd/package/contents/ui/config.qml
> M +1 -4 wallpapers/potd/package/contents/ui/main.qml
> M +0 -3 wallpapers/potd/plugins/providers/CMakeLists.txt
> D +0 -46 wallpapers/potd/plugins/providers/unsplashprovider.cpp
> D +0 -26 wallpapers/potd/plugins/providers/unsplashprovider.h
> D +0 -48 wallpapers/potd/plugins/providers/unsplashprovider.json
>
> https://invent.kde.org/plasma/kdeplasma-addons/-/commit/
> 2dc3455ad624f2e963b2d61405f38e770116dba4
After reading the terms of the new developer access possibilities for unsplash,
I would think the KDE wallpaper engine might be a valid use case if used on a
personal basis. So why not enabling this integration with the possibility to
enter an API key and further use the feature, instead of completely removing
it? We could also talk to the Unsplash support to get some view of them on the
situation...
--
You are receiving this mail because:
You are watching all bug changes.
