<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>ElixirStatus</title>
    <description>Elixir news and status updates from the community for Elixir and Phoenix</description>
    <link>https://elixirstatus.com/</link>
    
      <item>
        <title><![CDATA[Mold v0.3.0 released]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/fuelen?uid=2rnwD" width="64" height="64" />
              </td>
              <td>
                <h1>Mold v0.3.0 released</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    28 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> fuelen
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
Highlights:</p>
<ul>
  <li>
Lists now collect all element errors instead of stopping at the first one.  </li>
  <li>
Empty strings are treated as <code class="inline">nil</code> by integer, float, boolean, and atom types, making <code class="inline">nilable</code> and <code class="inline">default</code> behavior consistent across built-in types.  </li>
  <li>
Fixed error handling for malformed nested source paths and preserved full traces through nested unions.  </li>
  <li>
Expanded the documentation for defaults, validation, custom parsers, and error formatting.  </li>
</ul>
<p>
<a href="https://github.com/fuelen/mold/releases/tag/v0.3.0">https://github.com/fuelen/mold/releases/tag/v0.3.0</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/2rnwD-mold-v030-released">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>28 Aug 2026 21:03:22 +0000</pubDate>
        <link>https://elixirstatus.com/p/2rnwD-mold-v030-released</link>
        <guid>https://elixirstatus.com/p/2rnwD-mold-v030-released</guid>
      </item>
    
      <item>
        <title><![CDATA[Voyager: A modern Observer alternative for the BEAM]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/kamilkondrackiswm?uid=761c4" width="64" height="64" />
              </td>
              <td>
                <h1>Voyager: A modern Observer alternative for the BEAM</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    28 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> kamilkondrackiswm
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
Software Mansion introduces Voyager, a standalone, zero-dependency desktop app for BEAM node introspection that features a real-time node overview and an interactive supervision tree. The source code is now publicly available on GitHub under a fair-source model - making it completely free for individuals and teams of up to 10. Linux build is also live! </p>
<p>
Catch a live demo at the upcoming ElixirConf in Chicago.</p>
<p>
<a href="https://voyager.swmansion.com">https://voyager.swmansion.com</a> </p>

                <hr>
                <small><a href="https://elixirstatus.com/p/761c4-voyager-a-modern-observer-alternative-for-the-beam">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>28 Aug 2026 11:38:57 +0000</pubDate>
        <link>https://elixirstatus.com/p/761c4-voyager-a-modern-observer-alternative-for-the-beam</link>
        <guid>https://elixirstatus.com/p/761c4-voyager-a-modern-observer-alternative-for-the-beam</guid>
      </item>
    
      <item>
        <title><![CDATA[Latest webinar: How to Think About Game Servers (Pt 2)- from Erlang Solutions]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/CMC989?uid=quGgd" width="64" height="64" />
              </td>
              <td>
                <h1>Latest webinar: How to Think About Game Servers (Pt 2)- from Erlang Solutions</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    25 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> CMC989
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
Hernán Rivas Acosta is back with Part 2 of his game server series, looking at how latency and jitter affect multiplayer games.
Building on the first session, Hernán uses practical code examples to explain clock synchronisation, input delay and different ways to manage lag during gameplay.
Check it out here: <a href="https://www.erlang-solutions.com/webinars/how-to-think-about-game-servers-pt-2/">https://www.erlang-solutions.com/webinars/how-to-think-about-game-servers-pt-2/</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/quGgd-latest-webinar-how-to-think-about-game-servers-pt-2--from-erlang-solutions">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>25 Aug 2026 10:21:41 +0000</pubDate>
        <link>https://elixirstatus.com/p/quGgd-latest-webinar-how-to-think-about-game-servers-pt-2--from-erlang-solutions</link>
        <guid>https://elixirstatus.com/p/quGgd-latest-webinar-how-to-think-about-game-servers-pt-2--from-erlang-solutions</guid>
      </item>
    
      <item>
        <title><![CDATA[Composite v0.7.0 released]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/fuelen?uid=aE0ip" width="64" height="64" />
              </td>
              <td>
                <h1>Composite v0.7.0 released</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    22 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> fuelen
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
It adds <code class="inline">apply_tagged/1,3</code> for detecting unchanged queries and fixes dependency ordering and strict nested params.</p>
<p>
<a href="https://github.com/fuelen/composite/releases/tag/v0.7.0">https://github.com/fuelen/composite/releases/tag/v0.7.0</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/aE0ip-composite-v070-released">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>22 Aug 2026 18:09:43 +0000</pubDate>
        <link>https://elixirstatus.com/p/aE0ip-composite-v070-released</link>
        <guid>https://elixirstatus.com/p/aE0ip-composite-v070-released</guid>
      </item>
    
      <item>
        <title><![CDATA[Ecto ERD v0.8.0 released]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/fuelen?uid=XqlHJ" width="64" height="64" />
              </td>
              <td>
                <h1>Ecto ERD v0.8.0 released</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    22 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> fuelen
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
Adds D2 output format</p>
<p>
<a href="https://github.com/fuelen/ecto_erd/releases/tag/v0.8.0">https://github.com/fuelen/ecto_erd/releases/tag/v0.8.0</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/XqlHJ-ecto-erd-v080-released">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>22 Aug 2026 17:56:57 +0000</pubDate>
        <link>https://elixirstatus.com/p/XqlHJ-ecto-erd-v080-released</link>
        <guid>https://elixirstatus.com/p/XqlHJ-ecto-erd-v080-released</guid>
      </item>
    
      <item>
        <title><![CDATA[The Agent Needs Identity. The Model Does Not.]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/hfiguera?uid=cokez" width="64" height="64" />
              </td>
              <td>
                <h1>The Agent Needs Identity. The Model Does Not.</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    20 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> hfiguera
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
An engineering case study about keeping customer identity inside a Phoenix application while Jido, OpenAI, and trusted tools operate on stable Obscura pseudonyms. It covers tool calls, streaming responses, credential isolation, logs, telemetry, and a runnable deterministic example.</p>
<p>
<a href="https://hfiguera.github.io/obscura/blog/the-agent-needs-identity-the-model-does-not/">https://hfiguera.github.io/obscura/blog/the-agent-needs-identity-the-model-does-not/</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/cokez-the-agent-needs-identity-the-model-does-not">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>20 Aug 2026 21:47:32 +0000</pubDate>
        <link>https://elixirstatus.com/p/cokez-the-agent-needs-identity-the-model-does-not</link>
        <guid>https://elixirstatus.com/p/cokez-the-agent-needs-identity-the-model-does-not</guid>
      </item>
    
      <item>
        <title><![CDATA[What does Phoenix LiveView look like when the UI is connected to hundreds of physical robots?]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/karolinauske?uid=cCtoB" width="64" height="64" />
              </td>
              <td>
                <h1>What does Phoenix LiveView look like when the UI is connected to hundreds of physical robots?</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    18 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> karolinauske
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
A look at a real-world fleet management system, covering real-time telemetry, PubSub, MQTT, data synchronization, and some of the engineering trade-offs involved.</p>
<p>
<a href="https://curiosum.com/blog/phoenix-liveview-robotics-fleet-management">https://curiosum.com/blog/phoenix-liveview-robotics-fleet-management</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/cCtoB-what-does-phoenix-liveview-look-like-when-the-ui-is-connected-to-hundreds-of-physical-robots">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>18 Aug 2026 11:35:17 +0000</pubDate>
        <link>https://elixirstatus.com/p/cCtoB-what-does-phoenix-liveview-look-like-when-the-ui-is-connected-to-hundreds-of-physical-robots</link>
        <guid>https://elixirstatus.com/p/cCtoB-what-does-phoenix-liveview-look-like-when-the-ui-is-connected-to-hundreds-of-physical-robots</guid>
      </item>
    
      <item>
        <title><![CDATA[BEAM There, Done That #21: Elixir in the browser with Hologram]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/bartblast?uid=hTIZq" width="64" height="64" />
              </td>
              <td>
                <h1>BEAM There, Done That #21: Elixir in the browser with Hologram</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    17 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> bartblast
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
I was a guest on BEAM There, Done That with Francesco Cesarini and Allen Wyma, talking Hologram - running your Elixir in the browser instead of on the server. We covered why it targets JavaScript rather than WASM, how the compiler decides what code reaches the client, where LiveView is still the better choice, and the local-first layer I’m building next. <a href="https://www.youtube.com/watch?v=BOsSI7WlhdI">https://www.youtube.com/watch?v=BOsSI7WlhdI</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/hTIZq-beam-there-done-that-21-elixir-in-the-browser-with-hologram">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>17 Aug 2026 20:12:05 +0000</pubDate>
        <link>https://elixirstatus.com/p/hTIZq-beam-there-done-that-21-elixir-in-the-browser-with-hologram</link>
        <guid>https://elixirstatus.com/p/hTIZq-beam-there-done-that-21-elixir-in-the-browser-with-hologram</guid>
      </item>
    
      <item>
        <title><![CDATA[ElixirConf US 2026 in Chicago is coming...]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/paulinaprochorowska-em?uid=3rWXr" width="64" height="64" />
              </td>
              <td>
                <h1>ElixirConf US 2026 in Chicago is coming...</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    14 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> paulinaprochorowska-em
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
Hi All! The biggest event of the year for <strong>Elixir community</strong> - <a href="elixirconf.com"><strong>ElixirConf US 2026</strong></a> is coming up. It’s hybrid, so you can join from anywhere.</p>
<p>
A quick peek at the lineup (full schedule): <a href="https://elixirconf.com/#schedule">https://elixirconf.com/#schedule</a></p>
<p>
<strong>Keynotes</strong>:
José Valim (creator of Elixir), Chris McCord (creator of Phoenix), Zach Daniel (creator of Ash), Quinn Wilton
Talks worth clearing your schedule for. More speakers here: <a href="https://elixirconf.com/#speakers">https://elixirconf.com/#speakers</a></p>
<p>
Plus a full day of training, from functional-programming basics, to hands-on embedded Elixir with Nerves.</p>
<p>
<strong>Details</strong>
📅 Conference: Sept 10–11, 2026 · Training: Sept 4 &amp; 9 (training)
📍 Chicago, IL + Virtual
🎟️ Register here: <a href="https://elixirconf.com/#register">https://elixirconf.com/#register</a></p>
<p>
See you around!</p>

                <hr>
                <small><a href="https://elixirstatus.com/p/3rWXr-elixirconf-us-2026-in-chicago-is-coming">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>14 Aug 2026 21:36:20 +0000</pubDate>
        <link>https://elixirstatus.com/p/3rWXr-elixirconf-us-2026-in-chicago-is-coming</link>
        <guid>https://elixirstatus.com/p/3rWXr-elixirconf-us-2026-in-chicago-is-coming</guid>
      </item>
    
      <item>
        <title><![CDATA[Privacy-Safe Phoenix Socket and Channel Logging]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/hfiguera?uid=PdoQD" width="64" height="64" />
              </td>
              <td>
                <h1>Privacy-Safe Phoenix Socket and Channel Logging</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    14 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> hfiguera
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
An engineering case study about restoring Phoenix socket and channel visibility without logging raw connection parameters, topics, events, or payloads. It covers opt-in telemetry handling, parameter redaction, bounded labels, failure modes, and privacy-safe operational logging with Obscura.</p>
<p>
<a href="https://hfiguera.github.io/obscura/blog/privacy-safe-phoenix-realtime-logging/">https://hfiguera.github.io/obscura/blog/privacy-safe-phoenix-realtime-logging/</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/PdoQD-privacy-safe-phoenix-socket-and-channel-logging">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>14 Aug 2026 17:52:26 +0000</pubDate>
        <link>https://elixirstatus.com/p/PdoQD-privacy-safe-phoenix-socket-and-channel-logging</link>
        <guid>https://elixirstatus.com/p/PdoQD-privacy-safe-phoenix-socket-and-channel-logging</guid>
      </item>
    
      <item>
        <title><![CDATA[An Agent Skill for Updating Elixir Dependencies]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/zorn?uid=biGfC" width="64" height="64" />
              </td>
              <td>
                <h1>An Agent Skill for Updating Elixir Dependencies</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    14 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> zorn
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
✏️ New blog: I wrote up a blog post talking about the first skill I made, one that does a detailed Elixir dependency update.</p>
<p>
More than Dependabot, it reviews changelogs and looks for code call sites that might be impacted by the changes. It also presents a full list of diff links for the main and transitive dependencies.</p>
<p>
<a href="https://mikezornek.com/posts/2026/8/elixir-dependency-update-skill/?utm_source=elixirstatus">https://mikezornek.com/posts/2026/8/elixir-dependency-update-skill/?utm_source=elixirstatus</a>&amp;utm_campaign=elixir-dependency-update-skill</p>

                <hr>
                <small><a href="https://elixirstatus.com/p/biGfC-an-agent-skill-for-updating-elixir-dependencies">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>14 Aug 2026 14:11:23 +0000</pubDate>
        <link>https://elixirstatus.com/p/biGfC-an-agent-skill-for-updating-elixir-dependencies</link>
        <guid>https://elixirstatus.com/p/biGfC-an-agent-skill-for-updating-elixir-dependencies</guid>
      </item>
    
      <item>
        <title><![CDATA[WeaveScope: native Elixir tracing for production AI agents]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/nateless?uid=3sBRd" width="64" height="64" />
              </td>
              <td>
                <h1>WeaveScope: native Elixir tracing for production AI agents</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    14 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> nateless
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
We built <a href="https://weavescope.com">WeaveScope</a> for Elixir teams running AI agents on the BEAM.</p>
<p>
Its native Elixir library, BeamWeaver, captures complete trace trees for agent runs, model calls, tool calls, errors, inputs, and outputs - plus waterfall timing, latency, token usage, and model cost. When an agent is slow, expensive, or wrong, you can see exactly which step caused it, including concurrent work across BEAM tasks.</p>
<p>
Our goal is simple: give Elixir developers the best tracing experience for AI applications, without a Python sidecar or a generic observability stack bolted on afterward.</p>
<p>
It’s free to try. The Free plan includes 100,000 span events, 14-day retention, and one project. Add the native library, create an API key, and inspect your first trace at <a href="https://weavescope.com">weavescope.com</a>.</p>

                <hr>
                <small><a href="https://elixirstatus.com/p/3sBRd-weavescope-native-elixir-tracing-for-production-ai-agents">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>14 Aug 2026 14:02:17 +0000</pubDate>
        <link>https://elixirstatus.com/p/3sBRd-weavescope-native-elixir-tracing-for-production-ai-agents</link>
        <guid>https://elixirstatus.com/p/3sBRd-weavescope-native-elixir-tracing-for-production-ai-agents</guid>
      </item>
    
      <item>
        <title><![CDATA[Evolving a string with a genetic algorithm]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/sylvesterroos?uid=d557V" width="64" height="64" />
              </td>
              <td>
                <h1>Evolving a string with a genetic algorithm</h1>

                <font color="#aaa">
                  <font color="#aaa">
                    14 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> sylvesterroos
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
Breeding random bytes into the One Ring poem using Petri, an Elixir library for genetic algorithms.</p>
<p>
<a href="https://sylvesterroos.com/blog/evolving-a-string-using-a-genetic-algorithm/">https://sylvesterroos.com/blog/evolving-a-string-using-a-genetic-algorithm/</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/d557V-evolving-a-string-with-a-genetic-algorithm">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate>14 Aug 2026 11:41:46 +0000</pubDate>
        <link>https://elixirstatus.com/p/d557V-evolving-a-string-with-a-genetic-algorithm</link>
        <guid>https://elixirstatus.com/p/d557V-evolving-a-string-with-a-genetic-algorithm</guid>
      </item>
    
      <item>
        <title><![CDATA[Privacy-Safe Phoenix Request Logging Without Changing Controller Params]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/hfiguera?uid=0d4Ru" width="64" height="64" />
              </td>
              <td>
                <h1>Privacy-Safe Phoenix Request Logging Without Changing Controller Params</h1>

                <font color="#aaa">
                  <font color="#aaa">
                     7 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> hfiguera
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
A Phoenix request can have a correctly redacted assign while the default telemetry logger still reads the original conn.params. This article explains Obscura’s opt-in logging boundary, how controllers retain original data while logs receive only a sanitized representation, and how the integration handles routes, failures, and work budgets without falling back to raw request data.</p>
<p>
<a href="https://hfiguera.github.io/obscura/blog/privacy-safe-phoenix-request-logging/">https://hfiguera.github.io/obscura/blog/privacy-safe-phoenix-request-logging/</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/0d4Ru-privacy-safe-phoenix-request-logging-without-changing-controller-params">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate> 7 Aug 2026 13:45:13 +0000</pubDate>
        <link>https://elixirstatus.com/p/0d4Ru-privacy-safe-phoenix-request-logging-without-changing-controller-params</link>
        <guid>https://elixirstatus.com/p/0d4Ru-privacy-safe-phoenix-request-logging-without-changing-controller-params</guid>
      </item>
    
      <item>
        <title><![CDATA[Calculating P&amp;L When a Trade Spans Multiple Sessions]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/ryanrborn?uid=Coib3" width="64" height="64" />
              </td>
              <td>
                <h1>Calculating P&amp;L When a Trade Spans Multiple Sessions</h1>

                <font color="#aaa">
                  <font color="#aaa">
                     6 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> ryanrborn
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
What happens when an external event arrives after the process context that created it is gone — the record gets filed twice, and a FIFO matcher scoped to that context produces a confidently wrong number instead of an error.</p>
<p>
<a href="https://seriousalchemy.com/pnl-sessions">https://seriousalchemy.com/pnl-sessions</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/Coib3-calculating-pl-when-a-trade-spans-multiple-sessions">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate> 6 Aug 2026 15:23:28 +0000</pubDate>
        <link>https://elixirstatus.com/p/Coib3-calculating-pl-when-a-trade-spans-multiple-sessions</link>
        <guid>https://elixirstatus.com/p/Coib3-calculating-pl-when-a-trade-spans-multiple-sessions</guid>
      </item>
    
      <item>
        <title><![CDATA[Taking Ash Framework’s DSL on a Spin for RPC Fun]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/imeraj?uid=KJ3fP" width="64" height="64" />
              </td>
              <td>
                <h1>Taking Ash Framework’s DSL on a Spin for RPC Fun</h1>

                <font color="#aaa">
                  <font color="#aaa">
                     6 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> imeraj
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
I have been lately looking into more and more Ash framework’s code and exploring the DSL package — Spark that Ash uses to write pretty much all it’s DSLs. While writing DSL in Spark eliminates many macro magic from Elixir metaprogramming, code generation using Manifest takes it to a whole new level. I wanted to write up the process I followed from writing extension, to generating code using Manifest, and sending RPC calls to a remote BEAM node to execute remote code.</p>
<p>
<a href="https://meraj-gearhead.ca/taking-ash-frameworks-dsl-on-a-spin-for-rpc-fun-3db7393405dc">https://meraj-gearhead.ca/taking-ash-frameworks-dsl-on-a-spin-for-rpc-fun-3db7393405dc</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/KJ3fP-taking-ash-frameworks-dsl-on-a-spin-for-rpc-fun">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate> 6 Aug 2026 01:42:12 +0000</pubDate>
        <link>https://elixirstatus.com/p/KJ3fP-taking-ash-frameworks-dsl-on-a-spin-for-rpc-fun</link>
        <guid>https://elixirstatus.com/p/KJ3fP-taking-ash-frameworks-dsl-on-a-spin-for-rpc-fun</guid>
      </item>
    
      <item>
        <title><![CDATA[Goatmire Elixir - Last chance in a while]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/lawik?uid=uggwX" width="64" height="64" />
              </td>
              <td>
                <h1>Goatmire Elixir - Last chance in a while</h1>

                <font color="#aaa">
                  <font color="#aaa">
                     5 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> lawik
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
As vacations wind down. Your spot of joy before the winter sets in is of course Goatmire Elixir. It is high time to get tickets and travel sorted. All the information is on the website. Phenomenal speakers, legendary free workshops and with us skipping the year 2027 this is your last chance for a while to see what Goatmire is all about.</p>
<p>
<a href="https://goatmire.com">https://goatmire.com</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/uggwX-goatmire-elixir---last-chance-in-a-while">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate> 5 Aug 2026 19:22:27 +0000</pubDate>
        <link>https://elixirstatus.com/p/uggwX-goatmire-elixir---last-chance-in-a-while</link>
        <guid>https://elixirstatus.com/p/uggwX-goatmire-elixir---last-chance-in-a-while</guid>
      </item>
    
      <item>
        <title><![CDATA[(WIP) PON-BEAM re-architecture of the Erlang/OTP]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/matheuscamarques?uid=od9ZA" width="64" height="64" />
              </td>
              <td>
                <h1>(WIP) PON-BEAM re-architecture of the Erlang/OTP</h1>

                <font color="#aaa">
                  <font color="#aaa">
                     5 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> matheuscamarques
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
(WIP) PON-BEAM is a complete re-architecture of the Erlang/OTP Virtual Machine (ERTS — Erlang Run-Time System) using the Notification-Oriented Paradigm (PON)
<a href="https://github.com/matheuscamarques/pon_beam">https://github.com/matheuscamarques/pon_beam</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/od9ZA-wip-pon-beam-re-architecture-of-the-erlangotp">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate> 5 Aug 2026 17:07:21 +0000</pubDate>
        <link>https://elixirstatus.com/p/od9ZA-wip-pon-beam-re-architecture-of-the-erlangotp</link>
        <guid>https://elixirstatus.com/p/od9ZA-wip-pon-beam-re-architecture-of-the-erlangotp</guid>
      </item>
    
      <item>
        <title><![CDATA[Hologram v0.11: Regular Expressions, Client Stacktraces, and More]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/bartblast?uid=LxSnY" width="64" height="64" />
              </td>
              <td>
                <h1>Hologram v0.11: Regular Expressions, Client Stacktraces, and More</h1>

                <font color="#aaa">
                  <font color="#aaa">
                     5 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> bartblast
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
Elixir regexes now run in the browser, through a PCRE2 parser, translator and interpreter, so they return what the BEAM returns. Client errors now carry the same messages and stacktraces as errors raised on the server. Plus dynamic component and element tags, attribute and prop spread, and umbrella project support.</p>
<p>
<a href="https://hologram.page/blog/hologram-v0-11">https://hologram.page/blog/hologram-v0-11</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/LxSnY-hologram-v011-regular-expressions-client-stacktraces-and-more">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate> 5 Aug 2026 17:01:52 +0000</pubDate>
        <link>https://elixirstatus.com/p/LxSnY-hologram-v011-regular-expressions-client-stacktraces-and-more</link>
        <guid>https://elixirstatus.com/p/LxSnY-hologram-v011-regular-expressions-client-stacktraces-and-more</guid>
      </item>
    
      <item>
        <title><![CDATA[Security Vendor's AI Best Practices Labels Critical Elixir RCE Safe]]></title>
        <description><![CDATA[
          <table width="100%" border="0">
            <tr>
              <td width=80 valign=top>
                <img src="https://elixirstatus.com/rss/avatar/realcorvus?uid=IHXyV" width="64" height="64" />
              </td>
              <td>
                <h1>Security Vendor's AI Best Practices Labels Critical Elixir RCE Safe</h1>

                <font color="#aaa">
                  <font color="#aaa">
                     4 Aug 2026
                  </font>
                  <font color="#aaa">
                    by
                    <i class="icon-git_circle"></i> realcorvus
                  </font>
                  <font color="#aaa">
                    
                  </font>
                </font>

                <p>
A post about the dangers of AI generated SEO spam, especially as it relates to modern cybersecurity. </p>
<p>
<a href="https://paraxial.io/blog/ai-spam">https://paraxial.io/blog/ai-spam</a></p>

                <hr>
                <small><a href="https://elixirstatus.com/p/IHXyV-security-vendors-ai-best-practices-labels-critical-elixir-rce-safe">View on ElixirStatus</a></small>
              </td>
            </tr>
          </table>
        ]]></description>
        <pubDate> 4 Aug 2026 12:42:19 +0000</pubDate>
        <link>https://elixirstatus.com/p/IHXyV-security-vendors-ai-best-practices-labels-critical-elixir-rce-safe</link>
        <guid>https://elixirstatus.com/p/IHXyV-security-vendors-ai-best-practices-labels-critical-elixir-rce-safe</guid>
      </item>
    
  </channel>
</rss>

