Post

Couldn't resist looking back at firehose optimization after getting STAR-lite mostly working. Looks like 3x firehose bandwidth reduction is achievable with implicit MST + previous-commit cache of CIDs per repo.

fig (aka:[phil])@bad-example.com

i think there's a mostly-unexplored design space here between massive client fan-out and point-to-point links. eg. i want to run my own relay, but not from home, and ideally not with the full weight of multiple full subscribeRepos coming into my home.

Mike P

@fentiger.wtf

2 May

Any CID that exists in the MST could be expressed as a path through the tree, i.e. a sequence of small integers describing which child node to choose at each step, to take you from the root to that CID. I bet this issmaller than encoding the full CID, and means you don't need a separate cache.

fig (aka:[phil])

@bad-example.com

would be! but gotta assume the client isn’t keeping the full MST around (inductive proofs are where it’s at) …and to recover the original firehose you’d need to keep a full network mirror

2/5/26, 4:53 pm0 reposts1 like

No replies yet.