@fdroidorg@mastodon.technology here's a classic #Google tactic: use "open source" to get devs hooked, then gradually slip in proprietary bits. #AOSP's core apps move ever more towards proprietary, and they also do this with libraries like com.google.ar:core https://github.com/google-ar/arcore-android-sdk/issues/1538
@vesperto @eighthave @fdroidorg I wouldn't say it always works --- but it is definitely a common strategy! Wish there was a focus on copyleft-esque social domain licenses, (and more focus on hardware but thats another story lmao)
@vesperto @eighthave @fdroidorg I'm sometimes pondering possibilities of using the same EEE strategy in a "reverse" direction, i.e. for pulling people into Free Software. I'd love to try doing it esp. for email some day, but I think I might not have enough free time in my life for this, between work, peopleware, and other projects.
Email's probably the worse place to start (and thus the most needed):
I'd go with messengers.
@vesperto @eighthave @fdroidorg I wanted specifically to start with an email _client_ with some innovations I have on my mind, then possibly adding friendly encryption and also maybe transparently integrating other messenger systems. But, as I said, my ETA currently is +Infty... (Unless I somehow get to be financed to work on stuff like this. But even then some projects with a saner ETA are pragmatically higher on my list. In fact, planning a half-year sabbatical for one soon.)
@eighthave
@fdroidorg
Embrace, extend, extinguish – old tactic, always works.