Tadi Channel
Wanna hear a conspiracy theory on why the QPR1 source isn't public to this day? Since QPRs are only ever used by "best partners" and undoubtedly Google thinks primarily of Pixels when developing them, it's very plausible that they feel free to implement…
So QPR1 source just got released alongside Pixel feature drop. It seems it was kept a secret not because of unreleased security patches, but unreleased Pixel features.
🤯21😐8
Proton reserves the right to stop delivering registration mails to you. At the very least.
This either means a kind of blocking that can make you unable to login into your accounts (if login and registration sender is the same) or that at least on flagged accounts (which can supposedly happen simply because of vietnamese IP), they scan the mails/noscripts before encrypting them.
All this looks very far from their marketing. No, I didn't read their privacy policy, I'm already steelmanning them.
This either means a kind of blocking that can make you unable to login into your accounts (if login and registration sender is the same) or that at least on flagged accounts (which can supposedly happen simply because of vietnamese IP), they scan the mails/noscripts before encrypting them.
All this looks very far from their marketing. No, I didn't read their privacy policy, I'm already steelmanning them.
❤8😐6
Tadi Channel
Proton reserves the right to stop delivering registration mails to you. At the very least. This either means a kind of blocking that can make you unable to login into your accounts (if login and registration sender is the same) or that at least on flagged…
Even 7 months ago, it was a thing.
😐7❤4🤯1
Tadi Channel
There's a dude on Reddit who must've never read this pdf nor anything remotely similar and insists that DCG is staggered, it's such a weird conspiracy hill to die on. Both DCG and staggered slow down the rolling shutter relatively to same clock utilized on…
A slight correction, DGO doesn't seem to be equivalent to DCG.
https://web.archive.org/web/20211027145610/https://downloads.canon.com/cinemaeos/DGO-Sensor-White-Paper.pdf
Unless one of the two photosites always has a different gain than the other, DGO is prone to motion artifacts in form of gaps in motion or clipping below the white point. I couldn't observe this on DCG, while it's easy on QHDR despite the simultaneous exposures.
https://web.archive.org/web/20211027145610/https://downloads.canon.com/cinemaeos/DGO-Sensor-White-Paper.pdf
Unless one of the two photosites always has a different gain than the other, DGO is prone to motion artifacts in form of gaps in motion or clipping below the white point. I couldn't observe this on DCG, while it's easy on QHDR despite the simultaneous exposures.
🔥3❤1😐1
Tadi Channel
A slight correction, DGO doesn't seem to be equivalent to DCG. https://web.archive.org/web/20211027145610/https://downloads.canon.com/cinemaeos/DGO-Sensor-White-Paper.pdf Unless one of the two photosites always has a different gain than the other, DGO is…
And example of what can happen to QHDR despite the simultaneous exposures. The sole fact that the shorter exposures don't cover the same length of time as the long results in missing information for highlights. This obviously also affects staggered HDR, but even more, as exposures become fully sequential.
😐1
Tadi Channel
And example of what can happen to QHDR despite the simultaneous exposures. The sole fact that the shorter exposures don't cover the same length of time as the long results in missing information for highlights. This obviously also affects staggered HDR, but…
You can fight against this artifact specifically, but you'll either have to guess the missing data or prefer shorter exposure data for areas with motion.
😐1
I don't think I said it here, but the only OEM to fit denoscription by GrapheneOS communications is Nothing.
If it won't be them, it'll be a bust. I can't imagine HMD or Sony cooperating with a hardening-oriented third party system maker sufficiently, while Motorola, Samsung, OPlus, Honor and Vivo are way too proud (and in business of earning from preloaded bloat) to consider such a collaboration.
If none of the above, then it simply won't be a major OEM as much as it was claimed.
If it won't be them, it'll be a bust. I can't imagine HMD or Sony cooperating with a hardening-oriented third party system maker sufficiently, while Motorola, Samsung, OPlus, Honor and Vivo are way too proud (and in business of earning from preloaded bloat) to consider such a collaboration.
If none of the above, then it simply won't be a major OEM as much as it was claimed.
👍18😐3
1. It's the year 2032, you bought a faulty product.
2. You want to fill a repair/damage claim.
3. You're asked to take a photo of it.
4. Turns out your photo must come from a bootloader locked phone running stock because "Content Credentials", which "attest" you didn't photoshop the pics, are mandatory.
5. You must have a googled device to simply get your money back.
2. You want to fill a repair/damage claim.
3. You're asked to take a photo of it.
4. Turns out your photo must come from a bootloader locked phone running stock because "Content Credentials", which "attest" you didn't photoshop the pics, are mandatory.
5. You must have a googled device to simply get your money back.
😐24😁3🤯3
https://support.google.com/pixelcamera/answer/16507662?hl=en
For reference, as you can see, they're clearly not about individual's authorship, where the image author would be the one holding the signing key. It's attestation of "genuine device" embedded in the captured media.
For reference, as you can see, they're clearly not about individual's authorship, where the image author would be the one holding the signing key. It's attestation of "genuine device" embedded in the captured media.
Google
Fix issues with Content Credentials on Pixel Camera - Pixel Camera Help
You can verify how an image was created or edited with your Pixel camera. Content Credentials uses metadata attached to an image that describes the image’s history. This is part of Google’s efforts t
😐14
Tadi Channel
https://support.google.com/pixelcamera/answer/16507662?hl=en For reference, as you can see, they're clearly not about individual's authorship, where the image author would be the one holding the signing key. It's attestation of "genuine device" embedded in…
Their design is so much non-private that they had to mention a "strict no-logging policy" on their servers.
🤯8😐5