Skip to content
  • Home Home Home, current page.
  • Moments Moments Moments, current page.

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
RichFelker's profile
Rich Felker
Rich Felker
Rich Felker
@RichFelker

Tweets

Rich Felker

@RichFelker

Yeah, I do @musllibc, FOSS & infosec stuff. But now is not the time for a mostly-/only-tech Twitter feed.

musl-libc.org
Joined March 2014

Tweets

  • © 2018 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Rich Felker‏ @RichFelker Mar 24
      Replying to @CopperheadOS @TheDaveCA @matthew_d_green

      Alternative dialers & messaging apps have no reason to have access to each other's data.

      1 reply 0 retweets 0 likes
    2. CopperheadOS‏ @CopperheadOS Mar 24
      Replying to @RichFelker @TheDaveCA @matthew_d_green

      Talking about SMS/MMS, not alternative forms of messaging. You can only have one at a time, and if people want to migrate they need a way to export and import their data. Supporting that means letting people get tricked into giving it to a sketchy app.

      2 replies 0 retweets 0 likes
    3. CopperheadOS‏ @CopperheadOS Mar 24
      Replying to @CopperheadOS @RichFelker and

      The Phone permission is also for assorted utilities other than the dialers themselves. We can 100% agree that the approach on iOS of not offering those options is better for privacy/security but we know why Android does it and why Google wouldn't want to remove it like we would.

      1 reply 0 retweets 0 likes
    4. CopperheadOS‏ @CopperheadOS Mar 24
      Replying to @CopperheadOS @RichFelker and

      Similarly, Android could have done just fine without permissions like Contacts and persistent forms of shared pictures, shared storage, etc. access. It has ways to provide that data as needed with user consent each time. The permissions are essentially for bulk / auto retrieval.

      1 reply 0 retweets 0 likes
    5. CopperheadOS‏ @CopperheadOS Mar 24
      Replying to @CopperheadOS @RichFelker and

      If you were starting from scratch and wanted to make a very privacy / security focused system, it may be a very good idea to do away with persistent permissions and to require user consent as needed. Android has most of those options, but apps prefer getting a permission once.

      1 reply 0 retweets 0 likes
    6. CopperheadOS‏ @CopperheadOS Mar 24
      Replying to @CopperheadOS @RichFelker and

      Like Signal, where instead of needing to press "add contact", selecting a contact, and then seeing if they have Signal it will bulk import and check if your contacts have Signal. It could support not granting the permission, but it doesn't bother with a fallback.

      1 reply 0 retweets 0 likes
    7. CopperheadOS‏ @CopperheadOS Mar 24
      Replying to @CopperheadOS @RichFelker and

      Similarly, apps almost always take the path of requesting the Camera permission. They don't need that to have the user take a picture. They can open up a camera activity where you can take a picture that they end up with rather than using the permission. Devs want more control.

      1 reply 0 retweets 0 likes
    8. CopperheadOS‏ @CopperheadOS Mar 24
      Replying to @CopperheadOS @RichFelker and

      There's a legitimate reason to have stuff like the Camera permission, i.e. making actual alternative camera apps or other apps taking different approaches to handling taking pictures. However, having it means it gets massively overused and abused. That's just the reality of this.

      1 reply 0 retweets 0 likes
    9. CopperheadOS‏ @CopperheadOS Mar 24
      Replying to @CopperheadOS @RichFelker and

      For example our Auditor app uses the Camera permission to do QR code scanning from the view finder. It originally did QR code scanning *without* requiring the Camera permission. It does now because we need control over it to offer a good user interface.

      1 reply 0 retweets 0 likes
    10. CopperheadOS‏ @CopperheadOS Mar 24
      Replying to @CopperheadOS @RichFelker and

      We have the option to have the user take a picture for us with their usual camera app (without needing the permission) to scan it from that. What we did before was spawning the external zxing app with users granting that the Camera permission instead. Wanted a better UX though.

      2 replies 0 retweets 0 likes
      Rich Felker‏ @RichFelker Mar 24
      Replying to @CopperheadOS @TheDaveCA @matthew_d_green

      Proper factorization would be requesting a QR scan and having a system service do it.

      5:51 PM - 24 Mar 2018
      2 replies 0 retweets 0 likes
        1. New conversation
        2. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @RichFelker @TheDaveCA @matthew_d_green

          This is essentially what spawning the zxing barcode scanner app does. If the stock OS had to bundle QR code scanning support in the Camera app, it could work without needing the zxing app. We didn't see an advantage to using zxing vs. requesting Camera ourselves + better UI.

          1 reply 0 retweets 0 likes
        3. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @CopperheadOS @RichFelker and

          The zxing app / libraries used to be an official Google project and they could have polished it up and put it into AOSP as a standard OS feature and required it for the OS camera app. Not sure why they let it bitrot as a near dead now independent project instead. *shrug*

          1 reply 0 retweets 0 likes
        4. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @CopperheadOS @RichFelker and

          Seems like Android 9.0 will have some kind of standard QR support but that might simply be as part of Play Services like so many other useful libraries are now, which is no use to us...

          1 reply 0 retweets 0 likes
        5. Rich Felker‏ @RichFelker Mar 24
          Replying to @CopperheadOS @TheDaveCA @matthew_d_green

          Time to get around to implementing fake Play Services...

          1 reply 0 retweets 1 like
        6. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @RichFelker @TheDaveCA @matthew_d_green

          Yeah, it's really hard to implement some parts of it like the computer vision parts with OCR, detection of different object types, etc. The easy parts are either stubbing out actual server-based services or making real clients to them like microG does for GCM, etc.

          1 reply 0 retweets 0 likes
        7. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @CopperheadOS @RichFelker and

          Also there's the VR / AR stuff now and maybe that will end up being important to people in the future. A large amount of that is open source in AOSP but there's a lot of fancy stuff that isn't. Maybe AR will become a killer feature for people, who knows.

          1 reply 0 retweets 0 likes
        8. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @CopperheadOS @RichFelker and

          We think of a lot of the research / work that we do as simply figuring out how to do things properly for some saner future system... but app layer is probably going to be needed in practice for a long time to use existing apps. Fancy new microkernel is easy vs. new app ecosystem.

          2 replies 0 retweets 0 likes
        9. Rich Felker‏ @RichFelker Mar 24
          Replying to @CopperheadOS @TheDaveCA @matthew_d_green

          I don't think ux for integrating legacy apps is that hard. When installing give user simple control (2-3 choices) for "do you want it to integrate with other apps?"

          1 reply 0 retweets 0 likes
        10. 11 more replies
        1. New conversation
        2. Rich Felker‏ @RichFelker Mar 24
          Replying to @RichFelker @CopperheadOS and

          If you want to allow more power, let app provide custom code to run in full seccomp processing camera stream with small-N byte limit to send back when done.

          1 reply 0 retweets 0 likes
        3. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @RichFelker @TheDaveCA @matthew_d_green

          Agree, and the situation is that these existing operating systems / APIs with massive app ecosystems are here and they need to be slowly moved towards approaches like that via incredibly painful ecosystem-wide breaking changes with each major release.

          1 reply 0 retweets 0 likes
        4. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @CopperheadOS @RichFelker and

          Fully expect that stuff like persistent, bulk access to pictures, etc. gets mostly or entirely phased out. It's a painful, long process. Google eventually implements a fair number of the things that we implemented earlier and never expected them to provide any time soon.

          1 reply 0 retweets 0 likes
        5. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @CopperheadOS @RichFelker and

          It's a lot harder for them to do a lot of the things we decide are good ideas and implement downstream. Sometimes they make features for us and don't deploy them, like legacy app permissions review (we don't grant those at install time and we don't silently disable by default).

          1 reply 0 retweets 0 likes
        6. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @CopperheadOS @RichFelker and

          Permissions review == when you first run a legacy (API <= 22, i.e. not updated for post-5.x era APIs) app, you're shown toggles for all the permissions instead of them being enabled by default. It's a standard AOSP feature, not something we made. We only made some tweaks to it.

          1 reply 0 retweets 0 likes
        7. CopperheadOS‏ @CopperheadOS Mar 24
          Replying to @CopperheadOS @RichFelker and

          Earlier, we offered an opt-in option to disable permissions for legacy apps by default, but that wasn't very usable at all. Certainly not usable enough for us to enable it by default, and not enabled by default effectively means useless since few people will actually use it.

          0 replies 0 retweets 0 likes
        8. End of conversation

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2018 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Cookies
        • Ads info