<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>AzamatSafarov</title>
        <link>https://paragraph.com/@AzamatSafarov</link>
        <description>undefined</description>
        <lastBuildDate>Mon, 09 Nov 2026 14:34:58 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>All rights reserved</copyright>
        <item>
            <title><![CDATA[Hermes Agent Desktop]]></title>
            <link>https://paragraph.com/@AzamatSafarov/hermes-agent-desktop</link>
            <guid>9CJO6pRnL1yMdoAxA5dn</guid>
            <pubDate>Fri, 05 Jun 2026 21:09:58 GMT</pubDate>
            <description><![CDATA[Hermes Agent Desktop is here. Not a browser wrapper — a native Electron app wrapping the same Python runtime. Same config.yaml, same skills, same model. Different interface. What changed: streaming chat with inline tool cards, six built-in themes, command palette, skill management window, one-click updates. Visual context for multi-step agent tasks — each step is a card, not a line of terminal output. Lower barrier to entry. New users no longer need to know venv, pip install, or systemd. Down...]]></description>
            <content:encoded><![CDATA[<p>Hermes Agent Desktop is here.</p><p>Not a browser wrapper — a native Electron app wrapping the same Python runtime. Same config.yaml, same skills, same model. Different interface.</p><p>What changed: streaming chat with inline tool cards, six built-in themes, command palette, skill management window, one-click updates. Visual context for multi-step agent tasks — each step is a card, not a line of terminal output.</p><p>Lower barrier to entry. New users no longer need to know venv, pip install, or systemd. Download, install, launch — done. The classic CLI path took 15–30 minutes. Desktop cuts it to five.</p><p>Honest take: v0.15.x, still growing. Some CLI features not yet in the GUI — full kanban board management and Ink TUI session orchestration are more capable right now. But all CLI improvements auto-reach Desktop on update. One codebase, two interfaces.</p><p>If you’re on WSL migrating to Desktop, check hermes config path after install. Desktop may read a different profile directory than your CLI setup.</p><p><a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://hermes-agent.nousresearch.com/desktop">https://hermes-agent.nousresearch.com/desktop</a></p><p><strong>Dev.to</strong> — <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://dev.to/azamat_safarov_119e17602f/">https://dev.to/azamat_safarov_119e17602f/</a></p><p><strong>Medium</strong> — <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://medium.com/@akutagavasora777">https://medium.com/@akutagavasora777</a></p>]]></content:encoded>
            <author>azamatsafarov@newsletter.paragraph.com (AzamatSafarov)</author>
        </item>
        <item>
            <title><![CDATA[Test]]></title>
            <link>https://paragraph.com/@AzamatSafarov/test</link>
            <guid>zbcLQzu7sZs7AJ8eKE3X</guid>
            <pubDate>Fri, 05 Jun 2026 21:08:41 GMT</pubDate>
            <description><![CDATA[test]]></description>
            <content:encoded><![CDATA[<p>test</p>]]></content:encoded>
            <author>azamatsafarov@newsletter.paragraph.com (AzamatSafarov)</author>
        </item>
        <item>
            <title><![CDATA[Built Autoposting: 8 Platforms, 90 Seconds]]></title>
            <link>https://paragraph.com/@AzamatSafarov/built-autoposting-8-platforms-90-seconds</link>
            <guid>gTUIybeBcMDBQyJu0hbI</guid>
            <pubDate>Mon, 25 May 2026 10:48:44 GMT</pubDate>
            <description><![CDATA[Pipeline Architecture Built Autoposting: 8 Platforms, 90 Seconds I write every day. Articles, project updates, tool reviews. And every single time I finished a piece, the same exhausting ritual began: open Telegram, paste the text, format it, post. Then VK. Then Medium. Then Dev.to, Bluesky, WordPress, Mastodon, Tumblr... By platform 8, I had no energy left. Platform 9? I simply forgot it existed. The Problem: Manual Distribution Doesn't Scale For years I tried Buffer, Zapier, even manual cop...]]></description>
            <content:encoded><![CDATA[<figure float="none" data-type="figure" class="img-center"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/d959f090b8be16c9c0f77f25bd3002ab25e5a61408aac0eb767aae553f24e437.png" alt="Pipeline Architecture" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">Pipeline Architecture</figcaption></figure><h1 id="h-built-autoposting-8-platforms-90-seconds" class="text-4xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Built Autoposting: 8 Platforms, 90 Seconds</h1><p>I write every day. Articles, project updates, tool reviews. And every single time I finished a piece, the same exhausting ritual began: open Telegram, paste the text, format it, post. Then VK. Then Medium. Then Dev.to, Bluesky, WordPress, Mastodon, Tumblr... By platform 8, I had no energy left. Platform 9? I simply forgot it existed.</p><h2 id="h-the-problem-manual-distribution-doesnt-scale" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The Problem: Manual Distribution Doesn&apos;t Scale</h2><p>For years I tried Buffer, Zapier, even manual copy-paste with formatting tweaks. None of them adapted the content for each platform. The same markdown that looks perfect on Dev.to breaks on Telegram, gets stripped on Bluesky, and renders as raw asterisks on VK. I was spending nearly an hour on mechanical work that added zero value to my readers.</p><h2 id="h-the-turning-point" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">The Turning Point</h2><p>I stopped looking for a tool and built a pipeline instead. The architecture is simple but precise:</p><ol><li><p>Write once in markdown</p></li><li><p>Generate 8 platform-native versions automatically</p></li><li><p>Publish articles first (WordPress and Dev.to — they produce canonical URLs)</p></li><li><p>Then teasers with links go everywhere else</p></li></ol><h2 id="h-what-makes-this-different-from-buffer" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">What Makes This Different From Buffer</h2><p>Buffer treats every platform as the same inbox. My pipeline treats each one as its own audience with its own language. Telegram gets HTML formatting with emojis. Bluesky gets ultra-dense 300-character hooks. Dev.to gets full technical markdown with code blocks.</p><h2 id="h-results" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Results</h2><ul><li><p>Distribution time: 50 minutes → 90 seconds</p></li><li><p>Platform coverage: 3-4 → 8 consistently</p></li><li><p>Content failures: 30% → 5%</p></li></ul><p>Full write-up with architecture and Python code: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://dev.to/azamat_safarov_119e17602f/">https://dev.to/azamat_safarov_119e17602f/</a></p><h2 id="h-follow-for-more" class="text-3xl font-header !mt-8 !mb-4 first:!mt-0 first:!mb-0">Follow for more</h2><ul><li><p>Dev.to: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://dev.to/azamat_safarov_119e17602f/">https://dev.to/azamat_safarov_119e17602f/</a></p></li><li><p>Bluesky: @a-zamat.bsky.social</p></li><li><p>Mastodon: @<a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="mailto:Azamat_Safarov@mastodon.social">Azamat_Safarov@mastodon.social</a></p></li><li><p>Telegram: @Azamat_Safar0v</p></li></ul>]]></content:encoded>
            <author>azamatsafarov@newsletter.paragraph.com (AzamatSafarov)</author>
        </item>
        <item>
            <title><![CDATA[Found a Calendar for Life: WallPlan]]></title>
            <link>https://paragraph.com/@AzamatSafarov/found-a-calendar-for-life-wallplan-3</link>
            <guid>0leW1TlotvtJ482pNII2</guid>
            <pubDate>Sat, 23 May 2026 17:35:20 GMT</pubDate>
            <description><![CDATA[WallPlan on my wall Lately I keep catching myself with so many projects and commitments that I can't keep track anymore. Some stretch years ahead — travel, deadlines, book launches, article shipments, all competing for the same calendar slots and mental bandwidth. If Google Calendar and per-project kanban boards in Obsidian used to be enough, now I need to see everything at once, in one place, at one glance. I searched the open web and found nothing that fit. My colleague Maxim Osovsky built ...]]></description>
            <content:encoded><![CDATA[<figure float="none" data-type="figure" class="img-center"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/da4da2b4c635e37c1aa7c80355e48e7cc705a3bd5076ff47f8daccc380e5a627.jpg" alt="WallPlan on my wall" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">WallPlan on my wall</figcaption></figure><p>Lately I keep catching myself with so many projects and commitments that I can&apos;t keep track anymore. Some stretch years ahead — travel, deadlines, book launches, article shipments, all competing for the same calendar slots and mental bandwidth. If Google Calendar and per-project kanban boards in Obsidian used to be enough, now I need to see everything at once, in one place, at one glance. I searched the open web and found nothing that fit.</p><p>My colleague <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://t.me/osowski">Maxim Osovsky</a> built exactly what I needed: <strong>WallPlan</strong> — a wall calendar on a continuous paper roll. You hang it on the wall and see your entire year, or two, or three, or twenty. When you see two years at a glance, you start making different decisions. You see where there&apos;s no rush and where you&apos;re already late. You see the gaps between trips where you can actually write. You see the cluster of deadlines coming six months from now that looks harmless in a monthly view but terrifying at scale.</p><figure float="none" data-type="figure" class="img-center"><img src="https://img.paragraph.com/cdn-cgi/image/format=auto/https://storage.googleapis.com/papyrus_images/dd04b514f633c7be8a3a574a367bcada95f054f5db839df0a23a1bc7fbef2911.jpg" alt="WallPlan detail" class="image-node embed"><figcaption HTMLAttributes="[object Object]" class="">WallPlan detail</figcaption></figure><p>I configured mine for 24 months. Nothing stays in my head anymore — I can literally look up and see when the book draft is due, when articles need to ship, when trips happen, when I have empty months to breathe. The calendar becomes external memory.</p><p><strong>What WallPlan does:</strong></p><p><strong>Scale</strong> — from 1 year to 20 years. I picked two years. The roll is as long as your wall allows.</p><p><strong>Aesthetics</strong> — If you like July burning orange and December turning blue, turn on color months. If you prefer austere black and white, turn it off.</p><p><strong>Your own events</strong> — click any date, add your deadline, trip, or launch. Not prefilled holidays from some generic list. Your actual life.</p><p><strong>Gantt lanes</strong> — up to 10 tracks below the calendar, each a separate timeline: a project, a person, a habit, whatever you want to watch stretch across months. This was exactly the missing piece I didn&apos;t know I needed until I saw it.</p><p><strong>Language &amp; holidays</strong> — switch between Russian, Chinese, English, Hebrew, Arabic. Holidays on or off per region. I don&apos;t need RU/CN, turned them off.</p><p><strong>Export</strong> — SVG or PDF, then print at any copy shop and actually hang it.</p><p>If planning is your pain too, try it:</p><ul><li><p>24-month calendar preview: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://wayfinding.pro/cal/?o=html&amp;l=24">https://wayfinding.pro/cal/?o=html&amp;l=24</a></p></li><li><p>Full customizer (colors, language, holidays, scale): <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://wallplan.osovsky.com/ru">https://wallplan.osovsky.com/ru</a></p></li><li><p>English: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://wallplan.osovsky.com/">https://wallplan.osovsky.com/</a></p></li><li><p>Chinese: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://wallplan.osovsky.com/zh">https://wallplan.osovsky.com/zh</a></p></li><li><p>Hebrew: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://wallplan.osovsky.com/he">https://wallplan.osovsky.com/he</a></p></li><li><p>Arabic: <a target="_blank" rel="noopener noreferrer nofollow ugc" class="dont-break-out" href="https://wallplan.osovsky.com/ar">https://wallplan.osovsky.com/ar</a></p></li></ul>]]></content:encoded>
            <author>azamatsafarov@newsletter.paragraph.com (AzamatSafarov)</author>
        </item>
    </channel>
</rss>