This is not to say we haven't been actively looking at ways we can open up or become compliant with a few of the open protocols that already exist as long as it fits with the personal privacy we want for our users on top of the data privacy.
This is not to say we haven't been actively looking at ways we can open up or become compliant with a few of the open protocols that already exist as long as it fits with the personal privacy we want for our users on top of the data privacy.
That said, it's a similar problem with DuckDuckGo: how do we know they're respecting users' privacy? DDG has it easy, since they're a search engine; absolutely nothing about their product requires storing any info about their users whatsoever, and thus (as far as anyone knows, and as far as they say) they don't. Slyde, however, is a social network, which makes the collection and storage of data much harder (if not impossible) to avoid.
Another huge help on the transparency front would be to at least ensure the source code for any apps is publicly available. Even if not necessarily under a FOSS license (though that'd be a bonus), the apps being as easy as possible to independently audit would alleviate a lot of my own concerns with these sorts of social networking apps doing scummy things like using the microphone for ad targeting.