Something went wrong. Try again.
This string has no description
Something went wrong. Try again.
1.0 kB · 15 lines · Created 5mo ago
123456789101112131415 Base image: ghcr.io/astral-sh/uv:python3.12-bookworm-slim Python: 3.12.12 (GCC 12.2.0) Platform: Linux-6.12.87-fly-x86_64-with-glibc2.36 OpenSSL: 3.0.19 (27 Jan 2026) httpx: 0.28.1 httpcore: 1.0.9 Hosted on: fly.io (IAD region) SDK: our fork of bluesky-social/atproto (oauth-full branch)
The astral-sh/uv + python:3.12-bookworm-slim Docker base is going to be extremely common right now — uv has been growing fast and that's their official image. Pretty much any Python service shipped in the last 6 months that's on uv + slim Debian will share the same OpenSSL build, same cipher list, same JA4. If LeonardoClemente is on a similar uv-based or python:3.x-slim Docker setup, that's almost certainly why the fingerprints collide.
So {}'s read makes sense: it's not us hammering bsky, it's "anything Python-on-Debian-slim using httpx" all sharing the same JA4 fingerprint, and somebody in that fingerprint bucket has a runaway loop. WAF can't differentiate inside a fingerprint.