←back to thread

410 points morsch | 1 comments | | HN request time: 0.289s | source
Show context
jeroenhd ◴[] No.43982964[source]
> SAF cannot be used, as it is for sharing/exposing our files to other apps

SAF can be used. There are reasons why this wouldn't be a good fit for NextCloud (you can't share your entire internal storage, your download folder, or the root of an SD card, for instance), but I don't think NextCloud's statement makes sense.

replies(3): >>43983014 #>>43983158 #>>43985264 #
jasonlotito ◴[] No.43985264[source]
Just to make sure: Google software has the same exact permission structure across the board? e.g. No Google product uses the same permissions NextCloud is seeking, and instead, they are using SAF? Especially for things that do what NextCloud is doing here.

I just want to be sure that Google is playing by the same rules they they put out for NextCloud and other app developers.

replies(3): >>43986860 #>>43987759 #>>43987858 #
1. zb3 ◴[] No.43986860[source]
Google is smart enough to not make things that obvious, but let's not get fooled.. the point is that if API changes would negatively impact Google products financially, they'd not go through. But if they impact a competitor, it's not an issue.

Locked down API means Google can innovate (because they can change the API), but you can't.