Here's the graph you wanted, which I didn't post because it looks like incomprehensible chaos.
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 representing the AP federation API as a singular monolithic node here is misleading. every edge between AP servers represents each implementation of a federation API.
uninformed people are going to see this and think "duhh AP is centralized" are you on any psych meds?
Discussion
From the AP server's perspective, my graph is correct. You're philosophizing too much, write some code.
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 ugh if i have time later i will draw the graph i'm envisioning
nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 nostr:npub106dam65ww9ztdqj26xvh08dyuc7lj7nmkrtrujwsmyq2n6g3r33saq3m89 I have an even more retard-simple one but it's not for AP specifically
