svcShredditStylingOverrides

Seen 7 time(s) in 1 run(s).

What it sent and what came back (the newest 3 from our runs)

Read from each run's own recording (rule 73), secrets and signed link tokens taken out. Kept in ~/.logCli/rea/clientFacts.json, so it stays after the run is pruned.

runs/inspect/20261025T124815_MaleficentTry8338, step 1: goto /: 200, 3468 ms

Sent:

{
  "query": {
    "v": "0"
  },
  "body": null
}

Answered:

[]

runs/inspect/20261025T124815_MaleficentTry8338, step 3: goto /r/AskReddit/: 200, 536 ms

Sent:

{
  "query": {
    "v": "0"
  },
  "body": null
}

Answered:

[]

runs/inspect/20261025T124815_MaleficentTry8338, step 5: goto /search/: 200, 338 ms

Sent:

{
  "query": {
    "v": "0"
  },
  "body": null
}

Answered:

[]

What it does

This call is part of the page's ad-block check. The slice first asks nu() whether an ad blocker and acceptable ads are on, packs the result into v with lu({isAdblockEnabled, isEyeoPartnered, isAcceptableAdsEnabled}), and fetches /svc/shreddit/styling-overrides/?v=… (rea ev_12bce587…, whose one finding is this endpoint). In every recorded call we sent v=0 and got back an empty list, so no styling was changed. It fired on every page we opened.

What our machine does with it

log-cli's Reddit platform has only log reddit session check (the direct-API engine, with no Reddit client vendored yet) and log inspect in the account's AdsPower browser with no proxy (rule 84). Nothing waits on this call yet: inspect records it and names it in each step's exchanges.json, and SubQ reads it with the rest of the step. If log-cli acts on Reddit, v=0 is worth keeping an eye on: it is what the page reports about ad blocking in our AdsPower browser, and a different value would mean the browser started to look different.

What can go wrong

All seven recorded calls answered 200, the first in 3468 ms and the rest in 305-591 ms. The fetch sits in a try with an empty catch, so a failure is ignored completely and never stops the page or a run.