[winkeltripel]

9 years of the api working, then Google shuts them down. I expect an interface to be consistent after working for 9 years.

I think they're trying to keep their story simple, for the sake of clarity. I believe the nextcloud team when they say they need the permission.

Part of the issue is that nextcloud has many use cases, including ones where your files don't get synced to your mobile device until you touch the file, replacing them with a reference to a file. It's cool cause you can access and manage a tb of pictures or documents from a 64gb android.

[deng]

> I believe the nextcloud team when they say they need the permission.

I don't (and I do use NC). The sentence "SAF cannot be used, as it is for sharing/exposing our files to other apps" is simply wrong and llm_nerd is right that SAF should be able to handle that use case,see

https://developer.android.com/training/data-storage/shared/d...

There are some restrictions regarding which directories you can access, but for most use-cases it should be perfectly fine. It's also not that this should come as a surprise to them. In fact, there's an issue about this from the NC team themselves from August '22:

https://github.com/nextcloud/android/issues/10123

Why they still think SAF cannot be used is a mystery to me.

[threeseed]

> I expect an interface to be consistent after working for 9 years

Even if that interface is insecure and harmful to users ?

As an industry we've learnt a lot about how apps siphon and sell your data. And I appreciate this probably doesn't apply to NextCloud but it can be difficult to build an API that is flexible and secure so you will get casualties.

[lenkite]

How is this interface "insecure and harmful to users" ?