dan @danabra.mov@bsky.brid.gy
Public

maybe you're saying that out of these three, only Dynamically Configured works reasonably for local dev? this is not obvious "Collection Signal" seems most automatic so that's why i went with it. i assumed it would be essentially free since no users except me have the signal collection

Network Boundary Modes Tap syncs a subset of repos in the network. It can operate in three modes for determining this network boundary. Dynamically Configured (default): Tap starts out tracking no repos. Specific repos can then by added via /repos/add and removed via /repos/remove. Collection Signal: Set TAP_SIGNAL_COLLECTION=com.example.nsid. Track all repos that have at least one record in the specified collection. Many applications create a "declaration" or "profile" in a repo when that repo uses that application Full Network: Set TAP_FULL_NETWORK=true. Enumerates and tracks all findable repos on the entire network. Resource-intensive and takes days/weeks to complete backfill.
0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://bsky.brid.gy/convert/ap/at://did:plc:fpruhuo22xkm5o7ttr2ktxdo/app.bsky.feed.post/3mgizeiyfq22s on your instance and quote it. (Note that quoting is not supported in Mastodon.)