ptr.pet
at protocol indexer with flexible filtering, xrpc queries, and a cursor-backed event stream, built on fjall
at-protocol
atproto
indexer
rust
fjall
[docs] update readme
+6
-4
README.md
+6
-4
README.md
···
6
7
## vs `tap`
8
9
-
while [`tap`](https://github.com/bluesky-social/indigo/tree/main/cmd/tap) is designed primarily as a firehose consumer and relay, `hydrant` is flexible, it allows you to directly query the database for records, and it also provides an ordered view of events, allowing the use of a cursor to fetch events from a specific point in time.
10
11
### stream behavior
12
···
111
112
`hydrant` implements the following XRPC endpoints under `/xrpc/`:
113
114
-
#### `com.atproto.*`
115
116
the following are implemented currently:
117
- `com.atproto.repo.getRecord`
118
- `com.atproto.repo.listRecords`
119
120
-
#### `systems.gaze.hydrant.*`
121
122
-
##### `systems.gaze.hydrant.countRecords`
123
124
return the total number of stored records in a collection.
125
···
6
7
## vs `tap`
8
9
+
while [`tap`](https://github.com/bluesky-social/indigo/tree/main/cmd/tap) is designed as a firehose consumer and simply just propagates events while handling sync, `hydrant` is flexible, it allows you to directly query the database for records, and it also provides an ordered view of events, allowing the use of a cursor to fetch events from a specific point in time.
10
11
### stream behavior
12
···
111
112
`hydrant` implements the following XRPC endpoints under `/xrpc/`:
113
114
+
#### com.atproto.*
115
116
the following are implemented currently:
117
- `com.atproto.repo.getRecord`
118
- `com.atproto.repo.listRecords`
119
120
+
#### systems.gaze.hydrant.*
121
122
+
these are some non-standard XRPCs that might be useful.
123
+
124
+
##### systems.gaze.hydrant.countRecords
125
126
return the total number of stored records in a collection.
127