Tip: Don't just 📋CP. Remember to search commented-out rules and filters. They are optional, but can enhance the experience on specific devices and scenarios.

You can easily find them using these regexes (*.ubo & *.abp respectively):

^#\S. 

^!\S. 

AKA "User Types".

All file-names that have a stem (basename without extension) in common are considered to belong to the same profile. When you apply a profile to uBO, you are expected to use all files from said profile.

To check if a list of files are part of the same profile, you can use the common_stem fn:

const get_stem = (path: string) => {
	const basename = path.substring(path.lastIndexOf('/')   1)
	const dot_i = basename.lastIndexOf('.')
	return dot_i == -1 ? basename : basename.substring(0, dot_i)
}

const common_stem = (paths: ReadonlySet<string>) =>
	[...paths].every((path, _, path_ls) =>
		get_stem(path_ls[0]) == get_stem(path)
	)

For privileged (Administrator) accounts. These are the only users with (partial) root/System access (AKA "sudoers"), so they need ABSOLUTELY MAXIMUM SECURITY at the cost of convenience. Since admins don't need to browse many websites, the strict-blocking doesn't affect them much.

Any human user, usually my family or friends. They shouldn't be using "Hard-Mode", because literally any site they visit could break, and that's an inconvenience.

Most rules are "just-in-case", for the sake of future-proofing, and lack of information about the behavior of sites.

My own personal rule-set. Designed for my needs, desires, and convictions.

uBO doesn't support comments on dyn-rules.

uBO auto-removes syntactically-invalid lines, and # is unlikely to become valid, so this hack works... as long as each comment is placed on its own line (side-comments will turn the whole line into a comment), so be careful