A CLI for tangled operations.
11
fork

Configure Feed

Select the types of activity you want to include in your feed.

Document AppView sync limitations

onevcat f86a9e04 20af73a4

+12 -1
+12 -1
README.md
··· 365 365 ## Known Limitations 366 366 367 367 - Tangled AppView and Constellation indexing may lag behind successful PDS 368 - writes. 368 + writes. For newly created records, keep the returned AT URI or rkey and use it 369 + directly while indexes catch up. 370 + - AppView is not yet a complete projection of Tangled's ATProto records. In 371 + particular, protocol-level issue state records 372 + (`sh.tangled.repo.issue.state`) and pull request status records 373 + (`sh.tangled.repo.pull.status`) can be visible to `tang` while the web UI 374 + still shows stale state. Pull request records themselves may also fail to 375 + appear in AppView even when they exist on the author's PDS and are indexed by 376 + Constellation. Track upstream progress in 377 + [tangled.org/core#462](https://tangled.org/tangled.org/core/issues/462), 378 + [tangled.org/core#282](https://tangled.org/tangled.org/core/issues/282), and 379 + [the pull status ingestion record](https://pdsls.dev/at://did:plc:kl2ejrmz5zmxnno3ll4luz76/sh.tangled.repo.issue/3mkuyuh6t3l2k). 369 380 - Some older pull request records do not contain patch rounds, so `pr diff` and 370 381 `pr checkout` cannot operate on them. 371 382 - SSH clone depends on Tangled's SSH key authorization index. If a freshly added