# org.anthers.follow

> Published by [anthers.org](https://lexicon.garden/identity/did:plc:75xx6l27mt7a3uxoga5ka4qt)

✓ This is the authoritative definition for this NSID.

## Links

- [View on Lexicon Garden](https://lexicon.garden/lexicon/did:plc:75xx6l27mt7a3uxoga5ka4qt/org.anthers.follow)
- [Documentation](https://lexicon.garden/lexicon/did:plc:75xx6l27mt7a3uxoga5ka4qt/org.anthers.follow/docs)
- [Examples](https://lexicon.garden/lexicon/did:plc:75xx6l27mt7a3uxoga5ka4qt/org.anthers.follow/examples)

## Definitions

### `org.anthers.follow`

**Type**: `record`

One account following another on Anthers, meaning: show me what this person releases. Anthers mints this rather than adopting `app.bsky.graph.follow`, which it could. Following a creator for their releases is a different act from an edge in a microblog's social graph — somebody may reasonably want one without the other, and a creator may not be on that network at all — so conflating them would mean following a game developer here silently added them to a timeline somewhere else. Mirroring a follow onto another network is something a person chooses, never a consequence of following here.

**Key**: `tid`

| Property | Type | Required | Description |
|----------|------|----------|-------------|
| `subject` | `string` (did) | Yes | The identifier of the account being followed. A bare identifier rather than the object the other records use for their subjects, because this one names a PERSON rather than a record: an identifier is already precise and permanently resolvable, and there is nothing to carry beside it the way a record address could carry a version. |

## Raw Schema

```json
{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "One account following another on Anthers, meaning: show me what this person releases. Anthers mints this rather than adopting `app.bsky.graph.follow`, which it could. Following a creator for their releases is a different act from an edge in a microblog's social graph — somebody may reasonably want one without the other, and a creator may not be on that network at all — so conflating them would mean following a game developer here silently added them to a timeline somewhere else. Mirroring a follow onto another network is something a person chooses, never a consequence of following here.",
      "key": "tid",
      "record": {
        "properties": {
          "subject": {
            "description": "The identifier of the account being followed. A bare identifier rather than the object the other records use for their subjects, because this one names a PERSON rather than a record: an identifier is already precise and permanently resolvable, and there is nothing to carry beside it the way a record address could carry a version.",
            "format": "did",
            "type": "string"
          }
        },
        "required": [
          "subject"
        ],
        "type": "object"
      },
      "type": "record"
    }
  },
  "id": "org.anthers.follow",
  "lexicon": 1
}
```
