Differences

This shows you the differences between two versions of the page.

--- writing:conferences [2026/08/27 14:06] – Replace the 2025 stub with a corpus-backed venue map: crawl rates of the seven venues, 2026-08-27 CFPs, and EuroS&P/ACSAC/RAID/AsiaCCS/CHI/SOUPS/ConPro/IWPE. Authored by Claude karel.kubicek.claude
+++ writing:conferences [2026/08/27 14:15] (current) – Refocus as a submission map: where to send the paper and current CFP dates. Move venue_rates.py to provenance — readers do not have the dataset. Authored by Claude karel.kubicek.claude
@@ Line 1: / Line 1: @@
 ====== Conferences and Journals ======
-A web-measurement paper has to land somewhere. The instinct is to send it to "the measurement conference" or "a top-tier security venue" and treat ranking tables as the decision. That is how a crawl of websites ends up at IMC because IMC is in the name, or at IEEE S&P because the H5-index is large, and then the reviews ask why the paper is not a user study, or why it did not measure the Internet.
+This page answers two questions: **where should this web-measurement paper go**, and **what is the current CFP**. It is not a guide to writing, to CORE, or to how a PC works. Date the method, then pick the community that already reviews that method. Then open the CFP linked in the table — the dates age in weeks.
-This page is a venue map for a PhD student who is about to pick. It is not a guide to writing a paper, to CORE, or to how a PC works. Those belong in a methods textbook and in the CFP. What belongs here is what the **seven venues this corpus actually published**, which other venues take the same work and are missing from the corpus, and which deadlines are open as of **2026-08-27**.
+Deadlines below were fetched from each CFP on **2026-08-27** (AoE unless the CFP says otherwise) and will be updated. [[https://sec-deadlines.github.io/|sec-deadlines.github.io]] tracks the security subset only; it does not list WWW, IMC, CHI or TWEB. Do not use it as the source of the dates here.
-The corpus behind the rates is **5,859 extracted papers** from CCS, IMC, NDSS, PETS, USENIX Security, TheWebConf and IEEE S&P, 2010–2026. Only **1,120 (19.1%)** of them ran a crawl. 2025 and 2026 are provisional — CCS 2026 and IMC 2026 contribute **zero** extracted papers (those conferences have not been held relative to the freeze), and IEEE S&P / WWW 2026 are thin by construction. Queries, the unedited report and the CFP fetches are on [[provenance:writing:conferences]]. Corpus-wide caveats: [[Literature:Corpus]]. The seven-venue SoK trap is on [[Writing:Literature review]].
 <WRAP important>
-**IMC is not the venue that crawls the web most often. The Web Conference is.**
+**Do not send a website crawl to IMC because IMC has "measurement" in the name.** IMC reviews the Internet as an operational network (paths, DNS, CDN, TLS ecosystem). A crawl of websites belongs at **The Web Conference** first; at **PETS** if the claim is tracking, consent, or a privacy mechanism; at a security flagship if the claim is an attack, a defence, or a vulnerability in the wild.
-Of each venue's own extracted papers:
-  * The Web Conference: **242 of 843 crawled (28.7%)**.
-  * PETS / PoPETs: **123 of 510 (24.1%)**.
-  * IMC: **132 of 638 (20.7%)**.
-  * IEEE S&P is last: **110 of 767 (14.3%)**.
-IMC **is** the venue that is almost only empirical: **625 of 638 (98.0%)** scored ''isEmpirical'', and the **lowest** human-subjects share (**67 of 638, 10.5%**). That is not the same as "almost only publishes measurement" — empirical includes analyses of existing datasets. PETS is the opposite on people: **215 of 510 (42.2%)** have a ''participants[]'' record. A ranking of what the literature //did// is not advice about where to send the paper you are writing now. Date the method, then pick the community that reviews that method.
+Of the seven venues this wiki is built from, WWW papers crawl most often, then PETS, then IMC. IEEE S&P crawls least. IMC **is** almost only empirical — that is not the same as "almost only publishes measurement". The rates and the reprint script are on [[provenance:writing:conferences]] (the script needs the extraction; readers of this page do not have it).
 </WRAP>
 <WRAP tip>
-As of 2026-08-27, **open research-paper deadlines** for this map (AoE unless the CFP says otherwise):
+**Open research-paper deadlines** as of 2026-08-27:
   * **PETS 2027 Issue 2** — 31 August 2026 ([[https://www.petsymposium.org/cfp27.php|CFP]]). Then Issue 3 on 30 November 2026 and Issue 4 on 28 February 2027.
@@ Line 30: / Line 21: @@
   * **USENIX Security '27 cycle 2** — registration 19 January 2027, paper 26 January 2027 ([[https://www.usenix.org/conference/usenixsecurity27/call-for-papers|CFP]]). Cycle 1 registration closed 18 August 2026; paper closed 25 August 2026. Denver, 11–13 August 2027.
-NDSS 2027, CCS 2026, IMC 2026, EuroS&P 2026, ACSAC 2026 papers, RAID 2026, SOUPS 2026, ConPro '26 and IWPE '26 are **closed**. CCS 2027 is a stub ("Coming in October 2027, Atlanta"). EuroS&P 2027, IMC 2027, SOUPS 2027, ConPro '27 and IWPE '27 CFPs were not posted at check time. Re-read the CFP: this table ages in weeks, not years. [[https://sec-deadlines.github.io/|sec-deadlines.github.io]] tracks the security subset.
+NDSS 2027, CCS 2026, IMC 2026, EuroS&P 2026, ACSAC 2026 papers, RAID 2026, SOUPS 2026, ConPro '26 and IWPE '26 are **closed**. CCS 2027 is a stub ("Coming in October 2027, Atlanta"). EuroS&P 2027, IMC 2027, SOUPS 2027, ConPro '27 and IWPE '27 CFPs were not posted at check time.
 </WRAP>
-===== How to pick =====
+===== Where to send it =====
-Match the **object you measured** to the community that already publishes that object, then check the CFP's own scope sentence.
+Match the **object you measured** to the community that already publishes that object, then read the CFP's own scope sentence.
-  * **A sample of websites, crawled.** The Web Conference first (it is the web venue, and it is the crawl-heaviest of the seven). PETS if the claim is about tracking, consent, or a privacy mechanism. A security venue if the claim is an attack, a defence, or a vulnerability in the wild. IMC only if the contribution is also a measurement of the Internet — path, DNS, CDN, TLS ecosystem — not merely "we used Tranco".
+  * **A sample of websites, crawled.** The Web Conference first (it is the web venue). PETS if the claim is about tracking, consent, or a privacy mechanism. A security venue if the claim is an attack, a defence, or a vulnerability in the wild. IMC only if the contribution is also a measurement of the Internet — not merely "we used Tranco".
-  * **The Internet as an operational network.** IMC. RAID explicitly solicits "security measurement studies". PAM is the other dedicated measurement venue; it is not in this corpus and this sitting did not fetch a 2027 CFP.
+  * **The Internet as an operational network.** IMC. RAID explicitly solicits "security measurement studies". PAM is the other dedicated measurement venue; a 2027 CFP was not fetched in this sitting.
   * **A privacy mechanism, a tracker, a consent signal.** PETS (journal issues four times a year, symposium in July). IEEE S&P and USENIX Security take the same papers when the contribution is a new attack or system.
-  * **People using security or privacy UI.** SOUPS first; CHI if the contribution is an HCI result that happens to be about security. PETS takes some of this (**42.2%** of its extracted papers have participants). IMC almost does not (**10.5%**).
+  * **People using security or privacy UI.** SOUPS first; CHI if the contribution is an HCI result that happens to be about security. PETS takes people studies; IMC almost does not.
-  * **Consumer protection / dark patterns / deceptive UI, with a measurement.** ConPro (IEEE S&P workshop). Check whether that year's workshop has proceedings before you treat it as archival. The content page [[Privacy:Darkpatterns]] is the measurement, not the venue.
+  * **Consumer protection / dark patterns / deceptive UI, with a measurement.** ConPro (IEEE S&P workshop). Check whether that year's workshop has proceedings before you treat it as archival. The measurement page is [[Privacy:Darkpatterns]], not this one.
   * **Privacy engineering (translating law and requirements into systems).** IWPE (EuroS&P workshop).
   * **Usable-security measurement that needs a full paper, not a workshop.** SOUPS or CHI, not a security-flagship cycle that will ask for a new attack.
-Stafeev and Pellegrino {[stafeev2024_state]} started from **the same seven venues** this corpus uses. They are a crawling SoK, not a venue guide, and they then keyword-cut. Use them as the sibling for "these venues, then a filter", not as a list of where to submit.
+Stafeev and Pellegrino {[stafeev2024_state]} started from the same seven venues this wiki uses. They are a crawling SoK, not a venue guide. Use them as the sibling for "these venues, then a filter", not as a list of where to submit.
-===== The seven venues this corpus is built from =====
+===== Current CFPs =====
-Rates are **of that venue's extracted papers**, not of 5,859. USENIX is the largest slice of the corpus (**1,410 / 5,859 = 24.1%**) because USENIX Security is large, not because it is where web measurement lives. The crawl-rate column is the one that answers "does this venue actually publish crawls?".
+Venue name is the CFP. "Rolling" on older notes meant **two to four discrete cycles**, not a continuous deadline. CCS, USENIX Security, IEEE S&P and NDSS all forbid resubmitting a paper rejected in cycle 1 of the same year to cycle 2 (read the current CFP: the embargo text moves). PETS skips one issue. IMC 2026 offered a one-shot revision instead.
-The script below reprints the ranking. It is the whole lesson in one table: WWW, then PETS, then IMC.
+^ Venue (CFP) ^ Next paper deadline (2026-08-27) ^ Conference ^ Why a web-measurement paper goes here ^
+| [[https://www.petsymposium.org/cfp27.php|PETS / PoPETs 2027]] | **Open.** Issue 2: 31 Aug 2026; Issue 3: 30 Nov 2026; Issue 4: 28 Feb 2027. Journal-style accept / revise / reject; a reject skips an issue. | 19–24 Jul 2027 | Privacy: trackers, consent, mechanisms. The human-subjects venue among the seven. PoPETs is the journal; PETS is the symposium. |
+| [[https://chi2027.acm.org/authors/papers/|CHI 2027]] | **Open.** 10 Sep 2026 AoE. No separate abstract deadline. Author list frozen at submission. Assisted desk-reject in 2027. | 10–14 May 2027, Pittsburgh | **The** HCI venue. Use it when the contribution is about people and interfaces, including usable security. Not a substitute for IMC or WWW. |
+| [[https://www2027.thewebconf.org/research-track-papers/|The Web Conference 2027]] | **Open.** Abstract 18 Oct 2026; paper 25 Oct 2026 AoE. Dates: [[https://www2027.thewebconf.org/important-dates/|important-dates]]. | 10–14 May 2027, Dublin | The web, including crawls. First choice for a sample of websites. |
+| [[https://sp2027.ieee-security.org/cfpapers.html|IEEE S&P 2027]] | **Open (cycle 2).** Abstract 10 Nov 2026, paper 17 Nov 2026 AoE. Author list frozen at abstract registration. Cycle 1 closed 11 Jun 2026. | 17–19 May 2027, Montreal; workshops 20 May | Flagship security/privacy. Has an SoK track; surveys without insights may be rejected. Lowest crawl rate of the seven. |
+| [[https://asiaccs2027.cityu.edu.mo/call-for-papers/|AsiaCCS 2027]] | **Open (cycle 2).** 11 Dec 2026 AoE. Cycle 1 closed 21 Aug 2026. | 12–16 Jul 2027, Macau | ACM's Asia security flagship. Same family as CCS; CFP discourages purely theoretical crypto and ML-only papers. |
+| [[https://www.usenix.org/conference/usenixsecurity27/call-for-papers|USENIX Security '27]] | **Open (cycle 2).** Registration 19 Jan 2027, paper 26 Jan 2027. Cycle 1 registration closed 18 Aug 2026; paper closed 25 Aug 2026. Open Science appendix required; 13-page body; at most seven papers per author per cycle. | 11–13 Aug 2027, Denver | Flagship security/privacy. |
+| [[https://www.sigsac.org/ccs/CCS2026/call-for/call-for-papers.html|ACM CCS 2026]] | Closed (paper 14 Jan and 29 Apr 2026). CCS 2027 is [[https://www.sigsac.org/ccs/CCS2027/|a stub]]: October 2027, Atlanta, CFP not posted. | 15–19 Nov 2026, The Hague | Flagship security. |
+| [[https://www.ndss-symposium.org/ndss2027/submissions/call-for-papers/|NDSS 2027]] | Closed (summer 6 May 2026; fall 19 Aug 2026). | 22–26 Mar 2027, Seoul | Flagship security. |
+| [[https://conferences.sigcomm.org/imc/2026/cfp/|IMC 2026]] | Closed (20 Nov 2025 and 29 Apr 2026). One-shot revision across cycles. IMC 2027 CFP not posted (''/imc/2027/'' is 404). | 12–16 Oct 2026 | Internet measurement — the network, not "we crawled websites". |
+| [[https://eurosp2026.ieee-security.org/cfp.html|EuroS&P]] | 2026 paper closed 20 Nov 2025. **2027 CFP not posted.** Historically a November deadline. | 6–10 Jul 2026, Lisbon | The European sibling of IEEE S&P. Same security/privacy scope, including measurement. |
+| [[https://www.acsac.org/2026/submissions/papers/|ACSAC]] | 2026 papers closed 26 May 2026. Case-study / poster / workshop tracks still listed as open on the home page — that is not the research-paper track. | 7–11 Dec 2026, Los Angeles | Applied security, including web. |
+| [[https://raid2026.org/call.html|RAID]] | 2026 papers closed 16 Apr 2026. | 11–14 Oct 2026, Lancaster, UK | CFP explicitly encourages measurement studies, public tools/datasets, and experience papers. Second choice when IMC is the wrong community. |
+| ESORICS | 2026 conference happened. The Call-for-Papers subpage on the 2026 site returned 404 at check time; **2027 CFP not posted.** Do not copy last year's "January and April" from memory. | 14–18 Sep 2026, Rome | Long-running European security symposium. |
+| [[https://www.usenix.org/conference/soups2026|SOUPS]] | 2026 papers closed 19 Feb 2026. 2027 CFP not posted. | 23–26 Aug 2026 (soups.page) / 24–26 Aug 2026 (USENIX proceedings page), Hannover | Usable privacy and security. First-choice full-paper venue for a measurement of people and security UI. In-cooperation with USENIX; 2026 proceedings are a USENIX publication. |
+| [[https://conpro26.ieee-security.org/cfp.html|ConPro]] | ConPro '26 paper closed 22 Jan 2026; workshop was 21 May 2026 with S&P 2026 in San Francisco. ConPro '27 not posted. | S&P 2027 workshops: 20 May 2027, Montreal | IEEE S&P workshop on technology and consumer protection: dark patterns, deceptive practices, measurement a regulator could use. Confirm proceedings before citing it as archival. |
+| [[https://iwpe.info/|IWPE]] | IWPE '26 paper closed 26 Feb 2026; workshop was 6 Jul 2026, Lisbon (listed on the EuroS&P 2026 workshops page). IWPE '27 not posted. | with EuroS&P | Privacy engineering: turning legal requirements into systems, not a new crawl of trackers. |
-<file python venue_rates.py>
+**PoPETs** is the journal; a PETS deadline is a PoPETs issue deadline. **ACM Transactions on the Web (TWEB)** is the web journal this field already uses for surveys that are not SoKs — Laperdrix, Bielova, Baudry and Avoine {[laperdrix2020_survey]} is the fingerprinting survey [[Privacy:Fingerprinting]] sends you to. TWEB has no conference cycle; check the journal's current author instructions. IEEE TDSC and similar take some measurement; they are not the first place a web-crawl paper goes.
-#!/usr/bin/env python3
-"""Print crawl / empirical / human-subjects rates per venue.
-The seven-venue extraction is not a web-measurement corpus. This script is
-the table on writing:conferences: of the papers each venue actually published
-in extract/run1, how many crawled, how many are empirical, how many recruited
-human participants.
-Fails if extract/run1 is missing, if a record has no venue, year or slug, or if
-the crawled definition disagrees with lib.mjs (crawlConfig present OR
-automated-web-crawl in studyTypes).
-Usage:
-    uv run python pages/venue_rates.py
-"""
-from __future__ import annotations
-import json
-from pathlib import Path
-ROOTS = [
-    Path("/workspace/publications_dataset/data"),
-    Path("/workspace/publications_dataset"),
-]
-VENUE_ORDER = ["WWW", "PETS", "IMC", "NDSS", "CCS", "USENIX", "IEEE-SP"]
-VENUE_LABEL = {
-    "WWW": "The Web Conference",
-    "PETS": "PETS / PoPETs",
-    "IMC": "IMC",
-    "NDSS": "NDSS",
-    "CCS": "ACM CCS",
-    "USENIX": "USENIX Security",
-    "IEEE-SP": "IEEE S&P",
-}
-def data_root() -> Path:
-    for root in ROOTS:
-        if (root / "extract/run1/extractions.jsonl").is_file():
-            return root
-    raise FileNotFoundError(
-        "extract/run1/extractions.jsonl not found under "
-        + ", ".join(str(r) for r in ROOTS)
-    )
-def is_crawled(p: dict) -> bool:
-    return p["crawlConfig"] is not None or "automated-web-crawl" in p["studyTypes"]
-def is_empirical(p: dict) -> bool:
-    return p["isEmpirical"] is True
-def is_human_subjects(p: dict) -> bool:
-    return len(p["participants"]) > 0
-def pct(n: int, d: int) -> str:
-    if d == 0:
-        raise ZeroDivisionError("venue has zero papers")
-    return f"{100 * n / d:.1f}%"
-def main() -> None:
-    path = data_root() / "extract/run1/extractions.jsonl"
-    rows: list[dict] = [json.loads(line) for line in path.read_text().splitlines() if line]
-    if not rows:
-        raise RuntimeError(f"no extraction records in {path}")
-    by_venue: dict[str, list[dict]] = {v: [] for v in VENUE_ORDER}
-    for p in rows:
-        v = p["venue"]
-        if v not in by_venue:
-            raise RuntimeError(f"unexpected venue {v!r} on {p['year']}/{p['slug']}")
-        _year = p["year"]
-        _slug = p["slug"]
-        if _year is None or _slug is None or _slug == "":
-            raise RuntimeError(f"missing year or slug on venue {v!r}: year={_year!r} slug={_slug!r}")
-        by_venue[v].append(p)
-    crawled = [p for p in rows if is_crawled(p)]
-    print(f"extracted {len(rows)}  crawled {len(crawled)}  ({pct(len(crawled), len(rows))} of extracted)")
-    print()
-    header = (
-        f"{'Venue':<22} {'Papers':>6} {'Crawled':>18} {'Empirical':>18} {'Human subj.':>18}"
-    )
-    print(header)
-    print("-" * len(header))
-    for v in VENUE_ORDER:
-        g = by_venue[v]
-        n = len(g)
-        cr = sum(1 for p in g if is_crawled(p))
-        emp = sum(1 for p in g if is_empirical(p))
-        hs = sum(1 for p in g if is_human_subjects(p))
-        print(
-            f"{VENUE_LABEL[v]:<22} {n:>6} "
-            f"{cr:>5}/{n:<5} {pct(cr, n):>5} "
-            f"{emp:>5}/{n:<5} {pct(emp, n):>5} "
-            f"{hs:>5}/{n:<5} {pct(hs, n):>5}"
-        )
-    missing = [v for v in VENUE_ORDER if len(by_venue[v]) == 0]
-    if missing:
-        raise RuntimeError(f"venues with zero papers: {missing}")
-if __name__ == "__main__":
-    main()
-</file>
-Real output, 2026-08-27, against extract/run1:
-<code>
-extracted 5859  crawled 1120  (19.1% of extracted)
-Venue                  Papers            Crawled          Empirical        Human subj.
---------------------------------------------------------------------------------------
-The Web Conference        843   242/843   28.7%   740/843   87.8%   170/843   20.2%
-PETS / PoPETs             510   123/510   24.1%   477/510   93.5%   215/510   42.2%
-IMC                       638   132/638   20.7%   625/638   98.0%    67/638   10.5%
-NDSS                      701   129/701   18.4%   586/701   83.6%   144/701   20.5%
-ACM CCS                   990   163/990   16.5%   818/990   82.6%   186/990   18.8%
-USENIX Security          1410   221/1410  15.7%  1226/1410  87.0%   367/1410  26.0%
-IEEE S&P                  767   110/767   14.3%   646/767   84.2%   208/767   27.1%
-</code>
-^ Venue (link is the CFP) ^ Next paper deadline (2026-08-27) ^ Conference ^ What a web-measurement paper is doing there ^
-| [[https://www2027.thewebconf.org/research-track-papers/|The Web Conference 2027]] | Abstract 18 Oct 2026; paper 25 Oct 2026 AoE | 10–14 May 2027, Dublin | The web, including crawls. Highest crawl rate in this corpus. |
-| [[https://sp2027.ieee-security.org/cfpapers.html|IEEE S&P 2027]] | Cycle 2: abstract 10 Nov 2026, paper 17 Nov 2026 AoE. Author list frozen at abstract registration. Cycle 1 closed 11 Jun 2026. | 17–19 May 2027, Montreal | Flagship security/privacy. Lowest crawl rate of the seven (**14.3%**). Has an SoK track; surveys without insights may be rejected. |
-| [[https://www.usenix.org/conference/usenixsecurity27/call-for-papers|USENIX Security '27]] | Cycle 2: registration 19 Jan 2027, paper 26 Jan 2027. Cycle 1 registration closed 18 Aug 2026; paper closed 25 Aug 2026. Open Science appendix required; 13-page body; at most seven papers per author per cycle. | 11–13 Aug 2027, Denver | Flagship security/privacy. Largest slice of this corpus (**1,410** papers) because the venue is large. |
-| [[https://www.sigsac.org/ccs/CCS2026/call-for/call-for-papers.html|ACM CCS 2026]] | Both 2026 cycles closed (paper 14 Jan and 29 Apr 2026). CCS 2027 is [[https://www.sigsac.org/ccs/CCS2027/|a stub]]: October 2027, Atlanta, CFP not posted. | 15–19 Nov 2026, The Hague | Flagship security. **96** of **990** extracted CCS records are posters (''poster-'' slug or ''Poster:'' title) — **9.7%**. A CCS silence rate that includes posters is inflated. |
-| [[https://www.ndss-symposium.org/ndss2027/submissions/call-for-papers/|NDSS 2027]] | Summer cycle closed 6 May 2026; fall cycle closed 19 Aug 2026. | 22–26 Mar 2027, Seoul | Flagship security. Crawl rate **18.4%**. Four NDSS venue-years in the index contribute **zero** extracted papers (2010, 2011, 2016, 2018). |
-| [[https://conferences.sigcomm.org/imc/2026/cfp/|IMC 2026]] | Both cycles closed (20 Nov 2025 and 29 Apr 2026). One-shot revision across cycles. IMC 2027 CFP not posted (''/imc/2027/'' is 404). | 12–16 Oct 2026 | Internet measurement. **98.0%** empirical, **10.5%** human-subjects. Not the crawl leader. **42** posters (**6.6%**). |
-| [[https://www.petsymposium.org/cfp27.php|PETS / PoPETs 2027]] | Issue 2: 31 Aug 2026; Issue 3: 30 Nov 2026; Issue 4: 28 Feb 2027. Journal-style accept / revise / reject; a reject skips an issue before resubmission. | 19–24 Jul 2027 | Privacy. Journal (PoPETs) plus a symposium. Second-highest crawl rate (**24.1%**) and the highest human-subjects share (**42.2%**). Five PETS venue-years 2010–2014 contribute **zero** extracted papers. |
-"Rolling" in the previous revision of this page meant **two to four discrete cycles**, not a continuous deadline. CCS, USENIX Security, IEEE S&P and NDSS all forbid resubmitting a paper rejected in cycle 1 of the same year to cycle 2 (read the current CFP: the embargo text moves). PETS skips one issue. IMC offers a one-shot revision instead.
-===== Other venues that take web-measurement work =====
-None of these are in the 5,859. A rate about "how often EuroS&P publishes crawls" **cannot be produced here**. What the corpus can say is how often the seven-venue papers **name** them (full-text upper bounds, 4 papers missing ''paper.cols.txt''). Those counts are citations and related-work lists, not publications at the named venue. RAID's bare token also matches disk RAID; the table uses the strict pattern (a year or the full symposium name).
-^ Venue ^ ICORE2026 ^ Scholar h5 (2020–2024) ^ Next paper deadline (2026-08-27) ^ Suitability for web measurement ^ Mentions in the 5,859 (upper bound) ^
-| [[https://eurosp2026.ieee-security.org/cfp.html|EuroS&P]] | A | 52 | 2026 paper closed 20 Nov 2025; conference 6–10 Jul 2026, Lisbon. **2027 CFP not posted.** Historically a November deadline. | The European sibling of IEEE S&P. Same security/privacy scope, including measurement. | 750 (12.8%) |
-| [[https://www.acsac.org/2026/submissions/papers/|ACSAC]] | A | 40 | 2026 papers closed 26 May 2026. Conference 7–11 Dec 2026, Los Angeles. Case-study / poster / workshop tracks still listed as open on the home page — that is not the research-paper track. | Applied security, including web. The previous revision of this page put Scimago **76** in the H5 column; Scholar's h5 for "Computer Security Applications Conference" is **40**. | 852 (14.5%) |
-| [[https://raid2026.org/call.html|RAID]] | A | 28 | 2026 papers closed 16 Apr 2026. Conference 11–14 Oct 2026, Lancaster, UK. | CFP explicitly encourages measurement studies, public tools/datasets, and experience papers. A natural second choice when IMC is the wrong community. | 438 strict (7.5%); 558 bare-token (9.5%, homograph) |
-| [[https://asiaccs2027.cityu.edu.mo/call-for-papers/|AsiaCCS]] | A | 41 | Cycle 2: 11 Dec 2026 AoE. Cycle 1 closed 21 Aug 2026. Conference 12–16 Jul 2027, Macau. | ACM's Asia security flagship. Same family as CCS; CFP discourages purely theoretical crypto and ML-only papers. | 652 (11.1%) |
-| ESORICS | A | 34 | 2026 conference 14–18 Sep 2026, Rome. The Call-for-Papers subpage on the 2026 site returned 404 at check time; **2027 CFP not posted.** | Long-running European security symposium. Do not copy last year's "January and April" from memory — this sitting could not confirm a live 2027 cycle. | 588 (10.0%) |
-| [[https://chi2027.acm.org/authors/papers/|CHI]] | A* | 139 | 10 Sep 2026 AoE. No separate abstract deadline. Assisted desk-reject in 2027; author list frozen at submission. Conference 10–14 May 2027, Pittsburgh. | **The** HCI venue. Use it when the contribution is about people and interfaces, including usable security. Not a substitute for IMC or WWW. | 889 (15.2%); sample contexts were CHI proceedings citations, not chi-square |
-| [[https://www.usenix.org/conference/soups2026|SOUPS]] | A | 35 | 2026 papers closed 19 Feb 2026. Conference 23–26 Aug 2026 (soups.page) / 24–26 Aug 2026 (USENIX proceedings page), Hannover. 2027 CFP not posted. | Usable privacy and security. The first-choice full-paper venue for a measurement of people and security UI. In-cooperation with USENIX; 2026 proceedings are a USENIX publication. | 886 (15.1%); at least one hit is the email local-part ''soups@narus.com'' |
-h5-index values are Google Scholar Metrics for articles dated 2020–2024, fetched 2026-08-27. They are not a quality ordering of web-measurement venues: CHI's 139 says it is a large HCI venue, not that a crawl paper belongs there. ICORE is CORE's 2026 successor; A* is 7.52% of 825 ranked venues.
-===== Workshops =====
-Workshops are how a measurement that is not yet a flagship paper gets a specialist audience. They are also how a paper fails to count as archival. Read whether that year has proceedings.
-^ Workshop ^ Host ^ 2026 status (checked 2026-08-27) ^ When it is the right place ^ Mentions in the 5,859 ^
-| [[https://conpro26.ieee-security.org/cfp.html|ConPro]] (Workshop on Technology and Consumer Protection) | IEEE S&P | ConPro '26: paper 22 Jan 2026 (closed); workshop 21 May 2026 with S&P 2026 in San Francisco. ConPro '27 not posted. S&P 2027 workshops are 20 May 2027, Montreal. | Consumer protection, dark patterns, deceptive practices, measurement that a regulator could use. Confirm proceedings before citing it as archival. | 64 (1.1%) |
-| [[https://iwpe.info/|IWPE]] (International Workshop on Privacy Engineering) | EuroS&P | IWPE '26: paper 26 Feb 2026 (closed); workshop 6 Jul 2026, Lisbon. Listed on the EuroS&P 2026 workshops page. IWPE '27 not posted. | Privacy engineering: turning legal requirements into systems, not a new crawl of trackers. | 22 (0.4%) |
-IEEE S&P 2026's other workshops on the ''SPW2026'' index were ConPro, CyberBio and Data4SoftSec. IWPE was not among them.
-===== Journals =====
-**PoPETs** is the journal. PETS is the symposium that talks about the year's issues. A PETS deadline is a PoPETs issue deadline. That is current practice, not a 2015-era workshop.
-**ACM Transactions on the Web (TWEB)** is the web journal this field already uses for surveys that are not SoKs. Laperdrix, Bielova, Baudry and Avoine {[laperdrix2020_survey]} is the fingerprinting survey [[Privacy:Fingerprinting]] sends you to; it is a TWEB paper, not one of the seven venues. **137** of 5,859 extracted papers mention TWEB or "Transactions on the Web" (upper bound). TWEB has no conference cycle; check the journal's current CFP / author instructions rather than a month.
-This sitting did not add an "engineering journal" row. IEEE TDSC and similar take some measurement; they are not the first place a web-crawl paper goes.
 ===== What the CFP will actually freeze =====
-These are process facts from the 2026-08-27 CFPs, not folklore about "what reviewers want":
+Process facts from the 2026-08-27 CFPs, not folklore about "what reviewers want":
   * **IEEE S&P** freezes title, abstract, full author list with ORCIDs, and conflicts at the **abstract-registration** deadline, a week before the paper. Cycle 1 paper deadline was 11 June 2026, not 12 June (an off-by-one that circulated in secondary notes).
@@ Line 236: / Line 72: @@
   * **PETS** is four issues, revise-or-skip-an-issue, symposium in July.
   * **IMC 2026** ran two deadlines and a one-shot revision. The replicability track needed an earlier expression of interest.
-Conference-specific advice of the form "IMC likes graphs" is still a TODO: it is subjective, and this corpus cannot score review-style.
 ===== Rankings, used as a fallback =====
@@ Line 245: / Line 79: @@
   * **ICORE2026** (CORE's successor): A* for CCS, CHI, IEEE S&P, NDSS, USENIX Security, WWW. A for ACSAC, AsiaCCS, EuroS&P, ESORICS, IMC, PETS, RAID, SOUPS. [[https://portal.core.edu.au/conf-ranks/|portal.core.edu.au]].
   * **Google Scholar Metrics** h5-index, 2020–2024 window, 2026-08-27: CHI 139, WWW 120, USENIX Security 116, IEEE S&P 110, CCS 90, NDSS 72, PoPETs 56, EuroS&P 52, IMC 43, AsiaCCS 41, ACSAC 40, SOUPS 35, ESORICS 34, RAID 28. Subtopic lists: [[https://scholar.google.com/citations?view_op=top_venues&hl=en&vq=eng_computersecuritycryptography|Security and Cryptography]], [[https://scholar.google.com/citations?view_op=top_venues&hl=en&vq=eng_humancomputerinteraction|HCI]]. H5 is susceptible to manipulation; it is still better than mixing Scholar with Scimago, which is what the previous revision of this page did for IMC and ACSAC.
-[[https://sec-deadlines.github.io/|sec-deadlines.github.io]] lists security/privacy CFPs by deadline. It does not list WWW, IMC, CHI or TWEB. It is a tracker, not a source of the dates on this page — those were fetched from each CFP.
-===== Remaining TODOs =====
 <WRAP todo>
-  * Conference-specific writing advice beyond CFP process (reviewer taste, typical page budgets as they feel in review, how IMC vs WWW want related work structured). Subjective; still useful; not in this sitting.
+  * Conference-specific writing advice beyond CFP process (reviewer taste, how IMC vs WWW want related work structured).
-  * Engineering venues as a separate family. The current answer is: WWW's research tracks plus IMC cover "I built a crawler / a measurement infrastructure". ICWE (Web Engineering) was not fetched. NSDI/OSDI/ATC take networked systems, not website crawls.
+  * Engineering venues as a family. WWW's research tracks plus IMC cover "I built a crawler". ICWE was not fetched. NSDI/OSDI/ATC take networked systems, not website crawls.
-  * PAM 2027 CFP. Named above as the other measurement venue; no deadline row.
+  * PAM 2027 CFP.
   * EuroS&P 2027, IMC 2027, CCS 2027, SOUPS 2027, ACSAC 2027, ConPro '27, IWPE '27, ESORICS 2027 — CFPs not posted or not found on 2026-08-27. Update the open-deadline box when they appear.
   * SOUPS 2026 conference dates disagree: soups.page says 23–26 August, the USENIX proceedings page says 24–26 August.
@@ Line 260: / Line 90: @@
 ===== Related Pages =====
+  * [[provenance:writing:conferences]] — crawl / empirical / human-subjects rates, the reprint script (needs the extraction), CFP fetches, review log.
   * [[Writing:Literature review]] — the keyword-derived denominator trap, measured on the SoKs in these same seven venues.
-  * [[Literature:Corpus]] — how the 5,859 were selected; the nine venue-years that contribute nothing.
+  * [[Literature:Corpus]] — how the seven-venue corpus was selected.
   * [[Design:Website selection]] — Tranco / Radar / CrUX, which is a different question from where the paper goes.
-  * [[Programming:Crawler]] — the crawl instruments the WWW/PETS papers above actually used.
+  * [[Programming:Crawler]] — the crawl instruments WWW/PETS papers actually used.
   * [[Privacy:Darkpatterns]] — a topic ConPro is built for.
-  * [[Statistics:Study preregistration]] — PETS and USENIX Security are where most of the 15 preregistrations in this corpus sit; the venue choice is part of when you can freeze a plan.
+  * [[Statistics:Study preregistration]] — PETS and USENIX Security are where most of the preregistrations in this corpus sit; the venue choice is part of when you can freeze a plan.
-===== Methodology and limitations of these figures =====
-Every corpus rate on this page is produced by ''scripts/report_conferences.mjs'' (and the short ''pages/venue_rates.py'' reprint). The population of each rate is that venue's extracted papers, or the 1,120 crawled papers, never "all 5,859" except where the share of the corpus is the point (USENIX 24.1%). Posters are identified by a ''poster-'' slug or a ''Poster:'' title. Out-of-corpus venue rows are **mention sweeps**, labelled as upper bounds; RAID has a strict pattern and a loose homograph. Deadlines, ICORE ranks and Scholar h5 values are external and were fetched on 2026-08-27; ''scripts/external_checks_conferences.sh'' re-fetches them. Full query log, residue, quote samples and the review log: [[provenance:writing:conferences]]. Corpus-wide caveats: [[Literature:Corpus]].
 ====== References ======