Uninstall Mac apps with every file they leave behind, and see why each belongs. Free up space, fine-tune macOS, and set up Terminal.
Swift cache-cleanercleanerclideveloper-toolsdisk-cleanupdisk-spaceduplicate-finderhomebrewliquid-glassmac-cleanermacosmacos-appmacos-golden-gatemacos-tahoemacos-tweaksswiftswiftuiterminal-themesuninstalluninstaller
Say in the guide and the safety notes what the name and maker rules do
Țugui Dragoș0e29d32c0477
diff --git a/ARCHITECTURE.md b/ARCHITECTURE.mdindex 6e30c2ff..3d1bb603 100644--- a/ARCHITECTURE.md+++ b/ARCHITECTURE.md@@ -79,18 +79,17 @@ the Homebrew page's uninstall and cleanups are Homebrew's own.page can show progress.2. **Match.** For each file, `LeftoverMatcher` weighs the evidence that it belongs to the app: its bundleidentifier, the identifiers of what the app embeds, its application groups, its signing team, and its name. A- plug-in and a container named by a UUID are also weighed by the identifier they declare: a plug-in's name- says what it does and a UUID says nothing, so the identifier decides whose they are. A launch job is weighed- by the program it runs, since anyone can name its file: a job that runs a program inside the app is the- app's, and one that runs a program inside another installed app is that app's. The answer is a- `LeftoverMatch`: a confidence (`certain`, `likely`, or `possible`), the reason, the other installed apps that- claim the file too (with the apps of the same maker that macOS knows outside the Applications folders, the- apps Peel saw installed before, whose identifiers stay theirs once they are gone, and, for a file only the app's- name claims, another maker's app whose name holds that name as whole words; a file tied to the app only by its- maker's identifier or team, and named for another app of that maker that macOS knows anywhere, such as a build, is- not listed), the- other copies of the app that use it (any macOS knows, wherever they are, named by their place), and, when Peel- holds it back, why (`HoldBack`).+ plug-in and a container named by a UUID are also weighed by the identifier they declare: a plug-in's name says+ what it does and a UUID says nothing, so the identifier decides whose they are. A launch job is weighed by the+ program it runs, since anyone can name its file: a job that runs a program inside the app is the app's, and one+ that runs a program inside another installed app is that app's. The answer is a `LeftoverMatch`: a confidence+ (`certain`, `likely`, or `possible`), the reason, the other installed apps that claim the file too (with the apps+ of the same maker that macOS knows outside the Applications folders, the apps Peel saw installed before, whose+ identifiers stay theirs once they are gone, and, for a file only the app's name claims, another maker's app whose+ name holds that name as whole words; a file tied to the app only by its maker's identifier or team, and named for+ another app of that maker that macOS knows anywhere, such as a build, is not listed), the other copies of the app+ that use it (any macOS knows, wherever they are, named by their place), and, when Peel holds it back, why+ (`HoldBack`).3. **Measure.** `FileSize` walks each folder on a thread of its own, with a time budget. A size is what movingthe item would free: a file that shares its blocks with an APFS clone counts only what it holds alone, and onewith another name outside the folder counts nothing. A folder that doesn't answer in time, or that macOS won'tdiff --git a/GUIDE.md b/GUIDE.mdindex 4f5df33c..ad2cfa62 100644--- a/GUIDE.md+++ b/GUIDE.md@@ -18,6 +18,8 @@ and how to get it, [SAFETY.md](SAFETY.md) what it protects, [PRIVACY.md](PRIVACYinstaller's receipt are selected for you, and so is the folder Homebrew keeps for an app it installed, so thatHomebrew stops listing the app once it is gone. A match on the name alone is only a guess in your home folder, atthe top of a Library, or inside another app's folder or one of Apple's, so it waits under Review Before Removing.+ So does a folder named like the app while another installed app's name holds that name, as Epic Games Launcher+ holds Epic: the folder may be that app's.- **What may exist nowhere else is left to you.** A folder holding a crypto wallet, a signing key, a passworddatabase, or a repository is shown with its reason and not selected, and so is a place where an app keeps whatmay exist only on this Mac, such as local mail, message history, sign-in codes, VPN connections, a game's saves, a@@ -27,7 +29,9 @@ and how to get it, [SAFETY.md](SAFETY.md) what it protects, [PRIVACY.md](PRIVACYall, and neither can anything that syncs to your other devices, an app's container holding your documents, or afolder around a photo or music library. What Peel only guesses at, from the start of a name or an identifier theapp's maker or signing team also uses, waits under Review Before Removing, with what is shared and what Peel held- back.+ back. What is named for another app of the same maker that macOS knows, such as a build Xcode keeps, is that app's+ and isn't listed, and an identifier a tool gives apps whose makers set none, such as Electron's `com.electron.`+ ones, ties no two apps to one maker.- **What only an administrator can move** stays where it is when Peel's helper isn't allowed to move it from there.Once the app is gone, Peel says how many items stayed, and Orphaned Files lists them under Needs an Administrator,with how to remove them in Finder.@@ -82,8 +86,9 @@ Space shows what fills your disk, area by area, and what each area is.names. It also lists the files browsers keep to start a helper program that is gone. Nothing is selected for you.A system extension's copy can't be selected, since only macOS removes it, and its row says how. Peel doesn't listwhat only a guess could tie to an app, so look for it yourself: a folder named only for a maker, such as `Google`- in Application Support, a data folder only the app's documentation names, such as Tor Browser's- `TorBrowser-Data`, and a hidden folder in your home named like an app, since one such as `~/.local` is shared by+ in Application Support, a data folder only the app's documentation names, such as Tor Browser's `TorBrowser-Data`,+ a folder named like a gone app while another installed app's name holds that name, such as one called Epic beside+ Epic Games Launcher, and a hidden folder in your home named like an app, since one such as `~/.local` is shared bymany command-line tools. What only an administrator can move, from a place Peel's helper isn't allowed to move itfrom, is listed apart under Needs an Administrator, with how to remove it in Finder, and so is what an uninstallleft there, which nothing else would tie to the app once it is gone.diff --git a/SAFETY.md b/SAFETY.mdindex 70c5796c..a1af2618 100644--- a/SAFETY.md+++ b/SAFETY.md@@ -281,6 +281,10 @@ Only matches Peel is `certain` or `likely` about, and only when nothing else inswhile another installed app, whoever makes it, holds that name as whole words in its own, as Epic Games Launcherholds Epic: a folder called Epic may be that app's. A word in the name of an app that comes with macOS counts fornothing, and neither does another app's name for what sits in the app's or its maker's own folder.+- **A tool's default names no maker.** Electron's packagers name an app `com.electron.<name>` when its maker sets no+ identifier, Qt names it `com.yourcompany.<name>`, and ToDesktop and install4j write their own, so apps of many+ makers carry them: none of these counts as a maker, and one such app never lists or shares another's files as its+ maker's.- **Another app's data stays with it.** A folder that holds what another installed app keeps as its own, as theDeveloper page names it, such as Xcode's folders in `~/Library/Developer`, is listed with that app named and can'tbe selected: it goes with that app, never with this one.