• 3 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle

  • Kagi generated key points:

    • The new Find My Device network on Android was designed with a strong focus on user security and privacy.
    • The network uses a crowdsourced approach to locate lost or misplaced devices and belongings, even when they are offline.
    • The location data reported by participating Android devices is end-to-end encrypted, ensuring Google cannot access or use the location information.
    • The network has "aggregation by default" as a safety feature, requiring multiple nearby devices to detect a Bluetooth tag before reporting its location to the owner.
    • The network also has protections to avoid contributing location reports when near the user's home address.
    • Rate limiting and throttling are used to prevent malicious real-time tracking, while still allowing the network to be useful for finding lost items.
    • The network is compliant with industry standards for unwanted tracking, triggering alerts on both Android and iOS devices.
    • Users have full control over which of their devices participate in the network and how.
    • The network design has undergone internal security testing and is part of Android's vulnerability rewards program.
    • Prioritizing user safety and privacy is an ongoing commitment as the team continues to improve the Find My Device protections.


  • Kagi summary:

    • The Android Market (now Google Play Store) was launched in October 2008 with the T-Mobile G1 phone, helping establish app ecosystems on mobile.
    • Before app stores, finding and downloading apps was difficult through various online stores and carrier stores with limited selection and updates.
    • The Android Market centralized the app experience and discovery, giving access to a growing variety and number of apps in one place.
    • Early app successes helped drive more users, phones, developers and apps in a reinforcing cycle that grew the app economy exponentially.
    • Popular early apps filled gaps in Android's capabilities in areas like weather, file management, flashlights as built-in features were still being developed.
    • Later apps brought extra abilities beyond necessities, like music streaming, ebooks, games, social media and more.
    • The article reminisces on the novelty of app stores and ecosystems in their early days compared to their ubiquitous presence today.
    • Over 100,000 apps were available by mid-2010 and over 3.5 million apps today on Google Play.
    • We now take app discovery, updates, and the overall app experience for granted due to how well app stores do their job.
    • The article credits the Android Market and Apple App Store for establishing apps as the norm and changing our expectations of mobile.

  • Google Messages.

    And yeah, I think it really has had that effect. Most people don't know about it; I had to show my father how to set it up. They put a banner up on the app once when they introduce it, or when you first open Messages, but a ton of people just dismiss the banner and then don't see it.

    Versus apple who has a big show where they show off all the new shit they're doing, and the press breathlessly covers it, trickling it down to the average consumer.





  • In theory yes, but it becomes a problem of ergonomics. The transpiled library feels like a transpiled library, it doesn't match the conventions of Nim/Zig. The best ports/wrappers/whatever typically use the C lib for all the heavy lifting and unique things, and build their own interface, that matches conventions of the calling language


  • Its a neat language, very simple. Has a somewhat simple approach to codegen at compile time, which is both a boon and a curse; you can do a lot with it, and not get too deep into footgun territory, but once you hit the limits of what you can do, you're pretty much stuck there.

    The syntax and other features are very nice, and it makes rather small binaries. I'd say its comparable to Nim in this area.

    Sadly, it also suffers the same problems Nim suffers: dearth of libraries.


  • Nesting is now in native CSS, so it's even easier

    My approach for variants is to use attribute selectors. You don't get massive class names and it becomes more obvious what things are doing. Discover ability gets hurt a bit, but that was never BEMs strength either

    https://pdx.su/blog/2023-07-27-use-css-attributes