Live data from Hacker News

Google Pixel 6 and Pixel 6 Pro

store.google.com

571–580 of 851 posts

Re: Google Pixel 6 and Pixel 6 Pro

#571
post #408
post #89

This will get downvoted immediately but what the heck. I understand we need better representation for people of color in many places - but dang Google, not a single white guy on the Pixel 6 page [0]?? Dozens of photos of people, not one white male. Sort of jarring in the reverse if you ask me. [0] https://store.google.com/product/pixel_6?hl=en-US Edit: Because the common reply to mine seems to be "Well now you know h…

" Eschew flamebait. Avoid unrelated controversies and generic tangents. " https://news.ycombinator.com/newsguidelines.html

You mean "don't disagree with the narrative".

There's no flame in what he's saying. There is also no way he is encouraging others to flame.

He's stating his opinion on the topic, and it is not popular with others. How is that against the guidelines?

Re: Google Pixel 6 and Pixel 6 Pro

#572
post #535

Earlier quoted context omitted.

That’s all great - but don’t lure people too much into a false sense of security. While your Nexus 6 may run a shiny new version of Android, underneath it runs a crusty old 2017 kernel full of holes of different sizes. The community is great, but vendor support remains important. LineageOS and other projects can’t fix things in kernels they can’t compile - they can only provide security updates for open source compon…

Alright - I'll bite. This is a smartphone, not a windows PC with a bunch of services. There is Zero listening on any port. There is no attack surface for any kernel - the only thing there would be a bug in mms. Please share your source for kernel attacks, on any android version, that's not an attack on an app - but on the kernel. No, this is not a google play attack, or an attack on an outdated app - which are update…

Smartphones aren’t servers, but they run tons of services that interact with the surrounding world. Bluetooth, WiFi, etc…

The kernel also still plays a vital and security-meaningful role in processing calls from applications.

Running an out of date kernel could mean strangers ransoming your data, or could mean an attack becomes persistent and starts logging and uploading through reboots.

Running an out of date kernel often does not result in this, and that higher level security matters first.

However, the kernel does have an attack surface through those higher levels, and pwning the kernel still means something.

Those datacenters are running LTS kernels with minor versions updated, or have security patches backported, or have far more limited connections to the world than your phone — only one protocol, one port, one service, for example.

One example, since you asked: https://thehackernews.com/2019/10/android-kernel-vulnerabili...

Re: Google Pixel 6 and Pixel 6 Pro

#573
I really like that bootloaders on Google-branded devices have usually been unlockable, and they win points for that.

Currently I'm using that for GrapheneOS. https://grapheneos.org/

But I'm not fond of the recent front-facing camera cutouts in the display, which are tackier to cover with tape. I foresee being sad if/when end of upstream device security fixes forces me to upgrade hardware from my Pixel 3.

Re: Google Pixel 6 and Pixel 6 Pro

#574
post #432

Earlier quoted context omitted.

I like frictionless Fi is. Phone breaks? No prob. Grab a cheap Moto phone from the Fi store listing, get it in the mail the next day, and setup in 5 mins. Go over on data? No prob. Pay a prorated price at the exact same rate.

> Go over on data? Or you could be a T-Mobile subscriber and never "go over" on data, even when abroad. It just gets slower, but that's fine most of the time, at least for me. It's amazing to be able to use even slow internet in the butt crack of the world somewhere without paying an extra dime - that's the way it ought to be on all carriers.

Fi has infinite free slow data too. "Going over" in a way that involves money is only relevant to the first few gigabytes on the $0-60 data plan. (Unlimited Plus is flat $50 of data)

Re: Google Pixel 6 and Pixel 6 Pro

#576
post #408

Earlier quoted context omitted.

" Eschew flamebait. Avoid unrelated controversies and generic tangents. " https://news.ycombinator.com/newsguidelines.html

You mean "don't disagree with the narrative". There's no flame in what he's saying. There is also no way he is encouraging others to flame. He's stating his opinion on the topic, and it is not popular with others. How is that against the guidelines?

It was an obvious generic tangent into an obvious flamewar topic.

I realize that details like that can be activating, but in this case it was a clear swerve into offtopicness. This is not a borderline call!

Offtopic swerves can be fine when they're interesting and unpredictable, but classic flamewar swerves are the opposite of that.

Re: Google Pixel 6 and Pixel 6 Pro

#577
post #576

Earlier quoted context omitted.

You mean "don't disagree with the narrative". There's no flame in what he's saying. There is also no way he is encouraging others to flame. He's stating his opinion on the topic, and it is not popular with others. How is that against the guidelines?

It was an obvious generic tangent into an obvious flamewar topic. I realize that details like that can be activating, but in this case it was a clear swerve into offtopicness. This is not a borderline call! Offtopic swerves can be fine when they're interesting and unpredictable, but classic flamewar swerves are the opposite of that.

It wasn't. He was simply stating what he saw and why that made him uncomfortable.

It wasn't even remotely off-topic. This is a RELEASE banner/promo website for the product. He discusses that.

It seems just like censorship, and that's cool. I understand the requirements to keep narratives flowing. But we'll all end up in an echo chamber, unable to admit when we feel like something feels wrong.

You keep using words like "flamewar" and "flamebait" for the topic of someone feeling that a race was purposefully neglected for marketing. It sounds like you're the one trying to smooth over a very validly concerned topic.

Edit: I realise you are now attempting to delete his comments because he replied to other comments that were clearly not very nice (in his edit). So I guess you're just torching the flames that he's already tried torching? But with force?

Re: Google Pixel 6 and Pixel 6 Pro

#578
post #282

Earlier quoted context omitted.

It doesn't look like it, they still release phones exclusively with face unlock. What security issues can it have? Fingerprint sensors could be fooled with less work. And fingerprint sensors don't work always (e.g. for me they don't).

Hmm, I thought Apple had switched to requiring pin/watch for face ID unlocks because they were not totally secure. The same could be said for fingerprint though. I think the more secure biometric unlocks require the occasional pin verification anyways.

pin is used when faceID cannot recognize you (when you're wearing face mask)

Re: Google Pixel 6 and Pixel 6 Pro

#579
post #274

Google seems to have for some reason requested a very/overly broad embargo from reviewers which does not let them show any photos taken with the device or software features for now. MKBHD mentions this (and shows nothing from the phone really) @ https://youtu.be/roWxo6jWoYw?t=140 And Mrwhosetheboss said he refused to cover these phones due to the embargo. The Tech Chap mentions he can't show anything apart from the h…

What that really means is that the software has bugs and there's a hope that these will get fixed before they begin to be distributed. Note that there's more software in it than just Android.

Wait for a full review before hitting that buy button.

And we should appreciate journalists who disclose what Embargo is enforced on them.

Re: Google Pixel 6 and Pixel 6 Pro

#580

Earlier quoted context omitted.

Which is a shame since we were getting very close for a while there.

We have never been very close to integration.

Not in the US at least. But elsewhere, yes. The world as a whole? I agree with you, not close. But really that's fine.
Post reply on HN