@FiXato for a long time, this was only possible in a way that wouldn't give decent backwards compatibility. This has been solved in XEP-0447, but still pending implementation experience: https://xmpp.org/extensions/xep-0447.html#body
@chfkch@fdroidorg That's not quite correct. #Mobifree subgrant projects must be related to the #Mobifree partner projects, that doesn't rule out projects useful to #LinuxMobile. Some ideas: - A free software driver for some phone hardware that can be used for @e_mydata and Linux Mobile. - Improvements to Ubuntu Touch or others that are beneficial to @delta, either @deltatouch or the regular Linux version. - Android-compatibility layers for Linux Mobile (e.g. an Android flatpak runtime).
@gamey Of course I do know Waydroid and improvements to it would likely also be covered (if they're beneficial to any of the #Mobifree apps).
With the flatpak runtime I was rather hinting at something that is better integrated, i.e. by having Android apps turned into Flatpak apps, using Flatpak permissions and sandboxing and so on.
Anyway, I was obviously just dumping ideas to clarify that a lot of things can be funded.
@gamey The binder kernel modules are required for Waydroid because of how Waydroid works. Maybe binder can be implemented in userspace or maybe there are ways to completely get rid of binder while maintaining compatibility with the majority of apps.
I currently don't have the capacity, but would be very much interested in this.