{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreid3po7xc6id6kljwv5ayfoxc7gses5haged5vmaghzciyngvtvkuq",
    "uri": "at://did:plc:iw5jw32bqqdf4bkbhotvf23m/app.bsky.feed.post/3mm655rngsoz2"
  },
  "description": "Over the last year, my public GitHub activity became less of a portfolio and more of a living map.\n\n\nIt was not one single product, one clean roadmap, or one neatly packaged theme. It was an ecosystem of projects I participated in, followed closely, adapted, forked, curated, tested, documented, maintained, or used as reference points while moving through different parts of the open-source world.\n\n\nSome repositories were places where I contributed directly. Others were forks I kept as public refe",
  "path": "/a-year-of-public-code-projects-forks-experiments-and-open-threads/",
  "publishedAt": "2026-05-19T00:29:57.000Z",
  "site": "https://pablomurad.com",
  "textContent": "Over the last year, my public GitHub activity became less of a portfolio and more of a living map.\n\nIt was not one single product, one clean roadmap, or one neatly packaged theme. It was an ecosystem of projects I participated in, followed closely, adapted, forked, curated, tested, documented, maintained, or used as reference points while moving through different parts of the open-source world.\n\nSome repositories were places where I contributed directly. Others were forks I kept as public references. Some were experiments. Some were tools I studied because they solved problems I care about. Some were part of broader communities of programmers, hackers, maintainers, and builders.\n\nThat is the honest shape of the year: wide, practical, messy, curious, and public.\n\nAcross this map, there are 145 repositories connected to my public GitHub presence. I do not see them as trophies. I see them as traces: each repository marks a question I followed, a system I wanted to understand, a tool I wanted to preserve, or a corner of the technical ecosystem I became involved with.\n\n## The main thread: infrastructure for curiosity\n\nLooking back, the clearest pattern is not a single language, stack, or product category. The pattern is infrastructure for attention.\n\nAgain and again, I became involved with projects that collect information, organize it, automate it, archive it, monitor it, or turn it into something usable. RSS readers, Telegram bots, AI workflows, dashboards, self-hosted services, media catalogs, scraping tools, feed monitors, and personal knowledge systems all point in the same direction.\n\nThe underlying interest was simple: how can information become easier to capture, filter, deliver, revisit, and act on?\n\nThat thread appears in projects such as **alexandria** , a read-only public Markdown archive around GitHub; **rssskull** , a robust RSS-to-Telegram bot focused on reliable delivery; **ScoutBot** , a Telegram automation system for alerts and media capture; **worldmonitor** , a real-time global monitoring dashboard using Node.js and Docker; and **situation-monitor** , a panel for tracking news, markets, and geopolitical events.\n\nDifferent projects, same obsession: making the internet more legible.\n\n## AI, agents, and automation\n\nA large part of the year was spent around AI systems, agent workflows, and automation. Not in the vague “AI changes everything” sense, but in the practical sense: templates, workflows, bots, dashboards, experiments, and reusable patterns.\n\nThis included involvement with repositories such as **agent-skills** , **ai_agents_az** , **awesome-free-llm-apis** , **awesome-langflow** , **awesome-openclaw-agents** , **langflow-embedded-chat** , **langflow-templates** , **lawbot** , **lazier** , **MuLIAICHI-n8n-what-the-hell-is-everyone-building** , **n8n-workflows** , **n8nworkflows.xyz** , **sim** , and **world-br**.\n\nSome of these projects were about collecting resources. Others were about making workflows easier to reuse. Others were about observing what people are actually doing with tools like n8n, Langflow, OpenClaw, and agent-based automation stacks.\n\nThe most interesting part was never the hype layer. It was the plumbing: how prompts become workflows, how workflows become products, how bots become interfaces, and how automation quietly becomes personal infrastructure.\n\nI also spent time around visual generation and prompt libraries, including projects connected to **Awesome-Nano-Banana-images** and **awesome-nano-banana-pro-prompts**. Those repositories were not just about output. They were about watching how creative systems are shared, reused, tested, and documented by communities.\n\n## RSS, curation, and the old internet refusing to die\n\nRSS kept showing up again and again.\n\nThat probably says something about how I think. I like systems that are quiet, open, inspectable, and not dependent on algorithmic feeds. So I kept participating in and tracking tools around feeds, archives, link discovery, directories, and information routing.\n\nThis part of the year touched projects such as **ALL-about-RSS** , **awesome-rss-feeds** , **feedr** , **InReader** , **MultiNotify** , **rssexpert** , **thefeeder** , **archiver** , **awesome-etl** , **awesome-github-profile-readme** , **awesome-saas-directories** , **awesome-startup** , **awesome-vitepress-v1** , **free-for-dev** , **guiadevbrasil** , **scraping-apis-for-devs** , **the-book-of-secret-knowledge** , and **tabnews.com.br**.\n\nThis was not nostalgia. It was strategy.\n\nRSS, OPML, bookmarks, feeds, archives, and simple link directories are still some of the best ways to resist the chaos of modern platforms. They let you create your own reading layer over the web instead of accepting whatever an algorithm decides to serve.\n\n## Self-hosting, infrastructure, and homelab work\n\nAnother major track was self-hosting and homelab infrastructure.\n\nThis included involvement with projects like **awesome-homelab** , **awesome-selfhosted** , **homelabfork** , **ibramenu** , **dockergen** , **OpenList** , **Pentaract** , **Stirling-PDF** , **ttyd** , **theme.park** , **thinstation-ng** , **UNIT3D-Community-Edition** , **Ventoy** , **stws** , **azura-chat** , **arcadia** , and **skull-lib**.\n\nThe appeal here is obvious: control.\n\nSelf-hosting is not only about running services at home. It is about understanding the stack underneath the services people use every day. Deployment, storage, containers, thin clients, browser-accessible terminals, private cloud improvisation, trackers, dashboards, themes, and service orchestration all belong to that world.\n\nSome repositories were practical. Some were exploratory. Some were forks kept alive as public reference points. Together, they formed the infrastructure layer of the year.\n\n## Web apps, personal sites, and product experiments\n\nThe year also included a wide range of web projects, personal sites, and small product-like experiments.\n\nI was involved with or kept close to projects such as **banany-blog** , **cloneweb.online** , **Clone-Wars** , **deepseamantis** , **enigma** , **gabrielmurad** , **gumroad** , **muradgg** , **pressmurad** , **runawicodevico** , **site** , **vaporbosta** , **winget.pro** , **youare** , and **yourinfo**.\n\nThis area was less uniform, but that is exactly what made it useful.\n\nThere were blog platforms, portfolio experiments, browser fingerprinting demos, support systems, software repository servers, web utilities, product references, and deliberately strange prototypes. Some leaned personal. Others leaned technical. Others lived somewhere in between.\n\nThat border is important to me: the place where a website is not just a website, but a public artifact of identity, tooling, taste, and technical curiosity.\n\n## Security, hacking, and adversarial thinking\n\nSecurity and hacking formed another visible part of the map.\n\nRepositories such as **Awesome-Hacking** , **awesome-privacy** , **evilwaf** , **Hacking-guide** , **hacktricks** , **ILSpy** , **Private-Trackers-Spreadsheet** , **real-world-onion-sites** , **SecurityTesting** , **skull-guides** , **social-media-hacker-list** , **swot** , and **warning-cl** sat in this part of the year.\n\nThis was not about treating security as theater. It was about studying systems from the other side.\n\nGood technical work requires adversarial thinking. You need to understand how tools fail, how systems leak information, how defenses are bypassed, how privacy erodes, how reverse engineering works, and how communities document tactics that rarely fit inside official manuals.\n\nThis section of the work sharpened that lens.\n\n## Tools, utilities, and small scripts\n\nA lot of the year was also made of small utilities — the kind of projects that do not always look impressive from the outside, but often become the most useful in daily work.\n\nThat includes **alistofsoftwares** , **Bookmarklets** , **capcut-srt** , **CAS** , **checkme** , **dsize** , **dzip** , **grub-tweaks** , **htmlansi** , **introduction-to-bash-scripting** , **namegen** , **organizer-movies** , **safegen** , **Screeni-py** , **ShadesToolkit** , **skullgrade** , **theskullcon** , and **xxm**.\n\nThese projects feel like a workshop drawer: converters, generators, checkers, launchers, scripts, small web interfaces, Bash references, PowerShell tools, media organizers, and system utilities.\n\nNot every useful tool needs to become a product. Sometimes the value is in having a sharp little thing that does one job well enough to keep around.\n\n## Media, streaming, archives, and catalogs\n\nMedia was another recurring territory.\n\nProjects such as **artpacks** , **ascii-fire** , **ascii-studio** , **awesome-iptv** , **Bflix34567** , **Deep-Live-Cam** , **Flickv4** , **Iptv-Brasil-2025** , **oldpiratasclub** , **pablos-media** , **scrapiptv** , **semo** , and **vega-app** formed a strange but coherent cluster around streaming, catalogs, visual experiments, IPTV, archives, ASCII media, and entertainment interfaces.\n\nThere is a technical side to this: scraping, indexing, playback, cataloging, conversion, rendering, automation, and interface design.\n\nThere is also a cultural side. Media systems are never just about files. They are about access, memory, taste, discovery, preservation, and the informal networks people build around what they watch, collect, remix, and share.\n\n## Themes, identity, and personal publishing\n\nAnother part of the year revolved around themes, personal sites, and identity systems.\n\nThat includes **directory-plus** , **pablos-theme** , **skullx** , and **Treatises-and-Declarations**.\n\nThis is the more personal layer of the work. Themes and publishing systems are not only about presentation. They decide how writing feels, how navigation works, how a personal archive breathes, and how a public identity becomes readable.\n\nA good theme is not decoration. It is infrastructure for voice.\n\n## Games, prototypes, and experiments\n\nThe year also had room for experiments that did not need to justify themselves as products.\n\nProjects like **chess-pitico** , **city-roads** , **matrix-ss** , **observador** , **privatechess** , **roads** , **roko** , **seamless** , and **sudoku** belong here.\n\nSome were games. Some were visualizations. Some were intentionally cryptic. Some were simple prototypes. They mattered because they kept the exploratory muscle alive.\n\nNot every repository needs a market. Not every experiment needs a pitch. Sometimes the point is to follow a weird idea until it teaches you something.\n\n## Forks, mirrors, and ecosystem memory\n\nFinally, a meaningful part of the year involved forks, mirrors, adaptations, and preserved reference points.\n\nThat includes repositories such as **edit** , **gazela** , **GazellePW** , **gazelaPW** , **hxnull.nexus-old** , **medicat_installer** , and **msmg-toolkit**.\n\nForking is often misunderstood. A fork is not always a declaration of ownership. Sometimes it is a bookmark with history. Sometimes it is a way to study changes. Sometimes it is a backup. Sometimes it is a personal branch of an ecosystem that might disappear, mutate, or become harder to find later.\n\nIn that sense, these repositories are part of a larger habit: keeping technical memory accessible.\n\n## What this year really was\n\nIf I had to summarize the year honestly, I would not describe it as a year of building one thing.\n\nIt was a year of involvement.\n\nI participated in public code across AI, automation, RSS, self-hosting, security, media systems, web experiments, tools, themes, games, and infrastructure. I followed communities, kept forks, studied systems, adapted ideas, tested tools, curated references, and left public traces of the paths I was taking.\n\nThe result is not a polished monument. It is a map.\n\nAnd that map says something clearly: my work lives at the intersection of curiosity, infrastructure, information, media, automation, and open systems.\n\nThat is where I spent the last year.\n\nAnd it is probably where the next one begins.",
  "title": "A Year of Public Code: Projects, Forks, Experiments, and Open Threads",
  "updatedAt": "2026-05-19T00:29:57.306Z"
}