<p>We&#39;re trying out a new activity called a &quot;challenge problem&quot; where we focus on a theme for several months through submissions that may take various different forms. It&#39;s like a hybrid between a virtual workshop and a game jam.</p><p>For our first challenge problem, the theme is &quot;fearless extensibility&quot;.</p><p>If this sounds interesting to you, please see the challenge problem thread for additional context and submission details. Submissions are due on 2024-11-01.</p><p><a href="https://forum.malleable.systems/t/challenge-problem-fearless-extensibility/205" target="_blank" rel="nofollow noopener noreferrer" translate="no"><span class="invisible">https://</span><span class="ellipsis">forum.malleable.systems/t/chal</span><span class="invisible">lenge-problem-fearless-extensibility/205</span></a></p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://haunted.computer/@iximeow" class="u-url mention">@<span>iximeow</span></a></span> </p><p>Also, I&#39;ve seen no mention of building a self-rollback capability into their deployments. eg. for whatever reason the install fails (the reboot failing is considered an install fail), the prior version gets reinstated.</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> <span class="h-card" translate="no"><a href="https://tenforward.social/@noracodes" class="u-url mention">@<span>noracodes</span></a></span> in this particular case, a premature-aging issue, which certainly does make it harder to test for. (I am aware at least one buyer of coin-cell batteries that does accelerated-aging tests (load/temperature etc) but that&#39;s an inherently consumable product, so it&#39;s easier and more obviously necessary.) But yeah, I was just going for &quot;bulk electronics are better but only *most* of the time...&quot;</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> we don&#39;t know if (automated) mutual pledge agreements are legal so we left that part out entirely, but if they happen to be, they enable treating the network as a grid (similar to a power grid, but for money), which is always neat</p>

<p><span class="h-card" translate="no"><a href="https://mastodon.social/@whitequark" class="u-url mention">@<span>whitequark</span></a></span> Not much yet, other than saying that it&#39;s a good enough scope :)</p>

<p><span class="h-card" translate="no"><a href="https://social.hackerspace.pl/@q3k" class="u-url mention">@<span>q3k</span></a></span> was nanographs involved</p>

<p><span class="h-card" translate="no"><a href="https://chaos.social/@SoniEx2" class="u-url mention">@<span>SoniEx2</span></a></span> this does not seem to me like a coherent plan, sorry</p>

<p><span class="h-card" translate="no"><a href="https://tech.lgbt/@magicatgwen" class="u-url mention">@<span>magicatgwen</span></a></span> so, i think of recruitment as more _retention_ than _acquisition_</p><p>people will naturally accrete around something useful. but then many will drop off. but then you might be able to make that number lower if you try</p>

<p>This was a pain in the ass, but we managed to get the scope to the basement lab where it&#39;s gonna be worked on until we find a better, permanent space.</p><p>&#39;We&#39; in this is a little hardware hacking, analytical chemistry and semiconductor research lab some friends and I are founding in Munich - more about that soon!</p>