<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>research — toothywalrus</title><link>https://blog.toothywalrus.dev/topics/research/</link><description>Long-form write-ups about SDR, homelab, electronics and tooling — plus a weekly log of what actually got built.</description><language>en-us</language><lastBuildDate>Thu, 06 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.toothywalrus.dev/topics/research/index.xml" rel="self" type="application/rss+xml"/><item><title>stockflow, week 32: born Monday, mostly cancelled Thursday</title><link>https://blog.toothywalrus.dev/logbook/2026-w32-stockflow/</link><pubDate>Thu, 06 Aug 2026 00:00:00 +0000</pubDate><guid>https://blog.toothywalrus.dev/logbook/2026-w32-stockflow/</guid><category>weeknotes</category><category>research</category><description>&lt;p&gt;New repo on Monday. By Thursday most of it was argued away.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The idea&lt;/strong&gt; was a tool to manage stock-footage contributions across
platforms: analytics on what earns, then automation on top of that.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The problem&lt;/strong&gt; is that there is no contributor earnings API. Not
rate-limited, not partner-gated, not undocumented-but-reachable — absent. The
numbers I wanted to analyse are visible to a human in a dashboard and nowhere
else. Everything I&amp;rsquo;d sketched on top of that assumption goes with it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;What survives&lt;/strong&gt; is smaller and less interesting to describe: embedded
metadata and delivery. That part is real work with a real result, it just
isn&amp;rsquo;t the product I opened the repo to build.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;The honest version:&lt;/strong&gt; this is four days spent to avoid four weeks, and I do
believe that&amp;rsquo;s the right trade. It still reads as a loss in a week&amp;rsquo;s log, and
I&amp;rsquo;d rather write it down that way than dress it up. The repo stays, at a
tenth of its intended scope.&lt;/p&gt;
&lt;div class="provenance"&gt;
 &lt;h2&gt;Where this came from&lt;/h2&gt;
 &lt;p&gt;Work between 3 and 6 August 2026 in the &lt;code&gt;stockflow&lt;/code&gt; repository — the initial
scoping commit, the platform data-access research, and the build-vs-buy case
against the planned scope. Decision records 0001–0005. The repository is
private.&lt;/p&gt;
&lt;p&gt;The &amp;ldquo;no earnings API&amp;rdquo; conclusion comes from reading platform documentation,
not from attempting and failing to authenticate against one. If a private or
partner-only endpoint exists, I did not find it and did not have access to
test for it.&lt;/p&gt;

&lt;/div&gt;
</description></item></channel></rss>