@chris you are using a web browser, right? HTTPS is encrypted and the only identifiable information exchanged is your IP address (which isnt actually your IP address, we ran out of those years ago, and some sort of an IP address is needed to use the internet in the first place so its impossible not to send one), anyone viewing the encrypted traffic will not be able to idenify you from it, they can only idenify you from seeing your post, which is not the traffic which is encrypted, this is what apple encrypts, the traffic, the underlying request gets decrypted when it reaches apple
S
sylvie@chitter.xyz
@sylvie@chitter.xyz
Posts
-
I recently looked at my iPhone‘s traffic and was painfully reminded at how it sends every keystroke you type into the home screen search to Apples servers by default. -
I recently looked at my iPhone‘s traffic and was painfully reminded at how it sends every keystroke you type into the home screen search to Apples servers by default.@chris your post, the one im replying to right now, is also "encrypted and non-identifiable" in the exact same way the apple nonsense is, course that doesnt mean i cant read it and reply to it, or even know who sent it
-
I recently looked at my iPhone‘s traffic and was painfully reminded at how it sends every keystroke you type into the home screen search to Apples servers by default.@NikTheDusky honestly i (accidentally) dont have search autocomplete in my browser (not apple) and when i WANT autocomplete i just go to the home page of the search engine i use