Melody

lol you are so wrong.

TL;DR: I think this video oversimplifies the analysis according to the cards and gives Graphene OS undue weight without going into sufficient detail as to why each scored under each category.

I actually don't agree with this video; and firmly believe it is more than a little biased.

For example, the Pixel, AOSP and Android are given several undeserved points due to lack of proper information or understanding of how certain features work. I imagine this is the case too for the iPhone; if a bit less so.

The review apparently doesn't deep dive into settings or attempt to maximize privacy by turning off unwanted 'features' when settings switches are available to the user; nor does it assume that you set up accounts in as private of a manner as reasonably possible or toggle off as many default-on consent switches as needed.

While I would support scoring and dinging each case or instance for "Privacy Settings that don't actually work"...this video really doesn't do a lot of legwork and leans on the anecdotal evidence of scary news stories too much.

Worse was the fact that the entire video felt like they were shilling for Graphene OS; which is known to have a slightly unfriendly maintainer and community surrounding him to say the least.

No mention of Lineage or other privacy oriented Android ROMs were analyzed. AOSP too, was unfairly lumped in and dinged for specific points of the Default Pixel configuration....and yes there are major differences between AOSP and Pixel Android; even though Google tries to be less in-your-face invasive than the other OEMs. Not enough credit is given for the "On-Device" smart features implemented properly on the Pixels.

Out of personal experience; I'd actually rate a proper Lineage OS install of 4 whole Android versions ago to be more private than stock. Not quite as private as Graphene; but not quite as invasive and much more enforcing of privacy. The debloating provided by a clean AOSP-like ROM, such as Lineage, as opposed to a "Stock Android" configuration from a major OEM is stark.

Most importantly I personally feel that the privacy model chosen for the video is far too thickly detailed for an average person. Most of the privacy concerns listed on each card contained concern points that might only tangentally apply or don't apply at all to mobile phones. The way that each card was scored and applied felt low effort. None of the points on any of the card(s) were weighted with average users in mind.

I really hope someone goes into a much deeper dive; this video is basically clickbait that parrots the commonly parroted advice in the privacy community; which isn't even good advice, it's just 'One-Size-Fits-All' style advice which gives the user no room to make necessary 'Privacy vs Convenience' tradeoffs that they themselves could have made if they understood proper threat modelling.

I've always hated Crustyroll.

Crustyroll got it's start by standing on the backs of good noble fansubbers who provided their subs for free; and now they've come full circle. They became an enemy rather quickly when it profited them.

Actually; (basically) SIP over (basically) IPSec sounds pretty correct. Wish the dense technical manuals I read had explained it that way; makes a lot more sense to me as a Net Admin type of IT person.

I do remember reading that the protocol was basically encapsulated. Dunno about any encryption; probably there's not any at the IPSec level. I do know that the SIMs themselves probably contain certs that have some value; I just don't know if they handle any encryption or if they're just lightweight little numbers for authentication only.

If I'm understanding how 'WiFi Calling" works; it's still "identifying you" to the cell provider the same way; via your SIM. The only difference is they don't get an exact location because you're not using any cell towers typically.

I do suspect SIMs and eSIMs are still doing all the heavy cryptographic signing done on a typical phone network though...they're just not screaming your IMEI/IMSI all over open or even encrypted airwaves; nor is a WiFI signal triangulate-able typically due to it's short range.

They certainly make it easier to do so; by making it a switch you can toggle; which allows you to generate an identity; or choose not to and roll with the identity they've already seen.

Agreed.

Without concepts of privacy; things will soon fall into fascism.

(People can’t DM you)

This is false. However, you must generate an "identifier / group / channel" for them and share that link out-of-band to them." Basically it means nobody can slide into your DMs unless you yourself consent to it and forge a connection with them to do so. It does offer a way to invite other users to chat; but the other user must consent as well...which makes it far safer usually.

Keybase is better than Signal. You may not like it's current owners but it still works, still functions, and can be used to chat privately. It's entirely OSS on the client side; and server-side software isn't provided; but with an open Client; it's likely trivial to reverse and re-implement your own. (Keybase itself doesn't provide their server code; it's private due to abuse constraints)

Keybase is End to End Encrypted. It may not be as "feature rich" but all features are private.

I'm not sure if it's indev anymore though; and it does allow you to be as public or as private as you'd like to be about your identity.

In general; I think even 2 billion is too much. Nobody needs that much money.

At best; I think no one should be able to have more than about 500 Million. You get one house, and one car for each adult family member if you're married with non-adult kids. Adult kids don't add uncounted vehicles; they have their own limit. Anything that is seaworthy or airworthy counts as about as much "Wealth" as you initially spent on it minus a reasonable depreciation rate yearly as determined by the market, so no buying a thing and having it lose 30% of it's value the moment you drive it off the lot after buying it.

Additionally; to block too many shenanigans; wealth added by any property that is bought sticks; 3 years at minimum. This prevents people from storing too much excess in property and shell-gaming it. A company you own or have stake in cannot lend (in a long term) or gift you property in excess of 1% to 10% the wealth limit. (Depending on what the thing is). Companies may also not hold property or money in lieu of an individual personally; everything the company owns must have a global company function; and not personally benefit one or more people only. (Basically no executive-only or owner-only Jets; everyone from the tiniest manager on up should have access to it if there's a business reason for it)

It occurs to me that adding a visual watermark might actually serve to obscure a visual watermarking scheme that is otherwise invisible by providing data that scrambles or breaks the watermark decoder itself.

Audio watermarks can be distorted in any number of ways; and it could be that some of the wildly poor audio quality in most cam-rips is probably the only way you can defeat the watermark; by using a LQ microphone and encoding the audio to a very limited bitrate and then re-upsampling; to defeat any subtle alterations a digital watermark might make to the audio waveform.