@nexusband @FragmentedChicken depending who you ask.

@BearOfaTime @warm at 6", even smaller hands like mine are able to reach within .5cm of the top of the screen. At that size, the weight distribution of the phone is what makes a difference in terms of manageability. For example, the weight distribution of the Pixel 6a (6.1") makes it a breeze to use with my right hand, but a tad more difficult with my left one. Using it in reverse (had to once) is impossible one-handed.

@danielfgom @Welp_im_damned wdym? I can perfectly buy Pixels from the Google store or Amazon in Spain.

@AdmiralShat @FragmentedChicken phones that support esims have actual sim chips inside, and esims basically flash the carrier data onto that chip.

@soulfirethewolf heresy! /s

@Dave beeper is not an intermediary, it does not handle the messages. An e2e imsg from an iphone A to an iphone B goes like this: A -> apple -> B. With beeper, the only difference is that either A, B, or both, ain't an iphone. Beeper is a compatibility layer kind of like wine on Linux.

@Dave I meant this dissertation:
> ... The way Apple sees the situation: ...This tiny company [Beeper] has effectively hacked a closed protocol, and now millions of users are potentially having their messages handled by a company they’ve never heard of. What’s worse, since they’re sending blue-bubble msgs, those users will assume they’re sending encrypted msgs through a trusted source — Apple — and they’ll never know about this intermediary that promises it’s trustworthy, but who really knows?

@Dave I stopped reading the moment I saw that his thesis is based on the wrong fact that Beeper Mini relays messages through their servers. It doesn't, it connects directly w/ Apple, and the code is OSS & verifiable.

@ijeff this article is factually wrong.

@WarmSoda @Ranvier in the US, especially if you're young, you're indirectly forced. Luckily here that's not the case.

@Max_P @FurtiveFugitive you know, Chrome itself is closed source.

@soulfirethewolf @ijeff its biggest lockdown is the security model, which even though it won't disallow you from doing anything you couldn't otherwise do (if you're motivated enough), it draws the line of tradeoffs to make. I gave up rooting and a lot of stuff (like contactless payments) for it's security and stability, and I'm fine with that, but you should ask yourself if that's worth it for you. If you have to go out of your way to break the security model, even once, then it isn't for you.

@netchami @ijeff ironically, graphene had to do its porting through unofficial source releases and then finish the porting by comparing against the official A14 source; whereas Samsung, as a partner of google, had exclusive access to the unreleased source.

@independantiste @ArghZombies I honestly don't care what it is as long as it follows material design 3 and has material you support.

@skullgiver @ijeff people like eSIM because it allows multiple networks on phones that only have one physical slot; which nowadays, in my experience, is all except some cheap Xiaomis that have a microSD slot that doubles as dual SIM.

@DAMunzy @victron there's lots of tech stuff only available on Ali, or that are significantly cheaper there because of currency conversions and scalper resellers on other platforms.

@PrivateNoob it will, it's just that they wanted to get A14 out ASAP because of the security improvements.

@PrivateNoob @FragmentedChicken I think it's because graphene isn't done with the porting yet, because other features of the lockscreen like the shortcuts are also gone. They said that there was more work to do, so we'll see...

@ijeff that cuthole selfie camera is giving me so much OCD...

@phillaholic carriers have to "approve" updates; Google, Samsung, or whoever is your vendor can't actually push an update because the carrier must sign it with their key. Was it Google's fault for the vuln? Yeah. Was it AT&T's fault for your update to take 1 week longer to roll out to you? Yeah.