In the other hand, as a home user I like to be able to install only one base system (Nextcloud) and use it for all of my online life. This will free me up from setting up yet another system (Mastodon etc) only to host my social networking needs.

And this is implemented as a separate app, so you can dismiss it if you don't need it.

Most of those features are optional. So if you don't care about some functionality just uninstall the specific 'App'. Sure that is not as secure as not having those Apps in the first place, but I think, in general, Nextcloud is moving into the right direction, as many of their use-cases require a tightly integrated but wide set of features.

> Most of those features are optional. So if you don't care about some functionality just uninstall the specific 'App'.

That's true, but unless there are new developers joining to create/support these apps the addition of these new features may spread the developers too thin. Personally I'd rather have a robust set of smaller features than a buggy implementation of a lot of features. The latter is okay if it's just a "for fun" type of project. But I use nextcloud to keep my calendar/contacts/file-sync, so it's really not okay if the core functionality is unstable. So while I can uninstall these apps, I personally worry that it means less attention will be paid to the core features.

That is like saying ice cream makers should focus on the 'core' tastes, claiming that that is banana and vanilla because you like those.

For you calendar and contacts are core for a file sync and share software? Above somebody also asked us to focus on 'core', meaning adding ACL's and probably dropping the calendar/contacts.

So it's like the fable where god decides to ask people what weather they want and everyone wants something different so he decides to go back to doing whatever the fuck he wanted. We just keep letting ourselves guided by contributors and customers...

> That is like saying ice cream makers should focus on the 'core' tastes, claiming that that is banana and vanilla because you like those.

From my point of view, I'm suggesting the ice cream makers should stop trying to make paninis to go with the ice cream and instead focus on making sure the ice cream cones don't have holes in the bottom.

I nearly lost all my files because server-side encryption went wonky. That's core functionality that should, imho, be fixed before going off into ActivityPub.

More generally, I have trouble being enthusiastic about "We added activitypub" focus because of what it seemed to do to MediaGoblin. That project seemed to be chugging along and making steady progress until it seemed they focused a lot of their energy into ActivityPub. Since then, MediaGoblin hasn't really had any of its functionality updated, as far as I can tell. They certainly don't seem to have released a new version in over 2 years.

All for avoiding Panini's, but we're a Content Collaboration Platform - and Nextcloud Social fits certainly well in that.

WRT server-side encryption, it gets work all the time, though it is mostly an enterprise feature that gets love when enterprises pay for that. Very few volunteers work on it, if any. Help is of course welcome, in the end - either somebody pays for it, or somebody puts in free time.

This is true for every open source project, of course.

WRT MediaGoblin, no worries, it isn't like Nextcloud Social has all our attention. I guestimate it is at most 5% of our engineering time, if that. That is enough to make it work and improve it release over release, and we'll put in more if there is customer interest or lots of community contributions, but we always start such new things small. Talk started as a night-long-hacking-to-prove-it-could-be-done and now has 3-4 engineers on it full-time, because customers want to pay for it. Which also means it doesn't take away from other things - if we didn't do it, we simply couldn't afford these engineers in the first place. It isn't like they would work on server-side encryption ;-)

Okay, that makes sense and makes me feel better about it. Thanks for responding and clarifying.