<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated>2026-10-16T13:23:34Z</updated>
  <generator>https://nostr.now</generator>

  <title>Nostr notes by Adam</title>
  <author>
    <name>Adam</name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://nostr.now/npub1wnwy80yqtx5fjjkzwskpuu95x37vnsgrl4u75fuhxhzcjztjjegskuecjr.rss" />
  <link href="https://nostr.now/npub1wnwy80yqtx5fjjkzwskpuu95x37vnsgrl4u75fuhxhzcjztjjegskuecjr" />
  <id>https://nostr.now/npub1wnwy80yqtx5fjjkzwskpuu95x37vnsgrl4u75fuhxhzcjztjjegskuecjr</id>
  <icon>https://nostrcheck.me/media/74dc43bc8059a8994ac2742c1e70b4347cc9c103fd79ea279735c58909729651/e02b787600f760313f313e9f78dcab7c8c619029adce061c42d5a32f5b8403c3.webp</icon>
  <logo>https://nostrcheck.me/media/74dc43bc8059a8994ac2742c1e70b4347cc9c103fd79ea279735c58909729651/e02b787600f760313f313e9f78dcab7c8c619029adce061c42d5a32f5b8403c3.webp</logo>




  <entry>
    <id>https://nostr.now/nevent1qqsxt7rhddxa9htwqw6xxpj5q9h2pk7tjcw6q2gccyxwl45gq7jy4xqzyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zxdklq5</id>
    
      <title type="html">Got it working with HA Connect ZBT-2. It acts as either Thread or ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsxt7rhddxa9htwqw6xxpj5q9h2pk7tjcw6q2gccyxwl45gq7jy4xqzyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zxdklq5" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqs2tnexpwx3wxpdrkdmyeen86ykf88jy75ek2z45jz8ex6mhtu890qpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0dwkwg2&#39;&gt;nevent1q…kwg2&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;Got it working with HA Connect ZBT-2. It acts as either Thread or ZigBee so if you want both types, better to get two. The components in IoT stack handle all the config, you just need to tell it where to find the ZBT and use openthread:requireNodeLabel to force it onto the box that has the device attached. Matter should be locked to a box with Bluetooth so you can provision devices. &lt;br/&gt;Works great! 😁
    </content>
    <updated>2026-10-01T12:55:48Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqs9qnkw2upxv5ctuzqts0z63g47f35mfsm5jgk7c52phvm6p9hrnkgzyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zrf0573</id>
    
      <title type="html">Good morning Berlin! ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqs9qnkw2upxv5ctuzqts0z63g47f35mfsm5jgk7c52phvm6p9hrnkgzyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zrf0573" />
    <content type="html">
      Good morning Berlin!&lt;br/&gt;  &lt;img src=&#34;https://npub1wnwy80yqtx5fjjkzwskpuu95x37vnsgrl4u75fuhxhzcjztjjegskuecjr.blossom.band/d6fe20118c4ce18da5595373f6cc95c12772f61fe29f6b64ca652c4ae2c15045.jpg&#34;&gt; 
    </content>
    <updated>2026-10-01T12:48:26Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqswwgp9rhgdumvalyta3zewy2h3k9vt6xsywq8x5nd2h5yk03zarqgzyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9ztlyaaf</id>
    
      <title type="html">OrangeLab 0.7.0 released! This one brings OpenID Connect ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqswwgp9rhgdumvalyta3zewy2h3k9vt6xsywq8x5nd2h5yk03zarqgzyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9ztlyaaf" />
    <content type="html">
      OrangeLab 0.7.0 released! &lt;br/&gt;&lt;br/&gt;This one brings OpenID Connect authentication using PocketID for apps that support it. That means passkey instead of passwords and multiple accounts. As a bonus you get a homepage with list of apps available.&lt;br/&gt;&lt;br/&gt;IoT stack now has components to support ZigBee/Thread devices including WiFi/Bluetooth provisioning (OpenThread, Matter) and cameras (Frigate). All local without need to any Google/Apple/Amazon border router or sending your data anywhere outside of your network.&lt;br/&gt;&lt;br/&gt;Use Forgejo and Zot to store your repos and docker images. All images used in the cluster are automatically cached in case there any issues with upstream.&lt;br/&gt;&lt;br/&gt;&lt;a href=&#34;https://github.com/OrangeLab-space/orange-lab/releases/tag/v0.7.0&#34;&gt;https://github.com/OrangeLab-space/orange-lab/releases/tag/v0.7.0&lt;/a&gt;&lt;br/&gt; &lt;br/&gt; &lt;img src=&#34;https://blossom.primal.net/fa89adf8f3a7f38a88d9cc44cbc61d87c2198f1f742fb11a2dc29d606988f493.png&#34;&gt;  
    </content>
    <updated>2026-09-29T13:34:03Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsqqq8j9x9fyd3vle4rz5uyw5d5f0mkzr2mw2fqrd0getnwytx3klszyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zem4wyf</id>
    
      <title>Nostr event nevent1qqsqqq8j9x9fyd3vle4rz5uyw5d5f0mkzr2mw2fqrd0getnwytx3klszyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zem4wyf</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsqqq8j9x9fyd3vle4rz5uyw5d5f0mkzr2mw2fqrd0getnwytx3klszyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zem4wyf" />
    <content type="html">
       &lt;img src=&#34;https://blossom.primal.net/a36a0cc6bad905aae2541615359d904740f7cb67db8cd15a32434f48f649b659.jpg&#34;&gt; 
    </content>
    <updated>2026-09-03T23:49:12Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsqqqytf07vhc9qqtchkg09yus6hvylxsxg8pd5vvqdv69acgc7d7qzyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zc6q0ve</id>
    
      <title type="html">Does FIPS already handle public connections? I noticed in the ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsqqqytf07vhc9qqtchkg09yus6hvylxsxg8pd5vvqdv69acgc7d7qzyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zc6q0ve" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsfcz34cgamxzmy7pm7ag0wqt4v724jvzrhqku6gwkpc2nvhtk4d4gpp4mhxue69uhkummn9ekx7mqnrqmu8&#39;&gt;nevent1q…qmu8&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;Does FIPS already handle public connections? I noticed in the docs NAT is not supported yet. Does it mean that I just need to expose the ports to create geographically distributed mesh for now?
    </content>
    <updated>2026-04-15T10:56:06Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqs2vs36452wgcdrm6em32kue5u6zmgu0lc5u8090lncft9yaf2ls8czyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zglzl4c</id>
    
      <title type="html">BIP-110 is one example but there are many use cases for using ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqs2vs36452wgcdrm6em32kue5u6zmgu0lc5u8090lncft9yaf2ls8czyp6dcsauspv63x22cf6zc8nsks68ejwpq07hn638ju6utzgfw2t9zglzl4c" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsvd8052vwszjysw63g07fnss2ev5xldtvtkupp59vky0p6tpgax2shfppd8&#39;&gt;nevent1q…ppd8&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;BIP-110 is one example but there are many use cases for using custom images, like when you build your own from scratch. By default OrangeLab runs standard version of Knots (or Core), not the custom one. &lt;br/&gt;One might argue that promoting protocol change to increase OPRETURN from storing hashes to storing data is shitforking 😉&lt;br/&gt;Node runners have an incentive to keep things light on resources, both storage and bandwidth. It&amp;#39;s a matter of negotiating how far the validation rules should go. In the end it&amp;#39;s up to node operators to decide what a valid block is. You&amp;#39;re welcome to run any image and version, I&amp;#39;m just making it easier to do regardless of what you decide.  &lt;br/&gt;&lt;br/&gt;
    </content>
    <updated>2026-02-27T04:33:44Z</updated>
  </entry>

</feed>