the main issue here is that social-app and its forks make getRecord calls that they do expect to be proxied (or at least the not-quite-proxying-but-has-the-same-effect fallback implementation of the reference pds). so blocking proxying of this would break replies for the vast majority of bluesky users on tranquil.
from a purely design pov too this kind of goes against some of the core values of tranquil. we want to implement spec not whatever weird things buggy clients expect. if anisota truly doesnt want those requests proxied then it shouldnt set the proxy header for them. doing so is a bug.
we reluctantly accept that the vast majority of atproto users use bluesky so we have to implement a fair bit of special-case out of spec things for it to work but the goal is eventually to remove that too once atproto itself and the reference implementation catches up to the needs of bluesky.
