The Asurion article outlines how to manage various Apple "intelligence" features, which personalize and improve user experience but also collect data. It explains how to disable Siri suggestions, location tracking for specific apps or entirely, personalized ads, sharing analytics with Apple, and features like Significant Locations and personalized recommendations in apps like Music and TV. The article emphasizes that disabling these features may impact the functionality of certain apps and services, and offers steps for both iPhone and Mac devices.
The Asurion article, "How to Turn Off Apple Intelligence," provides a comprehensive guide for users of Apple devices who wish to limit the amount of data Apple collects for the purposes of improving its products and services. The article focuses on several key areas where data collection occurs and details the steps necessary to disable or restrict this collection. It begins by explaining that "Apple Intelligence" is a broad term encompassing various data gathering processes, not a single, monolithic feature that can be toggled on or off. Therefore, managing data sharing requires adjusting several individual settings across different areas of the operating system.
The article carefully outlines how to manage "Personalized Recommendations," which leverage user data to suggest apps, music, and other content. It explains how to disable these recommendations within the App Store, Apple Music, Apple Books, Apple Podcasts, Apple TV, and for News notifications. The article provides specific instructions for each, including navigating to the relevant menus and toggling the appropriate switches. For instance, within the App Store, users can disable personalized recommendations by tapping on their profile icon, then selecting "Personalized Recommendations" and toggling the switch to the off position.
Furthermore, the article addresses "Location Services," a feature that allows Apple and third-party apps to access location data. It emphasizes the importance of understanding the various levels of location access, including "Never," "While Using the App," "Always," and "Ask Next Time." The article thoroughly explains how to adjust these settings for individual apps, allowing users to granularly control which apps have access to their location and under what circumstances. The authors also highlight the "System Services" section within Location Services, which allows users to manage location-based system features such as location-based alerts, significant locations, and sharing location with family members.
The article then delves into "Siri & Dictation," explaining how voice data is used to improve Siri's performance. It guides users through the process of disabling Siri and Dictation entirely, or alternatively, opting out of sharing audio recordings with Apple for review and improvement purposes. The steps involve navigating to the "Siri & Search" section within the device's settings and adjusting the relevant toggles.
"Usage & Diagnostics," another significant data collection area, is also covered in the article. This feature shares diagnostic and usage data with Apple to help identify and resolve issues. The article explains how to disable the automatic sharing of this data by navigating to the "Privacy & Security" settings, then to "Analytics & Improvements," and disabling "Share [Device] Analytics."
Finally, the article briefly touches upon "iCloud Analytics," which analyzes iCloud data to improve services like Siri and Photos. The article explains how to disable this feature for specific services, such as Photos, by navigating to the respective app's settings within iCloud.
In conclusion, the article serves as a detailed manual for users who want to take control of their data privacy on Apple devices. It meticulously outlines the various data collection points, provides step-by-step instructions for disabling or limiting data sharing, and emphasizes the importance of understanding the implications of each setting.
Summary of Comments ( 254 )
https://news.ycombinator.com/item?id=43201974
HN users largely express skepticism and concern over Microsoft disabling extensions in Edge. Several doubt the claim that it's unintentional, citing Microsoft's history of pushing its own products and services. Some suggest it's a bug related to sync or profile management, while others propose it's a deliberate attempt to steer users towards Microsoft's built-in tracking prevention or Edge's own ad platform. The potential for this behavior to erode user trust and push people towards other browsers is a recurring theme. Many commenters share personal anecdotes of Edge's aggressive defaults and unwanted behaviors, further fueling the suspicion around this incident. A few users provide technical insights, suggesting possible mechanisms behind the disabling, like manifest mismatches or corrupted profiles, and offering troubleshooting advice.
The Hacker News comments section for the submitted NeoWin article, "Microsoft begins turning off uBlock Origin and other extensions in Edge," contains a robust discussion with varied perspectives on the issue. Several users express concern and skepticism about Microsoft's motivations, suggesting this move is an attempt to bolster their own advertising revenue or exert more control over the user experience. Some commenters point to the increasing trend of browsers limiting extension functionality and worry about the future of ad blocking and privacy-focused extensions. The potential for abuse and unintended consequences of disabling extensions without explicit user consent is a recurring theme.
Several users share personal anecdotes of extensions being disabled without their knowledge, echoing the article's claims. They discuss the inconvenience and frustration this causes, especially for users who rely on these extensions for accessibility, productivity, or security. There's also speculation about the technical reasons behind the disabling, with some suggesting it may be related to profile syncing issues or conflicts between different versions of Edge.
A counter-narrative emerges from some commenters who argue that the issue might be a bug rather than a deliberate action by Microsoft. They highlight the lack of official confirmation from Microsoft and suggest waiting for further clarification before jumping to conclusions. Some users also point out that extensions being disabled could be a security measure to protect users from malicious or compromised extensions. There's a discussion about the responsibility of extension developers to adhere to browser guidelines and ensure compatibility.
Several commenters delve into technical details, discussing the mechanisms by which Edge manages extensions and the potential points of failure. They speculate about the role of Edge's internal update process and the possibility of corrupted extension data. Some users propose workarounds and troubleshooting steps for those experiencing the issue, such as reinstalling extensions, clearing browser data, or creating a new profile.
Finally, a few comments touch on the broader implications of the issue for the future of the web and the balance of power between browser vendors and extension developers. The discussion highlights the tension between user choice and platform control, and the importance of open standards and transparency in the development of web technologies. Some users express a desire for more robust mechanisms for users to control their browsing experience and protect their privacy.