Walk the repo, count the records.
Permissioned Data Diary 7: Off the Record - Daniel's Leaflets
In which we put records in a repo, sign them, and sync them (but not quite the way you think).
repomirror/repomirror.md at main · repomirrorhq/repomirror
Contribute to repomirrorhq/repomirror development by creating an account on GitHub.
AT Proto Collection Tracker
Discover AT Protocol activity from the bottom up — live record counts by collection type from the Jetstream firehose, grouped by namespace.
AT Proto Collection Tracker
Discover AT Protocol activity from the bottom up — live record counts by collection type from the Jetstream firehose, grouped by namespace.
Bitesize Proto: Upserting ATProto Records - Hitchhiker's Guide to the Atmosphere
Tired of creating duplicate records in a repo from your atproto app?
Tally Counter & Tracker Daily - Apps on Google Play
Count anything by tap with widget: goal,coins,days,clicks,numbers,progress,reps
proposal: ingest repo records #282
`sh.tangled.repo` records are one of the last few records that need atprotation (2-way sync between appview/pds). this one is tricky because we want consistency between knot state, appview state and PDS state. the path forward is described below: - migration to did/rkey syntax universally: in several places, we utilize `did/repo-name` as a globally unique identifier for a repository, we should migrate this to `did/rkey`: * for the tangled appview: this means reworking our ACLs, routers and DB to use `did/rkey` or ATURI as a globally unique identifier for a repo * for knots: this means changing paths on disk to be `did/rkey`, allowing git ops to `host:did/rkey` , updating ACLs, and XRPC endpoints * for spindles: this means updating ACLs and XRPC endpoints - once this is done, we can define ingestion logic for all services in the network to pull sh.tangled.repo records * for the tangled appview, this should create/delete/update a repo pointer record * for knots: this should create-or-ignore/delete-or-ignore/update-or-ignore a repo on disk. migration of repos needs to be thought out here. * for spindles: as above - define edge-case behaviors: * when referring to repos by rkey, it is possible for clever users to create duplicate records with the same repo-name, appview routers must handle this ambiguity with a new interstitial page that offers a redirect, knots must return an error upon push/pull on ambiguous git URLs * the `knot` cli can introduce a command `backfill` or `sync` to bring knot state up to sync with the rest of the world (repos, collaborators, pubkeys, ACLs etc.).
Nonprofit Explorer - ProPublica
Since 2013, the IRS has released data culled from over 1.8 million nonprofit tax filings. Use this database to find organizations and see details like their executive compensation, revenue and expenses, as well as download tax filings going back as far as 2001.
The List - Civic Council of Georgia
A public record of individuals documented in connection with Georgia's democratic backsliding, compiled from public sources by the Civic Council of Georgia.
Meet the army of amateur archivists racing to save US history in national parks
Save Our Signs aims to document every sign in the more than 400 national parks and historic sites across the country before the Trump administration removes them
I am once again asking you if you write something that uses a user's whole repo to get the .car export and walk it instead of calling listRecords a billion times. It's faster and can be done in the browser even.
Bailey Townsend 🦀
I wrote a demo/example showing how you can walk a user's atproto repo via an export faster than doing individual calls inside a browser if you need to process a lot of their records using atcute. 22s vs 262s for my repo. Hosted on @wisp.place walktherepo.wisp.place
