{"id":2416,"date":"2026-02-03T22:48:16","date_gmt":"2026-02-03T22:48:16","guid":{"rendered":"https:\/\/www.danielpradilla.info\/blog\/?p=2416"},"modified":"2026-03-27T09:44:55","modified_gmt":"2026-03-27T09:44:55","slug":"echotree","status":"publish","type":"post","link":"https:\/\/www.danielpradilla.info\/blog\/echotree\/","title":{"rendered":"EchoTree"},"content":{"rendered":"

For years now I kept some of my social accounts alive with a Python script. It read from a collection of RSS feeds and shared at random times. It worked, my feeds stayed active, and people asked me what was I doing reading at 3am.<\/p>\n

The script had a bit of personality: it logged out all the time, and tended to share links as simple URLs, no preview. There was no context, no personal take, no small comment that explains why I was sharing this. Although I liked the serendipity of it, whenever I found a really cool article, I preferred to take the long route and curate the post by hand.<\/p>\n

I tried Buffer and a few similar tools, but they felt extravagant for something I only do now and then. I don’t share articles for a living, I share them because I believe in elective affinities, that quiet collective pull toward certain ideas. A piece of writing isn’t fully alive until it’s passed from hand to hand. Unshared, it feels like the proverbial tree falling in a forest with no one around to hear it.<\/p>\n

So I built EchoTree.<\/p>\n

What I like most about it is that it feels proportionate: no subscription tax, no heavy setup, no pressure to become a “content machine.” It’s just a private tool I control, built for thoughtful sharing.<\/p>\n

The goal<\/h2>\n

I wanted a light, intentional workflow:<\/p>\n