[11:08] <BluesKaj> Hiyas all
[18:51] <wxl> doesn't plasma have an appimage backend upstream???
[18:51] <wxl> s/plasma/discover/
[18:59] <RikMills> wxl: nope
[19:00] <wxl> https://news.softpedia.com/news/kde-plasma-5-16-desktop-promises-appimage-improvements-for-plasma-discover-more-525456.shtml ?
[19:03] <RikMills> wxl: I think they have confused appstream with appimage
[19:04] <wxl> RikMills: ah yes. thanks. do you know of any reason why NOT to support appimages?
[19:05] <RikMills> wxl: the reasons from here have not changed as afr as I know: https://pointieststick.com/2018/01/18/what-about-appimage/
[19:06] <RikMills> *as far
[19:09] <wxl> RikMills: and i think that's only partially true. appimages don't update themselves, and you can't find appimages through discover. in fact, there's no central place to find them.
[19:12] <wxl> RikMills: for example, consider nextcloud client. they primarily recommend an appimage (https://nextcloud.com/install/#install-clients) however when there's an update it says to "use the system's update tool to install it." except there isn't one. you have to go download it again. and if you wanted nextcloud to begin with, you couldn't just search and find it.
[19:13] <wxl> i guess that last problem is not something discover can help with, though.
[19:13] <wxl> the decentralization *IS* a problem in that case.
[19:14] <RikMills> sounds like they need to code it better and have build options for the appimage that make it suggest the right way to update