<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <updated>2026-11-03T02:21:31Z</updated>
  <generator>https://nostr.now</generator>

  <title>Nostr notes by dreieck</title>
  <author>
    <name>dreieck</name>
  </author>
  <link rel="self" type="application/atom+xml" href="https://nostr.now/npub10a0wc2cp96z5xsq3amdrp6t2vurnnklgcacrvyxd35j8nm9jm6kq9jsyaw.rss" />
  <link href="https://nostr.now/npub10a0wc2cp96z5xsq3amdrp6t2vurnnklgcacrvyxd35j8nm9jm6kq9jsyaw" />
  <id>https://nostr.now/npub10a0wc2cp96z5xsq3amdrp6t2vurnnklgcacrvyxd35j8nm9jm6kq9jsyaw</id>
  <icon>https://assets.chaos.social/accounts/avatars/111/677/120/241/254/319/original/0d214b18e1e94fbd.png</icon>
  <logo>https://assets.chaos.social/accounts/avatars/111/677/120/241/254/319/original/0d214b18e1e94fbd.png</logo>




  <entry>
    <id>https://nostr.now/nevent1qqsypkzdstkqzcuaaxe9falyscql0pe6a3t5z7l64c44ufcfsjdvtnszypl4amptqyhg2s6qz8hd5v8fdfnswwwmarrhqdssekxjg70vkt02c9gl2jy</id>
    
      <title type="html">Why should an #RNode not be able to do that? And yes, as I meant, ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsypkzdstkqzcuaaxe9falyscql0pe6a3t5z7l64c44ufcfsjdvtnszypl4amptqyhg2s6qz8hd5v8fdfnswwwmarrhqdssekxjg70vkt02c9gl2jy" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqszhzjw4tazd3jx09psrh3zumpanzvd685f593hrwjhv8h2z07zymsvy7y9f&#39;&gt;nevent1q…7y9f&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;Why should an #RNode not be able to do that?&lt;br/&gt;&lt;br/&gt;And yes, as I meant, end-user #usability due to lack of appropriate #software is not so good yet in #Reticulum, but instead of just writing software for a completely new system, the same energy could have gone into writing end user friendly #Reticulum software (both #firmware for nodes, and software for more capable devices like smartphones, desktop computers, etc.)
    </content>
    <updated>2026-02-08T15:53:14Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsv9du97h0v3hvfmypuguxecjqq28jvudglu8udcm096rdwy4ez3rqzypl4amptqyhg2s6qz8hd5v8fdfnswwwmarrhqdssekxjg70vkt02cglj7qz</id>
    
      <title type="html">(2/2) Why then people concentrate so much on #MeshCore, instead ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsv9du97h0v3hvfmypuguxecjqq28jvudglu8udcm096rdwy4ez3rqzypl4amptqyhg2s6qz8hd5v8fdfnswwwmarrhqdssekxjg70vkt02cglj7qz" />
    <content type="html">
      In reply to &lt;a href=&#39;/nevent1qqsq0xt3t7a2axqfx79pg732695kfx6lthz8zw6dcuvtydulfux9nagv23s8r&#39;&gt;nevent1q…3s8r&lt;/a&gt;&lt;br/&gt;_________________________&lt;br/&gt;&lt;br/&gt;(2/2)&lt;br/&gt;Why then people concentrate so much on #MeshCore, instead of making a good messaging client for #Reticulum and then we are basically at the same functionality that #MeshCore gives, plus much more advantages?&lt;br/&gt;&lt;br/&gt;(Or am I wrong?)
    </content>
    <updated>2026-02-08T15:18:17Z</updated>
  </entry>

  <entry>
    <id>https://nostr.now/nevent1qqsq0xt3t7a2axqfx79pg732695kfx6lthz8zw6dcuvtydulfux9nagzypl4amptqyhg2s6qz8hd5v8fdfnswwwmarrhqdssekxjg70vkt02c4tth0w</id>
    
      <title type="html">(½) In my understanding, one reason why #Reticulum is not usable ...</title>
    
    <link rel="alternate" href="https://nostr.now/nevent1qqsq0xt3t7a2axqfx79pg732695kfx6lthz8zw6dcuvtydulfux9nagzypl4amptqyhg2s6qz8hd5v8fdfnswwwmarrhqdssekxjg70vkt02c4tth0w" />
    <content type="html">
      (½)&lt;br/&gt;In my understanding, one reason why #Reticulum is not usable yet for the use case &amp;#34;internet-free communication accessible to many people&amp;#34; is missing multicast feature, meaning #groupchat s not working.&lt;br/&gt;&lt;br/&gt;But now I come to the conclusion that #MeshCore has the same issue: Group chats (channels in MeshCore) are just flood packets, not guaranteed to receive every group member (only where randomly at time of sending the packet makes it through), and beeing flood doing a big burden on the network.
    </content>
    <updated>2026-02-08T15:15:43Z</updated>
  </entry>

</feed>