Nice try RIAA. My favourite isn't in the Mega thread HAHAHA HAHAHAHA losers

What you're talking about is supposed anonymity in obfuscation, and that has been proven to not work.

Also, most VPN companies keep logs and can be subpoenaed. Not all, but most. I2P is meant to anonymize your traffic, so I do not see the point of your statement

Exactly. People should read your comment before shouting at me for not providing "proof". They seem incapable to understand that Big Tech can be smarter and more resourceful than a lot of security engineers

I can understand the argument against bandwidth, but how do you conclude that it is not anonymous enough? Even against a VPN?

Maybe I should have said "it's not anonymous based on your threat model"

[-] liveinthisworld@lemmy.dbzer0.com 3 points 4 days ago* (last edited 4 days ago)

Technically speaking, VPN logs tend to include the IP address of clients connecting to them, after which the good VPN providers like Mullvad, IVPN and maybe PIA tend to purge them somewhere in their process. Now, if the VPN is running in a RAM-only node, then these logs probably don't touch storage, which means there's not much need to shred information from hard drives for the VPN provider.

With that said, an ISP can technically log your traffic and see that you're connecting to the IP range associated with a VPN. That and perhaps some more covert side-channel/correlation attacks can, in theory, compromise your identity.

Of course, this is going deep into OPSEC and forensics, and I don't think the NSA is that interested in the average Billy torrenting "The Office" to go through that many logs, even if the studios sue in court. Hence, technically your privacy is somewhat maintained with the good VPN providers, but you're definitely not anonymous

For anonymity, yes. Sure you might fool Google trying to match your IP to your traffic but that's about it

I do not see why everyone wants to deny this and trust big tech. After you lot completely brainwashed?? Assume the worst, that malicious applications are recording both your microphone and your camera, and do the best you can. Anyone even taking Meta's/Google's side here is absurd to me.

That shouldn't be possible in theory unless I don't know it well enough. Care to provide a screenshot?

Man, why is everyone like this? Please read the documentation, the traffic is encrypted and metadata cannot identify you. Unless the NSA has an active hack for I2P lying around, NO-ONE IN THIS WORLD can find out what chunks of traffic just went flying by your internet connection

As he said, paid with crypto and managed with his own keys. I don't see how the seedbox provider can trace you if you do that, so there's not that much to worry about

[-] liveinthisworld@lemmy.dbzer0.com 4 points 4 days ago* (last edited 4 days ago)

Unless you PGP-encrypt everything by hand you've just lost the fight

38

Imagine if Verizon, AT&T, T-Mobile and Cox banded together for a showdown against the studios accusing them of liability? AT&T runs an NSA stronghold in Manhattan, they're not going to let their darlings go down in a teeny lawsuit like this. I really want to see this happening. Let them fight.

20

What else is everyone using to get music? Other than Soulseek.

36
submitted 1 month ago* (last edited 1 month ago) by liveinthisworld@lemmy.dbzer0.com to c/android@lemmy.world

Hi everybody,

I've been unable to make sense or gain better understanding of the Android update system, so I'm asking here.

Coming from the linux desktop, there's two main parts of the system: the kernel and the userland. I could simply update the kernel without updating userland and vice-versa.

But does it work the same way on Android? Why are we so dependent on OTA updates from the individual manufacturer? I understand that microcode is proprietary and can come only from the device manufacturer, but aren't kernel updates and userland decoupled from this (for devices which support project treble and GKI)? Can't I just run a different FOSS launcher, get the upstream GKI kernel and run it with the microcode offered by the manufacturer?

What consists of an Android "version"? Can't I just not update the microcode beyond what the manufacturer provides, and instead keep updating the kernel (by "kernel" I mean GKI and not the actual linux kernel) and userland and in essence keep updating my android version?

I'm probably missing some fundamental understanding of android here, which is why decided to ask here. Thanks for your help!

15

By now, most people in the custom ROM community must have already heard of KernelSU. I do think that it is worth the hype and is truly revolutionary, piggybacking on something I credit Google on (to some personal chagrin) - KMI.

The question I have is: when I attempt to install OTA updates to a device with KernelSU running as a Kernel module, will that affect KernelSU? Will I have to root again?

view more: next ›

liveinthisworld

joined 1 month ago