<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Advert4</title>
    <description>The latest articles on DEV Community by Advert4 (@advert4me).</description>
    <link>https://dev.to/advert4me</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4253618%2Fb69fb6c7-ce80-4304-bf26-d1d6d9b3f01f.png</url>
      <title>DEV Community: Advert4</title>
      <link>https://dev.to/advert4me</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/advert4me"/>
    <language>en</language>
    <item>
      <title>Building Advert4: safer retries for social publishing</title>
      <dc:creator>Advert4</dc:creator>
      <pubDate>Thu, 19 Nov 2026 10:52:53 +0000</pubDate>
      <link>https://dev.to/advert4me/building-advert4-safer-retries-for-social-publishing-3aog</link>
      <guid>https://dev.to/advert4me/building-advert4-safer-retries-for-social-publishing-3aog</guid>
      <description>&lt;p&gt;Social publishing has a tricky failure mode: a request times out after the network has already created the post. Retrying the same request can produce a duplicate.&lt;/p&gt;

&lt;p&gt;In Advert4, our Laravel publishing service separates a scheduled post from each network's publishing target. Each target records its own state and remote post ID. Before sending a create request, the service records that publishing has started. A network error after that point is treated as an uncertain result rather than a safe instruction to publish again.&lt;/p&gt;

&lt;p&gt;For Mastodon, we also attach a stable idempotency key. Media uploads are tracked separately so processing checks do not upload the same file again.&lt;/p&gt;

&lt;p&gt;The practical lesson: distinguish a definite rejection from an unknown outcome. Automatic retries are useful for some read operations and rate limits; a timed-out create request needs more care.&lt;/p&gt;

&lt;p&gt;We are building &lt;a href="https://advert4.me" rel="noopener noreferrer"&gt;Advert4&lt;/a&gt; at Electroinvest in Podgorica, Montenegro, and will share implementation notes as integrations are verified.&lt;/p&gt;

&lt;p&gt;Disclosure: this article was prepared with AI assistance.&lt;/p&gt;

</description>
      <category>architecture</category>
      <category>backend</category>
      <category>laravel</category>
    </item>
  </channel>
</rss>
