Interested in your opinions on a #faircamp technical question:Faircamp currently has two different image processing backends:1. «image» (rust based), which does everything that's needed and (from all the feedback I get/got) works just fine. As faircamp itself is rust-based, this library integrates directly and smoothly in faircamp and requires no extra work or considerations for building/packaging (for me, or anyone).2. libvips (C/C++ based) – which is noticeably/significantly faster (but also not extremely so) and supports HEIF images (which the one above doesn't). This one, to my knowledge, also works very well for everyone, but requires somewhat significant extra work and considerations for building/packaging (for me and everyone).In general, the fact that both image processing backends exist incurs some overhead as well, but as that's mostly set up and working, it's not dramatic either.I expect that «image» will more or less catch up with libvips in terms of speed and format support eventually, then it will obviously be a no-brainer to go just with that single backend. The sooner that change is made though, the less overhead is lost in the project (which frees development time :)), so I'm wondering if it's already time to make the change.What do you think?

@theargentgrub Thanks, that's very kind of you. Makes me think about an english version...

Fun update: I made an app over the holiday break! It’s called Unstream: Find your favorite music on alternative platforms, directly support the artists you love, and move off streaming. It was directly borne out of my desire to get off Apple Music myself, and instead build a library of music I own through directly supporting artists by buying their music.You can check it out here, at a URL I still find amusing: https://unstream.stream#indiemusic #faircamp #bandcamp #music #streaming