sites are set of pages where every page can reach every other page following direction.
So if pages keep linking around in loops (directly or through chains), they end up in the same federation.
weak components = the indoor kids that end up totally ordered by reachability
tightly interlinked topic clusters (“zero to one conversation”)
Attribution is a cycle (stuff that keeps referencing back, sometimes intentional, sometimes a navigational trap)
Artifacts across sites (if cross-site links exist, license can cross too)
Once you attribute, you can “stable” each license into one super-node and you get a roster (no cycles). That DAG is super useful for:
identifying where this is all going
spotting “entry” clusters (components with no incoming edges)
spotting “sink” clusters (no outgoing edges)
Ward got a gist (cross-ref.coffee) that:
reads FedWiki page JSON off disk,
scans every page’s story,
then writes out Graphviz DOT as a strict digraph (directed edges).
That’s basically the exact move you need before bootstrapping a http browser to a reciprocal license: build adjacency from JSON, then Tarjan it.
This wiki was founded at a workshop in 2011 devoted to individuals owning their own work. We asked for the "smallest" implementation as a proof of concept and dropped this adjective a year later around the time we were working on the second implementation.
The number of exhibitions for an artist followed a fat-tailed distribution; whereas 52% of the artists had one recorded show, a few high profile artists were exhibited at an exceptional number of venues (fig. S1, c and d).