4 ms·

> Last I checked, Google had registered something over 3 billion Android user identities. Relying on that large a population to 1) trust individual software aut

> Last I checked, Google had registered something over 3 billion Android user identities. Relying on that large a population to 1) trust individual software authors with 2) no specific code of conduct or review process and 3) have a high level of familiarity with permissions systems, architectures, and peculiarities of specific releases strikes me as a good working definition of "unreasonable expectations". What would the alternatives be (given 3 billion user identities)?

dredmorbius 11y ago
A system far more like Debian's in terms of app development/provisioning, and user-centric protections. A dev-compensation system not dependent on advertising. https://plus.google.com/104092656004159577193/posts/2eg1rG6kmJp https://plus.google.com/104092656004159577193/posts/2eg1rG6k...
- fixermark 11y ago
  Sorry to say: Debian's has advantages, but is a pain in the ass. The focus on security and reliability in packages means both stable and unstable tend to be so far behind head that I rarely find things I want to try are directly supported by the available binaries. Which is not to say Debian's approach is bad for its purposes; I just wouldn't want to use a smartphone app ecosystem designed like that. Advertising is trickier to wrestle down. I'm not sure in an ecosystem where advertising is allowed, a race to the bottom isn't to be expected, and best of luck banning it entirely.
  - dredmorbius 11y ago
    Rather than respond to what you think I might have written, how about actually reading the suggestion and responding to its points. This would be more valuable to both of us.
    - fixermark 11y ago
      People only ever respond to what they think other people have written; such is the nature of communication. If you mean respond to the multi-paragraph G+ post: too many pieces to dedicate time to at this juncture. I misunderstood what you meant by the Debian model "in terms of app development" to refer to package creation / maintenance approach. If you mean these three elements: Putting user interests first Seeing specific limitations on app capabilities Promoting Free Software in all possible cases ... Then I think from Google's standpoint, it's probably understood that they are covering #1 already (item 1 in https://www.google.com/about/company/philosophy/ https://www.google.com/about/company/philosophy/), #2 ought to be covered by M's security model, and #3 is a bit of a non-starter for a commercially viable app store (though Android certainly doesn't preclude it, as evidenced by F-Droid and other alternate app stores).

dredmorbius 11y ago

A system far more like Debian's in terms of app development/provisioning, and user-centric protections. A dev-compensation system not dependent on advertising. https://plus.google.com/104092656004159577193/posts/2eg1rG6kmJp https://plus.google.com/104092656004159577193/posts/2eg1rG6k...

fixermark 11y ago
Sorry to say: Debian's has advantages, but is a pain in the ass. The focus on security and reliability in packages means both stable and unstable tend to be so far behind head that I rarely find things I want to try are directly supported by the available binaries. Which is not to say Debian's approach is bad for its purposes; I just wouldn't want to use a smartphone app ecosystem designed like that. Advertising is trickier to wrestle down. I'm not sure in an ecosystem where advertising is allowed, a race to the bottom isn't to be expected, and best of luck banning it entirely.
- dredmorbius 11y ago
  Rather than respond to what you think I might have written, how about actually reading the suggestion and responding to its points. This would be more valuable to both of us.
  - fixermark 11y ago
    People only ever respond to what they think other people have written; such is the nature of communication. If you mean respond to the multi-paragraph G+ post: too many pieces to dedicate time to at this juncture. I misunderstood what you meant by the Debian model "in terms of app development" to refer to package creation / maintenance approach. If you mean these three elements: Putting user interests first Seeing specific limitations on app capabilities Promoting Free Software in all possible cases ... Then I think from Google's standpoint, it's probably understood that they are covering #1 already (item 1 in https://www.google.com/about/company/philosophy/ https://www.google.com/about/company/philosophy/), #2 ought to be covered by M's security model, and #3 is a bit of a non-starter for a commercially viable app store (though Android certainly doesn't preclude it, as evidenced by F-Droid and other alternate app stores).