chown.de / tangled-repo-firehose
this repo has no description
1
fork

Configure Feed

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

Go 90.5%
HTML 9.0%
Makefile 0.5%
6 2 0

Clone this repository

https://tangled.org/chown.de/tangled-repo-firehose https://tangled.org/did:plc:x3ni2r3jgdqms5euhzt2qqdr/tangled-repo-firehose
git@tangled.org:chown.de/tangled-repo-firehose git@tangled.org:did:plc:x3ni2r3jgdqms5euhzt2qqdr/tangled-repo-firehose

For self-hosted knots, clone URLs may differ based on your setup.

Download tar.gz
README.md

tangled-repo-firehose#

A little experiment with jetstream to visualize repositories and stargazers on tangled.org.

What is it?#

I was trying to find popular repositories on tangled.org, but so far, no such method or lexicon exists. Which led me down to, how do you figure out what people are doing right now.

And here we go.

If you want to see a demo, check here: https://bsky.app/profile/chown.de/post/3mkvet2xfis2q.

How does it work?#

Caveat There's (currently) no atproto operation to enumerate all users or repositories, so coverage grows from what the firehose shows live plus various walks across DIDs. Star counts will not match tangled.org.

The app subscribes to Bluesky's jetstream and extracts sh.tangled.*. From there, background workers will resolve DIDs to handles, fetch language stats from knots, discover unseen repos referenced by stars, and backfill historical stars per known DID.

Persistence is SQLite via entgo.io.

Run it#

make run-dev # localhost:8080

Inspect:

  • /: the repositories (alternative: /repos.json)
  • /knots: known knots (and some status)
  • /handles: resolved handles