<?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>Forem: Aksh Kumar</title>
    <description>The latest articles on Forem by Aksh Kumar (@fire_op_09793239d94e6553f).</description>
    <link>https://forem.com/fire_op_09793239d94e6553f</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2280699%2Fc3f293a0-b3f7-4dd7-8552-001043b893a8.png</url>
      <title>Forem: Aksh Kumar</title>
      <link>https://forem.com/fire_op_09793239d94e6553f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/fire_op_09793239d94e6553f"/>
    <language>en</language>
    <item>
      <title>Edge AI fails not at detection but at capturing the full story</title>
      <dc:creator>Aksh Kumar</dc:creator>
      <pubDate>Sat, 18 Apr 2026 17:01:54 +0000</pubDate>
      <link>https://forem.com/fire_op_09793239d94e6553f/edge-ai-fails-not-at-detection-but-at-capturing-the-full-story-1a39</link>
      <guid>https://forem.com/fire_op_09793239d94e6553f/edge-ai-fails-not-at-detection-but-at-capturing-the-full-story-1a39</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fmk1awk3i003l00ly5hhu.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fmk1awk3i003l00ly5hhu.png" alt=" " width="800" height="533"&gt;&lt;/a&gt;While working with an edge device through an Android SDK, I noticed a key limitation in how event evidence is handled.&lt;/p&gt;

&lt;p&gt;Current limitations in this setup&lt;/p&gt;

&lt;p&gt;• Captures only the moment of detection&lt;br&gt;
• Provides very short clips of 2 to 3 seconds&lt;br&gt;
• No access to pre event context&lt;br&gt;
• No visibility into post event outcome&lt;br&gt;
• No option to retrieve additional footage on demand&lt;/p&gt;

&lt;p&gt;Why this is a problem&lt;/p&gt;

&lt;p&gt;• Lack of context leads to misjudgment&lt;br&gt;
A short clip is not enough to confirm if the event is real or noise&lt;/p&gt;

&lt;p&gt;• No pre event visibility&lt;br&gt;
It is not possible to understand what led to the detection&lt;br&gt;
This makes debugging and validation difficult&lt;/p&gt;

&lt;p&gt;• No post event validation&lt;br&gt;
There is no way to see what happened after the trigger&lt;br&gt;
Outcomes remain unclear&lt;/p&gt;

</description>
      <category>ai</category>
      <category>android</category>
      <category>edgedevice</category>
      <category>computervision</category>
    </item>
    <item>
      <title>[Boost]</title>
      <dc:creator>Aksh Kumar</dc:creator>
      <pubDate>Sat, 18 Apr 2026 16:58:51 +0000</pubDate>
      <link>https://forem.com/fire_op_09793239d94e6553f/-nmc</link>
      <guid>https://forem.com/fire_op_09793239d94e6553f/-nmc</guid>
      <description></description>
    </item>
  </channel>
</rss>
