Preparing for scoped storage (Android Dev Summit '19)
Android DevelopersCited 4× on HN, 2020-2025
85K views · 7 years ago · talk · dated
A 2019 Android Dev Summit session on the scoped storage model in Android 10. It gives a plan overview and best practices for apps adapting to the new restrictions.
Cited as the official explanation of Google's scoped storage changes and its intent to limit broad file access.
35:31June 2021 FreeBSD Developer Summit: Raid-Z Expansion
FreeBSD
4K views • 5 years ago
34:00User-level threads....... with threads. - Paul Turner - Google
Linux Plumbers Conference
41K views • 13 years ago
1:16:58code::dive conference 2014 - Scott Meyers: Cpu Caches and Why You Care
NOKIA Technology Center Wrocław
231K views • 11 years ago
12:39I Hope Google Doesn’t Ban Us... - Abusing Unlimited Google Drive
Linus Tech Tips
5.8M views • 8 years ago
32:30Benno Rice: The Tragedy of systemd -- BSDCan 2018
BSDCan
25K views • 8 years ago
1:14:19NYC Tech Talk Series: How Google Backs Up the Internet
Google TechTalks
41K views • 12 years ago
1:10:02Building Software at Google Scale Tech Talk
Google TechTalks
58K views • 14 years ago
33:53Linux for Chromebooks: Secure Development (Google I/O ’19)
Chrome for Developers
239K views • 7 years ago
58:36Advanced Topics in Programming Languages: A Lock-Free Hash Table
GoogleTalksArchive
29K views • 14 years ago
47:18The Tragedy of systemd
linux.conf.au
1.3M views • 7 years ago
1:01:34Google I/O 2008 - Dalvik Virtual Machine Internals
Google for Developers
188K views • 18 years ago
42:20"Stop Rate Limiting! Capacity Management Done Right" by Jon Moore
Strange Loop Conference
41K views • 9 years ago
1:25:25OpenZFS Office Hours with Matt Ahrens
OpenZFS
0 views • 13 years ago
56:19MINIX 3: a Modular, Self-Healing POSIX-compatible Operating System
FOSDEM
90K views • 16 years ago
1:12:02Java on a 1000 Cores - Tales of Hardware / Software CoDesign
Google TechTalks
23K views • 17 years ago
1:45:47Bryan Cantrill on Jails and Solaris Zones
PapersWeLove
34K views • 10 years ago
53:0236C3 - A systematic evaluation of OpenBSD's mitigations
media.ccc.de
18K views • 6 years ago
34:51Capsicum: Practical Capabilities for UNIX
USENIX
11K views • 16 years ago
30:50Why Google Stores Billions of Lines of Code in a Single Repository
@Scale
317K views • 11 years ago
40:18"Compacting the Uncompactable" by Bobby Powers
Strange Loop Conference
29K views • 7 years ago
4 comments from Hacker News
I'm guessing it was back ported to Android 4.4, so it probably hasn't been available quite that long. (Update: Nevermind, looks like it was in the initial 4.4 release: link ) But they've definitely been warning about the pending API change since at least 2019: ▶ this video The devs in the comments of that video do have some valid complaints about the added complexity of not being able to use the standard Java filesystem APIs anymore with the new permissions model, but still, it has been 6 years.
This is a bit surprising in 2024 (well almost 2025). Android has a really nice API for reducing the need for this permission, and most of it has been around sicnce android 10. ▶ this video Maybe the author is not aware of these? How about opening an issue?
syncthing is an incredible piece of software. It should be noted that: * "Security" changes in recent versions of Android seem designed to kill use cases like syncthing. See links below. * There is no iOS version, as near as I can tell because iOS is already where Android is headed. The crux of the problem is syncthing is a single golang binary, but the only way to manage filesystem permissions on iOS (and now Android) is through tightly controlled OS dialogs, and there is no way to do this from golang. There aren't even NDK APIs for it. The closest thing Android is providing to an escape hatch is "all files access" [5], for which your app has to go through an approval process in order to be put on the play store. If you watch [2], GOOG makes it very clear that they want to minimize the number of apps that obtain this permission. It's unclear to me whether apps installed through FDroid or side-loaded will be able to use that permission at all, or if the APKs must be signed. I'm all for improved security, but never at the cost of controlling what I am ABLE to do with my computer. It's sad that our operating systems are turning into gatekeepers between developers/users and the hardware they "own". [0]: link [1]: link [2]: ▶ this video [3]: link [4]: link [5]: link
Disclaimer: I'm not really an Android developer. I was considering implementing a service I'm working on for Android and after many hours of research determined it's not a suitable operating system for my purposes. Personally I no longer consider Android a viable computing platform. As a developer you simply don't have the tools available to give your users control over their data and experience. With the changes to storage security the last couple years, they've essentially dumbed it down to the level of a web browser, and in the process pretty much deprecated running native (C, C++, Rust, Golang, etc) applications. I'm not opposed to improving security, but when you can't even run software like syncthing or a file explorer without getting special Play store approval, something is wrong. I've been meaning to write a blog post summarizing what I learned. This official video is actually a pretty good summary of some the changes made and what the goal is: ▶ this video