# pics.2bit.feed.photogate

> Published by [2bit.pics](https://lexicon.garden/identity/did:plc:sbmntiflmknij2axeck3w6u7)

✓ This is the authoritative definition for this NSID.

## Links

- [View on Lexicon Garden](https://lexicon.garden/lexicon/did:plc:sbmntiflmknij2axeck3w6u7/pics.2bit.feed.photogate)
- [Documentation](https://lexicon.garden/lexicon/did:plc:sbmntiflmknij2axeck3w6u7/pics.2bit.feed.photogate/docs)
- [Examples](https://lexicon.garden/lexicon/did:plc:sbmntiflmknij2axeck3w6u7/pics.2bit.feed.photogate/examples)

## Definitions

### `pics.2bit.feed.photogate`

**Type**: `record`

A photo author's statement about the comments on one of their photos, modeled on app.bsky.feed.threadgate. Comments live in their authors' repos, so a photo's author cannot delete one; instead they list it here, in their own repo, and the AppView folds it out of the thread - still one tap away for anyone who asks, the way Instagram and Bluesky treat hidden comments. The record key must be the photo's own rkey, and a gate is only honored in the repo that holds the photo - one written anywhere else is ignored.

**Key**: `tid`

| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `createdAt` | `string` (datetime) | Yes |  |
| `hiddenComments` | `array` | No | AT URIs of pics.2bit.feed.comment records on the photo that its author has hidden. Hidden comments are left out of the thread, the photo's comment count and notifications, and listed separately on request (see pics.2bit.feed.getComments' `hidden`). |
| `photo` | `string` (at-uri) | Yes | AT URI of the pics.2bit.feed.photo this gate applies to. Must match the gate's own repo and record key. |

## Raw Schema

```json
{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "A photo author's statement about the comments on one of their photos, modeled on app.bsky.feed.threadgate. Comments live in their authors' repos, so a photo's author cannot delete one; instead they list it here, in their own repo, and the AppView folds it out of the thread - still one tap away for anyone who asks, the way Instagram and Bluesky treat hidden comments. The record key must be the photo's own rkey, and a gate is only honored in the repo that holds the photo - one written anywhere else is ignored.",
      "key": "tid",
      "record": {
        "properties": {
          "createdAt": {
            "format": "datetime",
            "type": "string"
          },
          "hiddenComments": {
            "description": "AT URIs of pics.2bit.feed.comment records on the photo that its author has hidden. Hidden comments are left out of the thread, the photo's comment count and notifications, and listed separately on request (see pics.2bit.feed.getComments' `hidden`).",
            "items": {
              "format": "at-uri",
              "type": "string"
            },
            "maxLength": 200,
            "type": "array"
          },
          "photo": {
            "description": "AT URI of the pics.2bit.feed.photo this gate applies to. Must match the gate's own repo and record key.",
            "format": "at-uri",
            "type": "string"
          }
        },
        "required": [
          "photo",
          "createdAt"
        ],
        "type": "object"
      },
      "type": "record"
    }
  },
  "id": "pics.2bit.feed.photogate",
  "lexicon": 1
}
```
