Live data from Hacker News

Android 10

android.com

391–400 of 518 posts

Re: Android 10

#391

Earlier quoted context omitted.

Please stop advocating for Telegram: https://gizmodo.com/why-you-should-stop-using-telegram-right... https://twitter.com/tqbf/status/987372998935105539 Signal is definitely the more secure choice, but Whatsapp is still king of the network effect at least in my neck of the woods.

Update 8/31/2019: After publication of this article Telegram’s creators implemented several changes that are recognized by qualified cryptographers as a vast improvement to its encryption scheme. Since 2017, for example, the MTProto protocol has been recognized as IND-CCA secure.

Its still not actually on by default and you can't use encrypted chat synced between your desktop and phone. Group chats also don't have encryption and (last I checked) count be run e2e encrypted.

Probably 99%+ of conversation on Telegram are visible to the Telegram company.

Re: Android 10

#393

Earlier quoted context omitted.

RCS is dead. The take up amongst operators is really low. And it's unlikely that will change anytime soon as their focus is on the 5G rollout and not on re-platforming their messaging system. Also the system is unencrypted so you would have to be crazy to use it in this environment.

I don't understand why they would do a default unencrypted messaging service today.

Probably because the spec started all the way back in 2008, and you could revise it yet again, even though almost nobody is currently supporting it, or you can get it out and improve the situation for many people, even though it's not perfect. I imagine pushing for an extension to support encryption might be a lot easier if there's actual uses to call for it.

Given that Google has started rolling it out with a fallback to Google servers if the network provider doesn't supply one, and Google has said they understand encryption is important and they will push for it, we might actually see some progress soon (on both the adoption and encryption fronts) if we're very lucky.

You can see references to that info in some of my other comments on this article, since I looked it up again today after mentioning it earlier.

Re: Android 10

#394

Earlier quoted context omitted.

Apps are going to use whatever CPU and memory is available. It's the same reason a chat app can use hundreds of MB of memory on a desktop. Why optimize that lower when laptops ship with 16+ GB these days? In my experience that $140 phone actually does end up being laggier and less responsive which can be super annoying when scrolling and tapping with your fingers. I'm not a hardware engineer, but somehow this seems t…

While I think your comment is accurate, I'd argue that optimization is a better use of money and time than changing icons every 6 months to a year just so that the app looks new. Honestly, why do icons change so much? Is it some psychological thing? I'm going to get used to whatever layout it is anyway and most popular apps have gone through a few designs and figured out what works. Like HN has not changed its layout…

I think it’s a signal that says “I run the newest OS, so I have fairly recent hardware, so I’m relatively wealthy”, and that sells phones.

Re: Android 10

#395
post #126

Earlier quoted context omitted.

This is an interesting workaround. People forget that part of the point of different colors for iMessage vs SMS was to indicate that iMessage is encrypted and SMS isn't. It's also a handy marketing thing, but there is a technical justification for making a visible distinction. AirMessage is basically a proxy that strips encryption for Android devices: "AirMessage leverages the power of your Mac computer in order to r…

I don't think that's what's happening here. I think AirMessage is just functioning as an iMessage client by using the Messages app on the Mac as a proxy. It would be no different from sitting physically in front of the computer. You can only read the messages off the screen and you can only send messages through Message itself.

I think we're saying the same thing. :-)

I would imagine that the AirMessage Android app is actually in communication with the AirMessage server on your Mac. It uses some automation (perhaps via something like https://github.com/shusain93/OSXMessageProxy) to talk the the Messages app. The connection is encrypted from there to the other side, as if you were sitting in front of your Mac. This happens in reverse the other way.

Hacky, and now you own the weak links in the E2E encryption chain. But a neat workaround, in a pinch.

Re: Android 10

#396
post #221
post #126

Earlier quoted context omitted.

This is an interesting workaround. People forget that part of the point of different colors for iMessage vs SMS was to indicate that iMessage is encrypted and SMS isn't. It's also a handy marketing thing, but there is a technical justification for making a visible distinction. AirMessage is basically a proxy that strips encryption for Android devices: "AirMessage leverages the power of your Mac computer in order to r…

Does it re-encrypt them when sending, though? I would have to assume they've at least looked at doing that, otherwise it's a giant security hole.

See my peer response. I would imagine all traffic from the Macother device is encrypted. You're responsible for securing the AndroidMac link.

Re: Android 10

#397
post #359

Earlier quoted context omitted.

Except this feature doesn't add security, it just adds a tool for reducing the usability trade-off of having a long hard password. I think it is very misleading phrasing.

If the feature makes folks more likely to use a 64 character random password for your Wi-Fi then I'd say it certainly does add security. Presumably folks will be "sharing" the plaintext value of their Wi-Fi password with friends regardless of whether they use this feature or not, so it appears to neither increase nor decrease THAT aspect of Wi-Fi password security.

I highly doubt anyone is using 64 character wifi passwords because QR codes are an option.

Good luck typing that into your playstation with a controller and your chinese IoT product.

The best solution is still the middle ground between readability/memorability + strength. Or stored in a password library until needed.

Re: Android 10

#398

Earlier quoted context omitted.

> We have had similar, but not as bad, reactions to other low end device we use for testing Let me guess -- Nexus 5X? I use one as my primary phone, and the slowness is noticeable but usually tolerable.

Hope you have it backed up, because they die sooner or later. For me it was sooner, for my friend it was later. Some soldering problem if I recall things right. A bootloop is the first (and sometimes the last sign).

> Hope you have it backed up, because they die sooner or later

Tangential to your point, but is there anything useful that isn't backed up more or less by default in the standard Android workflow? I get that the privacy-concerned wouldn't use eg Google Photos, but they also likely heavily overlap with the set of people savvy enough to set up backup solutions for important data.

Re: Android 10

#399

Earlier quoted context omitted.

>At this point, there's very little difference between the hardware of flagships and commodity, especially considering the real-world use of smartphones. Cameras.

Exactly. In 2019 you're paying for software and camera

Would you include screens? I feel like my decisions (between flagships) tend to be driven primarily by screen.

Re: Android 10

#400
post #289
post #76

Earlier quoted context omitted.

I wonder if any of the Google apps will support a dark mode. Maps / Gmail are harder to use with all of the white

Neither Maps or Gmail is using Dark Mode for me on the Pixel I updated this morning. Hopefully it'll be added in an update.

Both apps' dark modes are shown in screenshots on the official Android 10 page.

https://9to5google.com/2019/09/03/gmail-dark-mode-android-te...

Probably not far off.

Post reply on HN