pub.leaflet.comment

{
  "$type": "pub.leaflet.comment",
  "reply": {
    "parent": "at://did:plc:6ayddqghxhciedbaofoxkcbs/pub.leaflet.comment/3m666a4cp6c2e"
  },
  "facets": [],
  "subject": "at://did:plc:btxrwcaeyodrap5mnjw2fvmz/pub.leaflet.document/3m664kxn3xk2h",
  "createdAt": "2025-11-21T22:51:43.939Z",
  "plaintext": "wait it does!?!??!"
}

did:plc:lwckcyzhyrufq4ytg2abji7d | at://did:plc:lwckcyzhyrufq4ytg2abji7d/pub.leaflet.comment/3m66eo7cohs2r

{
  "$type": "pub.leaflet.comment",
  "facets": [
    {
      "index": {
        "byteEnd": 207,
        "byteStart": 190
      },
      "features": [
        {
          "$type": "pub.leaflet.richtext.facet#bold"
        },
        {
          "uri": "https://dholms.leaflet.pub/3mhj6bcqats2o?interactionDrawer=comments#record-addressing",
          "$type": "pub.leaflet.richtext.facet#link"
        }
      ]
    },
    {
      "index": {
        "byteEnd": 370,
        "byteStart": 366
      },
      "features": [
        {
          "$type": "pub.leaflet.richtext.facet#bold"
        }
      ]
    },
    {
      "index": {
        "byteEnd": 459,
        "byteStart": 455
      },
      "features": [
        {
          "$type": "pub.leaflet.richtext.facet#bold"
        }
      ]
    },
    {
      "index": {
        "byteEnd": 468,
        "byteStart": 464
      },
      "features": [
        {
          "$type": "pub.leaflet.richtext.facet#bold"
        }
      ]
    }
  ],
  "subject": "at://did:plc:yk4dd2qkboz2yv6tpubpc6co/site.standard.document/3mhj6bcqats2o",
  "createdAt": "2026-03-20T20:15:06.084Z",
  "plaintext": "Overall I like the direction that this is heading, this seems quite pragmatic!  I had a few thoughts on clarity of the record addressing, and some light thoughts on the scheme differences.\n\nRecord addressing\n\nI was a little confused reading this, until I read it a second time. I was under the impression that the space itself would have a record that would have an skey. I didn't understand that any record inside a permissioned space would have both an skey and rkey. I think adding an example lexicon of a record in a space as a code block might help communicate that better.\n\nFor the scheme \"ats://\" - two things pop to mind. First, might people expect ats:// to mean \"atproto secure\" vs \"atproto space\"?\n\nSecond, might this create a feeling of (i'm being facetious) \"they said *one* protocol, now they have *two*\"? Looking through the lens of protocol registration for browsers and operating systems?\n\nUnderstandably, you haven't published the differences in resolving the data yet compared to public data; but I wonder if this is something to take into consideration, and maintain a single \"at://\" scheme."
}

did:plc:ml6hwrktvr7r5nhxs7f7eoz4 | at://did:plc:ml6hwrktvr7r5nhxs7f7eoz4/pub.leaflet.comment/3mhjdfoo6oc2b