What the sources actually say

The official documentation describes a multiple-strategies mechanism: nfqws can apply different desync strategies to different requests through multiple desync profiles, delimited by the --new parameter. Each profile carries a filter. Hard filter parameters — IP version, ipset and TCP/UDP port range — are always identifiable immediately, even before the hostname is known. Hostlists can also act as filters and can be combined with hard parameters.

Profiles are matched from first to last until a filter matches, and a final empty profile numbered 0 catches whatever matched nothing. The documentation warns about a subtle behavior: a connection can be served by one profile before its hostname is known and switch to another profile afterwards, so 0-phase desync methods need careful thought in multi-profile setups.

The same section ends with a warning that matters for anyone assembling per-service setups: multiple strategies exist only for cases where everything cannot be combined into one strategy, and copy-pasting blockcheck results for different websites into multiple strategies leads to a mess that may never unblock all resources.

On the community side, the Flowseal Windows build ships several ready-made strategy files whose README advises trying different strategies — ALT, FAKE and others — until one works, explicitly noting that effectiveness depends on many factors. Community discussions such as Discussion #251 (YouTube) and Discussion #7899 (Discord, YouTube and games) contain user-shared parameter sets and batch-file tweaks. Those are individual reports from specific providers, versions and environments, not tested configurations from the upstream author.

Any community-shared BAT configuration is version- and environment-specific. A strategy file that one discussion participant reported as working on their ISP can fail or break other services on yours, and older files may reference parameters or fake-packet files that current builds no longer ship.

How targeted profiles work, step by step

  1. Start from the principle the documentation states: prefer one combined strategy, and split into multiple profiles only when a single strategy genuinely cannot cover your targets.
  2. Define each profile with --new and attach its filter — hard parameters such as ipset or port range when you can identify traffic without a hostname, hostlists when the hostname is the reliable signal.
  3. Order profiles deliberately, because matching runs from the first profile to the last and stops at the first match; the empty profile 0 handles the rest.
  4. Use hostlist-exclude semantics to carve exceptions out of a broad profile — for example keeping a domain untouched even when its IP range sits inside an ipset include filter, the exact use case the build README gives for its exclude lists.
  5. Beware 0-phase methods in switching setups: the documentation notes that some methods constrained to connection establishment behave differently when a profile switch happens mid-connection.
  6. Test every service you rely on after any change, not only the one you targeted — community threads repeatedly show a Discord-oriented tweak breaking YouTube or the reverse.

What is source-backed vs community-reported

  • Source-backed (official documentation): multiple desync profiles with --new, hard and hostlist filter matching order, the empty profile 0, the profile-switch caveat, and the warning against stitching together blockcheck outputs.
  • Source-backed (build README): the Flowseal build ships multiple named strategy files and itself recommends trying alternatives until one works in your environment.
  • Community-reported (Discussions #251 and #7899): specific parameter combinations, per-service tweaks and strategy preferences shared by participants for their own providers and builds.

When the reported workaround may not apply

A targeted strategy is only as portable as the assumptions inside it: the DPI behavior of one ISP, the hostname set of one service at one point in time, and the parameter support of one build version. Community strategy files from discussions are historical snapshots — services change CDN infrastructure and providers change DPI rules, so a hostlist that was precise when posted can silently drift out of date. The official documentation position stands: no hostlist-based profile layout is universally best, and Zapret does not guarantee access for every ISP, browser or region.