Do apps like Dropbox and OneDrive also have this problem?
Yeah, but Google's own apps are not subject to the same permissions - I'm fully expecting I would have no issues should I choose to enable Google Photos/Drive sync for things. Same for iCloud on iOS.I mean, this isn't surprising. These kinds of wide-ranging APIs are wide open for abuse so Google is locking them down, following in Apple's footsteps in some cases to make Android as locked down as iOS. It's kind of a natural outcome of trying to provide security to the "regular user" who has no understanding of security.
It doesn't sound like they hosed themselves; Google offered that as a service to the developer.Nextcloud, for anyone who's not familiar with it, is a FANTASTIC self-hosed alternative ...
Syncthing is great, I use it from F-Droid, so I actually can sync anything I want.A similar app called Syncthing also got booted off the Play Store for the same reason. I still have it on my phone and it's a fantastic Cloud-free way to backup my phone to my NAS, even over the internet.
Permissions are supposed to be laid in front of me and then I can make an educated decision whether to install it or not. Why is Google blocking useful apps that can compete with their Cloud Storage while allowing data-slurping malware masquerading as shopping apps and games on the store?
One of the problems WRT NextCloud is that it's a communications framework wrapper. You can enable all sorts of plugins to add different features, and those plugins are all created as individual open source (or not) projects. But it's the NextCloud app that gets signed.Yeah, but Google's own apps are not subject to the same permissions - I'm fully expecting I would have no issues should I choose to enable Google Photos/Drive sync for things. Same for iCloud on iOS.
In my opinion, both Google and Apple need a slap on the wrist with a morningstar - either put speed bumps for all apps(including yours) or let users decide to use different "OS-level" services than the ones you want them to use.
I'll grant that giving random apps wide-ranging permissions is a bad idea, but maybe we can take a page out of Windows's way of doing things? You need a certificate for your app, IIRC a paid one, and Microsoft can revoke it if you've been naughty.
For clarity, the on-device permission experience here is the same for Google's apps as it is for Nextcloud's. What Nextcloud is running into is that certain permissions need to be justified to Google before they'll let them into the app store at all. For example, the Android SDK and OS will let you write and sideload a RSS app that requests 24/7 background location access, but Google won't let it into the Play Store without submitting additional justification. The policy isn't unreasonable in itself, its just that its impossible to talk to an actual person at Google if they reject your explination.Yeah, but Google's own apps are not subject to the same permissions - I'm fully expecting I would have no issues should I choose to enable Google Photos/Drive sync for things. Same for iCloud on iOS.
I mean, this isn't surprising. These kinds of wide-ranging APIs are wide open for abuse so Google is locking them down, following in Apple's footsteps in some cases to make Android as locked down as iOS. It's kind of a natural outcome of trying to provide security to the "regular user" who has no understanding of security. One difference though is that Google resists provide human interaction in their support at all costs, whereas Apple is more happy to provide that, so when Google decides "you can't" it's often difficult to find a human who will change the decision.
While I generally agree - this is a good example of security being hard - it's hard to understate just how much of a feature the poor customer service is for them in circumstances like this. These are pretty big name apps (relatively speaking) that compete directly with a lot of Google's offerings. I have absolutely no doubt that their leadership considers this a win-win - tighten security for their product AND give them that fig leaf to cover clearing out a couple of competitors from easy access.I mean, this isn't surprising. These kinds of wide-ranging APIs are wide open for abuse so Google is locking them down, following in Apple's footsteps in some cases to make Android as locked down as iOS. It's kind of a natural outcome of trying to provide security to the "regular user" who has no understanding of security. One difference though is that Google resists provide human interaction in their support at all costs, whereas Apple is more happy to provide that, so when Google decides "you can't" it's often difficult to find a human who will change the decision.
Downloading and side-loading the Nextcloud app from the F-Droid external store and granting the app necessary permissions restores the ability to upload any files to a Nextcloud instance.
While I like the host-your-own-cloud idea, I'm too gun-shy about external access to my home storage to do it. So, I don't do "cloud". I'm never signed into Google for longer than it takes to do my business there, then I explicitly sign out, and delete the account on my phone (since it will still sign in for some functions even when I tell it not to).
I get that a lot of people don't exactly follow my example, and that's fine. It's their choice. I choose not to because the security headaches that come from opening up a direct pathway to your data is a hurdle I just can't emotionally take. I'm too distrustful of the technology (and I believe justifiably so, given how many breeches of data storage there seems to be) to implement it.
That said, it's pretty pissy of Google to hamstring competition.
Headline should be something along the lines of "Anti-trust violator violates anti-trust laws", because they're in a dominant position to make programs and features like this not work at all if they don't want them to. Making rules for thee, but not for me, that limits consumer choices is the epitome of monopolistic behavior.
Gonna bet this won't be remediated in the settlement about their antitrust behavior, either.
I've personally never been able to get NextCloud to function on UNRAID. That being said, I have not tried since 7 released with Tailscale support built in, so I may give it a go again.I'm a moderate user of Nextcloud and have the Android app installed, but I've never used it for auto-upload as I mainly use it to access files that come into my Nextcloud repository from elsewhere.
Still--this really chaps my ass.
Nextcloud, for anyone who's not familiar with it, is a FANTASTIC self-hosed alternative to a wide and growing number of cloud-based apps. It's trivially easy to set up and use and is only getting better with time.
Well... mostly better I guess.
It isn't using their servers to manage the user access, so it is local streaming as far as they're concerned. That's the downside to local streaming - you can create managed user profiles, but it's the same login and MFA. You have to set up a PIN to prevent other users from watching on your profile.(I think you could also use Tailscale to get around the new remote streaming charge on Plex, since it'd look to Plex like it's local network streaming.)
In the case of NextCloud (which I don't use because it's a massive overcomplicated monolithic mess just begging for bugs to creep in), the "server side" is typically owned and operated by the very person who owns and uses the client. And the data.So unlike Google and Apple, where they know exactly what code is going to run when someone enables access for their apps and services, if you enable full access for NextCloud, all it takes is enabling the wrong plugin server-side, and suddenly Bad Things can happen on the client.
I, not Google, own the "risk landscape" on my device. Period.This doesn't mean that just outright blocking full file access is the right way to go, but the risk landscape is vastly different in these cases, and it's going to be relatively complex to maintain the same level of security while opening access up to solutions like NextCloud.
FYI, the version on F-Droid is also no longer being updated, you should switch to "syncthing-fork"Syncthing is great, I use it from F-Droid, so I actually can sync anything I want.
Because Syncthing and co are competition that removes googles access to your data. That malware just increases googles power of users.A similar app called Syncthing also got booted off the Play Store for the same reason. I still have it on my phone and it's a fantastic Cloud-free way to backup my phone to my NAS, even over the internet.
Permissions are supposed to be laid in front of me and then I can make an educated decision whether to install it or not. Why is Google blocking useful apps that can compete with their Cloud Storage while allowing data-slurping malware masquerading as shopping apps and games on the store?
that’s… optimistic. Apple’s developer relations are atrocious. they never really did manage to scale their dev support to match the expanded base of developers when iphone went big. Apple is legendarily capricious during app review, and has earned itself a lot of enmity. Even die hard Apple supporters like John Gruber see the mess for what it is and been trying to bring attention to it for years.One difference though is that Google resists provide human interaction in their support at all costs, whereas Apple is more happy to provide that, so when Google decides "you can't" it's often difficult to find a human who will change the decision.
what you describe is a lot like iOS, where each sync service (even icloud) has its own separate data store location, and users can then choose to put files there or not. here’s mine:I dislike Google as much as anyone else here, but in this case it is Nextcloud being lazy and disingenuous.
There is a recommended way of creating the kind functionality that Nextcloud seeks to provide in android - by creating a document provider, which crucially does not require giving the app carte blanche to every file in the system.
The way it works is that the app gets a dedicated storage location in the local file system to store the files in user's cloud storage to be synced and available locally, and it integrates with system dialogs for opening/saving files. It's the same concept as Placeholder Files in Windows.
This is especially annoying to me as I'd love to host my own cloud storage, but Nextcloud's client expecting full filesystem access to work makes it a no go.
Google is stating security concerns as a reason for revoking the permission. This is hard to believe for us. Nextcloud has had this feature since its inception in 2016, and we have never heard about any security concerns from Google about it.
No, that's not it at all. What's being prevented here is using NextCloud to sync/backup arbitrary folders on the device. So if I have data in MyCoolApp and want to keep that says in NextCloud, I just point NextCloud directly to that folder.I dislike Google as much as anyone else here, but in this case it is Nextcloud being lazy and disingenuous.
There is a recommended way of creating the kind functionality that Nextcloud seeks to provide in android - by creating a document provider, which crucially does not require giving the app carte blanche to every file in the system.
The way it works is that the app gets a dedicated storage location in the local file system to store the files in user's cloud storage to be synced and available locally, and it integrates with system dialogs for opening/saving files. It's the same concept as Placeholder Files in Windows.
This is especially annoying to me as I'd love to host my own cloud storage, but Nextcloud's client expecting full filesystem access to work makes it a no go.
But what if I want to give NextCloud or Syncthing carte blanche access to every file in the file system so it can be effectively backed up automatically?There is a recommended way of creating the kind functionality that Nextcloud seeks to provide in android - by creating a document provider, which crucially does not require giving the app carte blanche to every file in the system.
[...]
This is especially annoying to me as I'd love to host my own cloud storage, but Nextcloud's client expecting full filesystem access to work makes it a no go.