Yikes.

In 1997; I was walking about 2 miles to and from school. Unsupervised. I had a house key on my neck and was a latchkey kid in third grade. I obediently walked to and from school directly from home; meeting the crossing guard a half mile from school twice a day; as I had to cross a major 4 lane divided highway.

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.

The reason things like Alcohol are “considered and generally recognized as safe” has a lot to do with their effect length on the body. It’s possible to isolate someone intoxicated this way for up to 24 hours and see them recover all of their facilities in the short term.

Granted; it still has long-term effects that are bad, just not show-stoppingly so, and it only affects people who actually abuse the stuff long-term for many years.

I do agree we should be a lot tougher on Alcohol use in general. Maybe not Prohibition levels; but some framework to cut off people from acquiring quantities that can intoxicate them so badly that they pose a danger to themselves and others.

They faffed around, and now they’re finding out that, yes, the experts were in fact right! Restricting abortion access does cause more deaths and poor health outcomes!

Legitimately I question that this is even newsworthy.

It appears that these women are harming nobody and are partaking of the drug(s) safely and sensibly in a manner that ensures that no one is being significantly endangered. Yes the residual dangers exist and bad trips can happen to pretty much anyone. I don’t feel as if they’re even posing a danger to their children; if this is in fact being done in such a way that the kids are never being exposed to their parents while they’re in an altered mental state due to hallucinogenic intoxication. If it isn’t; yeah; I could see why a local branch of child services might pay them a visit. However, I’m not going to make that negative assumption.

I don’t particularly commend the women, nor the news outlet, for coming out about this though; it is still very much technically illegal by current law. But, I also do agree that the stigma attached to drug use, even when done so responsibly, is in fact ridiculous and stupid in general. However, I don’t see a better way of achieving what that does…so I couldn’t suggest any better alternatives and I don’t support going back to a previous era in Law where drugs that factually are provably dangerous, for some reason, are not regulated. Reasonable and Sensible Regulations on dangerous Drugs are REQUIRED; it’s just that some people have a different definition of ‘Reasonable and Sensible’ which has to be ironed into a proper consensus for society.

I think there’s a problem with the ‘C only’ devs refusing to be accomodating to the Rust developers. Instead of being stubborn; why not provide them what is needed and help the Rust team learn how to maintain what is needed themselves?

None of the reasons I’ve seen mentioned are legitimate reasons for refusing to at least help them a few times, and helping them to learn how to do the onerous task themselves so they can keep it off the main plate for too long.

C devs do not need to learn Rust to provide critical information; they need only be present and cooperative with Rust devs to help them find, convert, and localize data structures for Rust use. They can stand to sit and pair code with their Rust Dev counterparts long enough to teach a Rust Dev counterpart how and what they need to look for in C code. It’s not that big of an ask, and it’s not something that really is a large ask. Provide the bindings for a short period of time, and work on training a team of Rust Devs to maintain the bindings.

That way both sides are stepping up to meet the others and the data isn’t being sat on by the C-only Devs.

Here’s a rule for uBlock Origin.

Credit: https://lemmy.one/comment/597479 && original link: https://lemmy.nz/comment/446556

! Anti-Youtube Anti-Adblocker https://lemmy.one/comment/597479

youtube.com##+js(set, yt.config_.openPopupConfig.supportedPopups.adBlockMessageViewModel, false)

youtube.com##+js(set, Object.prototype.adBlocksFound, 0)

youtube.com##+js(set, ytplayer.config.args.raw_player_response.adPlacements, [])

youtube.com##+js(set, Object.prototype.hasAllowedInstreamAd, true)