Earlier quoted context omitted.
[flagged]
[flagged]
[flagged]
My Mac contacted 63 different Apple owned domains in an hour, while not is use
121–130 of 218 posts
Re: My Mac contacted 63 different Apple owned domains in an hour, while not is use
#122Earlier quoted context omitted.
My Macbook used to grind CPU for 10-20 minutes after every power on. That happened with literally fresh install and it does it every time. I don't know why does it do that. May be some indexing? This lack of transparency was one of the reasons for me switching to Linux too. I don't want my OS to do anything at all in background, that I didn't explicitly configured to. I want to be in full control of my software. Linu…
Huh, which process was doing this grinding on your MacBook?
In my experience this is usually Spotlight indexing files/checking previous indexes etc. If you have any backup software running that will do it too.
Re: My Mac contacted 63 different Apple owned domains in an hour, while not is use
#123Earlier quoted context omitted.
Have you tried GNU/Linux?
I've tried to use it as my daily driver multiple times since 1997 but ultimately for me personally and the security posture I have chosen to adopt the utility of being able to copy and paste from my phone to my desktop without having to deploy and secure my own infrastructure outweighs any paranoiac doomsday delusions someone may try to implant in my mind.
Have you tried using KDE Connect? It is really impressive.
Re: My Mac contacted 63 different Apple owned domains in an hour, while not is use
#124Re: My Mac contacted 63 different Apple owned domains in an hour, while not is use
#125Earlier quoted context omitted.
This article: Apple’s OS relies on a lot of services to deliver its features! That article: Microsoft reports every click you make Is that the comparison you’re making?
No. This article: My Mac contacted 63 different Apple owned domains in an hour, while not is use > while not in use That is not "Apple reports every click you make", _very_ different from Microsoft. These requests seem like they are all for background tasks to keep data up to date when the user goes to use it. Now can you see a difference between that and _reporting_ on what you are doing?
> These requests seem like they are all for background tasks to keep data up to date when the user goes to use it.
Where did you get this information? Is it just a guess based on what Apple declared about these domains?
In the article, there is no info about the content sent to these Apple owned domains. For all we know, MacOS could send detailed reports on the user's activity.
Re: My Mac contacted 63 different Apple owned domains in an hour, while not is use
#126Earlier quoted context omitted.
Apple has been involved in all the same government spying programs as Microsoft. They do not offer any services or products with E2E encryption that they do not control the key too.
But at least they have E2E encryption. The whole point of which is not having the key to.
The whole point is that a 3rd party (Apple) doesn’t have the key. It’s not real E2E and it’s still susceptible to government overreach.
Re: My Mac contacted 63 different Apple owned domains in an hour, while not is use
#127While this seems like a lot, in some ways this is what user's expect. Push notifications should be coming all the time, assuming the system is on. Most users expect various maintenance services to run when the system idle so it doesn't interfere with their active use of the system. When users open apps like Weather (or view a widget), they expect it to already be up to date without having to manually refresh or wait…
When Microsoft has telemetry: * Windows is a spyware machine - how can anyone use it? Year of Linux baby! When Apple has telemetry: * It's working as expected. So... to be fair, is there a thorough comparison of the two? How are they the same, and how are they different?
Apple users tend to trust Apple (whether or not that trust is misplaced is a different topic). Very few people trust Microsoft.
Re: My Mac contacted 63 different Apple owned domains in an hour, while not is use
#128Earlier quoted context omitted.
This is a very valid criticism of my post and many that group "opinions" as if they come from a single source. Here, the top-voted comment is OK with Apple software phoning home, but there's no evidence they are not equally OK with Microsoft software phoning home, so I'm contrasting this popular opinion with another popular opinion elsewhere. Here's one example from a different user, where Microsoft is described as "…
Microsoft put ads in their OS menus. Kindof a stretch to "both sides" this one.
Apple does too! Drives me crazy, although it’s not nearly as bad as Windows.
Re: My Mac contacted 63 different Apple owned domains in an hour, while not is use
#129Earlier quoted context omitted.
But at least they have E2E encryption. The whole point of which is not having the key to.
The whole point is that a 3rd party (Apple) doesn’t have the key. It’s not real E2E and it’s still susceptible to government overreach.
Not every Apple service is E2E encrypted, but some of them (like iMessage) are, and it's 100% real E2E.
Re: My Mac contacted 63 different Apple owned domains in an hour, while not is use
#130Earlier quoted context omitted.
Is it even a push notification if you have to fetch them from a server?
Is there mobile push technology which is actually fundamentally push, all the way down to the transport layer? Like open socket, listening for incoming packets only, no notifications-> no traffic? I was under the impression it was all polling if you go down far enough, but at least because of central registration the phone only needs to poll one single pubsub service instead of a separate server per subscription. Cou…
Yes, sms is "actually push" all the way down to the transport layer.
As far as I know, this is still what push notifications are built upon for an idle/sleeping device.
Carrier infrastructure knows which tower you last connected to, instructs that specific tower to broadcast a message telling your phone to wake up and fetch the remaining 80% of the notification content (the sms bit is usually just enough for your device to learn the UUIDs of the notifications)