{
  "$type": "com.whtwnd.blog.entry",
  "theme": "github-light",
  "title": "How to use ATProto Dashboard",
  "content": "I cerated ATProto Dashboard. It can see 3rd party Collection onATProto. <br />\nURL: https://atpdashboard.usounds.work/\n\n<h1>Features</h1>\nIn ATProto, you can create custom collections (lexicons) like this \"WhiteWind.\" However, there has been no way to find out what collections exist. While there are some sites that monitor lexicons managed by Bluesky, there seem to be fewer tools for discovering custom collections. That’s why I decided to build this dashboard.\n\nCollection tracking began on January 17, 2025, so events prior to that date have not been collected.\n\n<h2>Dashboard</h2> \nView statistics of 3rd party Collections.\n\n<h2>Browser</h2>\nBrowse 3rd party Collections in a tree structure. \n\n<h1>How to Use for Dashboard</h1>\n\n<h2>Settings (Added on January 21th, 2025)</h2>\n<h3>Exclude collections with transaction key</h3>\nCollections that embed Transaction IDs (TIDs) are excluded from the aggregation target. I intentionally exclude known collections, and any occurrences outside the known ones will need to be addressed as they arise.\n\n<h2>Headline<h2>\nThe numbers at the top represent the following:\n\n<h3>Total Collections</h3>\nThe total number of unique collections collected so far. If there are collections created within the last 72 hours, display their count separately.\n\n<h3>Total Sub Name Spaces</h3>\nFor example, in my service, there are two collections: uk.skublur.post and uk.skublur.preference.\nIf the namespace up to uk.skublur is the same, it is considered part of the same service. However, generic services like io.github or app.netlify may be misidentified, resulting in a slightly lower count than the actual number of services.\n\n<h3>Total Users</h3>\nThis counts the DIDs of users who created records in custom collections.\nNote: This does not represent the creators of the services, as there is currently no way to identify them.\n\n<h3>Cursor Delay in Minutes</h3>\nThis metric is unrelated to collections.\nSince the backend uses Jetstream, this indicates how many minutes the Jetstream reception is delayed.\nIf there’s a delay of around a day, please contact the author.\n\n<h4>Hidden Feature</h4>\nTap the numbers in the headline to refresh the dashboard.\n\n<h2>Graph</h2>\nData is aggregated and displayed in 24-hour units. Since the 24-hour period is calculated in real time, the shape may change slightly each time you access it.  \n<h3>Daily Collections</h3>\nDisplays collections that had activity and newly created collections.  \n<h3>Daily Users</h3>\nDisplays users who triggered events, including active users and new users.  \n\n\n<h2>Collection</h2>\nDisplays a list of collections.\n\n<h3>COLLECTION</h3>\nThe name of the received collection. Collections created within the last 72 hours will have a green badge.\n\n<h3>EVENTS</h3>\nThe number of Create events that occurred for that collection.\n\n<h3>FIRST INDEXED</h3>\nThe earliest record created in that collection (after January 17, 2025).\n\n<h3>LAST INDEXED</h3>\nThe most recent record created in that collection.\n\n<h4>Sorting</h4>\nClick the column headers (e.g., COLLECTION, EVENTS) to sort by that column.\nFor example, sorting by FIRST INDEXED in descending order can help you find new services more easily.\nHowever, please note that this system only tracks events starting from January 17, so earlier records may be misidentified as the first.\n\n<h1>How to Use for Browser</h1>\nAt the top, you can set search conditions. The search results will not update until you tap **Search** (except for a few specific checkboxes). \n<h2>Search Collections</h2>\nSearch by Collection name.\n\n<h2>First Indexed</h2>\nSearch by the date the Collection was first detected, using a From–To range. You can specify only one side if desired. Due to simplified timezone handling, there may be a margin of error of about one day.\n\n <h2>Last Indexed</h2>\n Search by the date the Collection was last detected, using a From–To range. You can specify only one side if desired. Due to simplified timezone handling, there may be a margin of error of about one day. \n\n<h2>Has Lexicon</h2>\nNarrow down to Collections that *might* be resolvable via Lexicon. At this stage, DNS record checks are not performed, and if the data has been removed from the PDS, false positives may occur. \n\n<h2>Exclude specific collection</h2>\nRoughly exclude Collections that are presumed to have been created for temporary testing purposes.\n",
  "createdAt": "2025-08-02T14:11:52.890Z",
  "visibility": "public"
}