(feeling woozy today so sorry if i sound weird; had an agent help me with investigation, but ended up writing the issue body myself)
noticed bluesky's app labeler in my moderation prefs. told opencode to investigate — looks like noAppLabelers preference got replaced with ignoredAppLabelers now. Traced it to 8559f5c3b1f48e96e103756a1ab133c8e0bfcb8d and was initially confused to not find any preferences (it populates from unsubscribing to app-labelers?) and also that the AtpAgent is still configured with the default labelers.
Unlike previous noAppLabelers this one doesn't seem to apply to the atproto-accept-labelers header. (I verified this personally in the browser console after "unsubscribing" from Bluesky's default labeler — it's still listed as did:plc:ar7c4by46qjdydhdevvrndac;redact in atproto-accept-labelers)
src/state/session/moderation.ts now unconditionally configures the bluesky default labeler on the wire, and it looks like "ignoring" it merely hides labels from it (if it even does — that part I did not verify). But part of the label enforcement lives on the AppView side — the infamous !takedown, for example. That still gets acted upon. (Last time I checked, the default labeler was hardcoded in the reference AppView, but my agent tells me that's not true anymore — don't have the energy to test it right now, because usually takedowns are applied for a reason and I don't want to see this shit).
Is this intentional? Because from my viewpoint (being able to ignore app labelers) this smells like a regression… 😭️
the previous toggle was broken and I guess this one isn't fully complete. I do want the default labeler to have 0 effect if the user says they don't want it!