You are reading content from Scuttlebutt
@cel %m0R78xpq2si3GRiRdjtCnyOc3frsxeCA/ILoonrAy6A=.sha256

ebt.js - #patchfoo script for viewing #ssb-ebt storage (~/.ssb/ebt/).

This shows you which peers your ssb-server has replicated with using ebt, when they last replicated, and how much data (their feed / wants vector clock) is stored for that peer. It is basically like doing ls -lt ~/.ssb/ebt | head and turning the ids into clickable links.

The ones with a small value like 2 bytes I think means that my sbot never stayed connected long enough to that peer to get their want list - although some of those pubs I've certainly connected to many times, so maybe the want list got reset at some point - I'm not sure.

patchfoo-ebt-script.png

In the full list, I can scroll back and how the size of the want list has grown over time. For example, 2019-02-01 630 KB, 2019-10-26 493 KB, 2018-05-06 374 KB, 2018-02-23 272 KB. Also, some have a smaller size than the surrounding ones, probably because that id followed fewer feeds. Also I can see when many peers probably went offline. This data is my local node but is about not only connections to pubs but connections from regular peers too, since I have my local sbot exposed to the internet like a pub [%EhrIbw2...]. On my pub there is more data though: 728M, 1481 ids; vs. 167M, 404 ids locally.

Now I want to graph/chart this data…

@cel %PXepyXraiFii4vCZAXogDANWXMRFwoXwTEbyJSQcBFc=.sha256

Converted to a ssb-exec script:

ebt.js

Join Scuttlebutt now