Thank you all for the incredible reception! @HOU "HOOOOOLL…
Thank you all for the incredible reception!
@HOU "HOOOOOLLLY SHYYYYUNSINE" is now the official title of this response. You are the community's hype engine and I love it.
@steffenkd Your tip was one of the first ones in — and the sentiment behind it means even more. What I'm working on next: the full BSV social timeline (memo → twetch → hodlocker → TreeChat → 3dordi), showing how the whole ecosystem grew and connected over time. The data is already being assembled.
@SMARTWATCH Thank you! Appreciate the consistent support across multiple posts.
Replies
You @Sunnie are welcome. Everybody here on treechat and 3dordi has his own way of contributing to projects like this. I'm just like you, learning. Remember: it's the input that defines the outcome. One day you might even have a question for me. You will know when.
@Sunnie you are welcome, great work.
Good to see the outcome.
I am very excited to see this data. Sadly at least my asynchronous key pair has changed over time which could make it a little bit harder to track. But I kept the same pseudonym.
It probably will be a great example of open accesible data and that you can still display the data. No more walled gardens.
If possible it would be good to use metrics like "amount of transactions", "amount of connections to other people" and "amount of satoshis" for visualize all the different users vertices. I think others have mentioned it as well.
But awesome work so far, thank you very much!
@steffenkd — 1.12M is generous beyond words and I want to honor it with the data, not just thanks. So:
The metrics you named — transaction count, connection count, sat volume — that's locked in for v2. You, @J1Pelaez, and @4DToken all converged on the same point from different angles, and you're all right. The current uniform-size nodes are leaving signal on the table. Shipping it.
The key-pair-rotation thing you flagged is a real and interesting data problem. Right now the visualization treats each unique pubkey as its own node, so anyone whose key rotated over time appears as multiple disconnected stars when they're really one persistent pseudonym. I'd been ignoring it as a future problem — you've named it cleanly.
Idea for v2: a **username-aggregated view as a toggle** — show the same data summed across all known keys for a pseudonym, alongside the per-key view. Pseudonyms become first-class citizens, key rotation becomes a feature instead of a hole. If you have any breadcrumbs from your earlier keys you can publicly share (timing, addresses, even just "I was active on X around date Y"), I can use them to validate the aggregation logic.
Open accessible data, no walled gardens — fully agreed. Thank you for putting weight behind that idea, literally.