2026-05-23T11:12:59Z https://nostr.now lostcause https://nostr.now/npub1khf5amw8mrupe649a5mhkk3d2d8wjj06urz6kwawpftk4f68tjlstdmd3q https://m.primal.net/LsQy.jpg https://m.primal.net/LsQy.jpg https://nostr.now/nevent1qqstmuqnf6tkkkr5kstgtsl96exhnh8v3x3vcplzgn0j8v89v8uatwgzyz6axnhdclv0s8825hknw76694f5a62fltsvt2em4c99w648gawt76gwdtf I’ve been working on something new: **NScript**.<br/><br/>It’s a small, statically typed scripting language built specifically for Nostr.<br/><br/>Instead of treating Nostr as a library bolted onto another language, NScript makes things like events, relays, signers, filters, permissions and NIPs part of the language itself.<br/><br/>The idea is to make Nostr automation and app logic easier to write, easier to audit, and harder to get subtly wrong.<br/><br/>It’s still early, but it can already parse and type-check scripts, compile them to an intermediate form, and run them against capability-controlled hosts. Support is growing across NIPs including NIP-17, NIP-44, NIP-47, NIP-59, NIP-65, NIP-77 and others.<br/><br/>I’m also starting to look beyond individual NIPs at higher-level protocols like **Concord**, which is exactly the kind of thing NScript should eventually be able to script cleanly.<br/><br/>Repo:<br/><a href="https://github.com/imattau/nscript">https://github.com/imattau/nscript</a><br/><br/>Still experimental, but it’s starting to feel like a real Nostr-native runtime rather than just another SDK.<br/><br/>#nostr #nostrdevs #nscript #nostrblog #scripting #development #nips #concord #blossom 2026-09-21T09:17:34Z https://nostr.now/nevent1qqspw648pqsmusm7g639qew9gqm93y8endznt7dsed95qnlnlq7p68gzyz6axnhdclv0s8825hknw76694f5a62fltsvt2em4c99w648gawt75gv083 Big update to **npack** today.<br/><br/>npack is a Nostr-native package manager where releases are signed by Nostr keys, discovered through relays and stored as content-addressed `.npk` packages on Blossom.<br/><br/>The latest work adds some important pieces:<br/><br/>• a local package catalogue with `npack refresh`, `search` and `info`<br/>• a background `npackd` service so graphical app stores and other tools can use npack without needing to understand Nostr<br/>• proper transaction progress, cancellation, rollback and recovery<br/>• separate user/system daemons with PolicyKit authorisation<br/>• AppStream metadata support for Linux software stores<br/>• Nix integration has now been tested against real npack releases<br/><br/>v0.3.0 is being prepared now.<br/><br/>The interesting bit for me is where this is heading: Nostr can handle software discovery and publisher identity, Blossom can handle the actual package storage, while npack provides the package management layer on top.<br/><br/>Still early, but it is becoming a fairly complete stack.<br/><br/><a href="https://github.com/imattau/npack">https://github.com/imattau/npack</a><br/><br/>#nostr #npack #linux #opensource #nostrblog 2026-09-21T04:11:09Z https://nostr.now/nevent1qqsf6mnyghres5y089ge90act6f0adeh9fkcq6rphcelx8ht9xgzc7gzyz6axnhdclv0s8825hknw76694f5a62fltsvt2em4c99w648gawt7fdrm72 NostrHost has moved forward quite a bit over the last few days.<br/><br/>The biggest change is that the native app system is starting to feel real. Apps can now be discovered, installed, updated, moved, backed up and restored without leaning so heavily on the old YunoHost model.<br/><br/>Nsites are also starting to become a proper part of the platform. They can now be discovered alongside apps in the catalogue, which makes them feel much less like a side feature and more like part of the normal hosting experience.<br/><br/>The Nostr control side has also been pushed further, with more of the server’s identity, permissions and admin actions flowing through the same model.<br/><br/>There have been plenty of smaller improvements too, including better catalogue handling, multi-user app support, cleaner admin settings and more work removing older YunoHost dependencies.<br/><br/>Still early, but it is starting to feel much more like one platform now.<br/><br/><a href="https://github.com/imattau/nostrhost">https://github.com/imattau/nostrhost</a><br/><br/>#nostr #selfhosting #opensource #yunohost #nostrblog #nostrhost 2026-09-18T08:38:19Z https://nostr.now/nevent1qqs9xe4kj9fuy9zn54jf36xkgf4s234kfj057gh90plzuc9mpjfu5tczyz6axnhdclv0s8825hknw76694f5a62fltsvt2em4c99w648gawt78vyf69 Core Lightning is now packaged for YunoHost and up and running.<br/><br/><a href="https://github.com/imattau/core-lightning_ynh">https://github.com/imattau/core-lightning_ynh</a><br/><br/>Even better, the existing Alby Hub YunoHost package successfully connects to it. That gives us a working self-hosted stack:<br/><br/>Bitcoin Core → Core Lightning → Alby Hub<br/><br/>The goal is to make running your own Bitcoin + Lightning infrastructure much easier through YunoHost and the Nostr Catalog.<br/><br/>⚠️ **Important:** Core Lightning can hold and move real Bitcoin. This YunoHost package is new and should be considered experimental. Bugs, configuration mistakes, failed backups or loss of Lightning node state can result in loss of funds.<br/><br/>Start with testnet where possible. If using mainnet, only use funds you can afford to lose and make sure you understand Lightning backups and recovery first.<br/><br/>Core Lightning:<br/><a href="https://github.com/imattau/core-lightning_ynh">https://github.com/imattau/core-lightning_ynh</a><br/><br/>Alby Hub:<br/><a href="https://github.com/imattau/alby-hub_ynh">https://github.com/imattau/alby-hub_ynh</a><br/><br/>Install through the Nostr Catalog:<br/><a href="https://github.com/imattau/nostr_catalog_ynh">https://github.com/imattau/nostr_catalog_ynh</a><br/><br/>#nostr #bitcoin #lightning #alby #yunohost #selfhosting #nostrdevs 2026-09-10T23:03:16Z https://nostr.now/nevent1qqsff8qqfjtewms0nl83qre0kc9mpy2tk97act9ap2x2tpunlk0z9gqzyz6axnhdclv0s8825hknw76694f5a62fltsvt2em4c99w648gawt78ja6tw #privacy #decentralized #messenger #socialmedia<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/naddr1qq04w6tjv4xkjm3df4jhxum9denk2u3d2fjhv6t9wukkyut0xamnvq3qc3gyzcvf2xakqy4vy06umu7hgpr97ttyp05yrlvmk8g8xvmse57qxpqqqp65wpjdhn9" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">naddr1qq…dhn9</a></span> </div> <hr> <p><strong>WireMin</strong></p> <p>In 2025, the battle for digital privacy rages on. Big Tech’s data grabs and government overreach haven’t let up, making tools like WireMin Messenger more relevant than ever. WireMin is a decentralized social network and messenger that ditches central servers for a peer-to-peer setup. Your device does the heavy lifting routing and storing messages, leaving no honeypot for snoopers. It’s built for privacy, security, and dodging censorship. But how does it hold up in today’s crowded field of secure comms? Let’s break it down.</p> <p><strong>How It Stacks Up in 2025</strong></p> <p>To gauge WireMin’s worth, we need to pit it against the big players in privacy-focused messaging: SimpleX, Matrix, and Session. Here’s where they stand in 2025.</p> <ul> <li><strong>SimpleX</strong>: This one’s still the anonymity king. By 2025, SimpleX has likely doubled down on its no-user-IDs model, using temporary, anonymous pairwise identifiers that make tracking a nightmare for anyone trying. It’s fully decentralized, like WireMin, but leans harder into disappearing footprints. WireMin counters with cryptographic social identities less transient but still tough as nails against surveillance. SimpleX might win for the ultra-cautious, but WireMin’s usability keeps it in the fight.</li> <li><strong>Matrix</strong>: The federated behemoth has grown up a bit by 2025. It’s probably patched some of its old metadata leaks, beefing up encryption or server-side privacy controls. Still, Matrix’s reliance on servers, however distributed leaves it vulnerable compared to WireMin’s serverless purity. Matrix has the edge in features and a massive user base, but if privacy’s your hill to die on, WireMin runs circles around it.</li> <li><strong>Session</strong>: Session’s blockchain roots have likely blossomed by now think a slicker node network and tighter crypto integration. But its choice to skip perfect forward secrecy still haunts it. WireMin, with full end-to-end encryption and metadata shielding, delivers a cleaner privacy punch. Session’s got flash, but WireMin’s got substance.</li> </ul> <p><strong>The Good and the Bad</strong></p> <p>Here’s what WireMin brings to the table, and where it stumbles.</p> <p><strong>Pros:</strong></p> <ul> <li><strong>True Decentralization</strong>: No servers, no choke points. It’s just you and your peers, talking directly. That’s a middle finger to anyone trying to shut it down.</li> <li><strong>Ironclad Privacy</strong>: End-to-end encryption is standard, but WireMin goes further, cloaking your social metadata so even your chat habits stay off the radar.</li> <li><strong>Censorship-Proof</strong>: In 2025’s clampdown climate, WireMin’s design ensures no one can gag you—short of smashing your device.</li> </ul> <p><strong>Cons:</strong></p> <ul> <li><strong>Small Crowd</strong>: WireMin’s user base is still niche. If your crew’s stuck on mainstream apps, you’ll feel the isolation.</li> <li><strong>Tech Hurdles</strong>: Self-hosting is the price of freedom here. By 2025, it’s probably still a fiddly process great for geeks, daunting for newbies.</li> <li><strong>Staying Power</strong>: WireMin’s young. Without steady updates and community muscle, it could fizzle out. Time will tell.</li> </ul> <p><img src="https://wiremin.org/main/images/comparisonH.png" alt="clear-img"/></p> <p><strong>My Take After Using It</strong></p> <p>Jumping into WireMin in 2025 is a mixed bag. The interface is lean and mean, no fluff, just function. Messages zip through fast, and knowing my data’s not feeding some corporate algorithm feels damn good. But setting it up? That’s a slog. Self-hosting demands patience and a bit of know-how, think port forwarding and network tweaks. Once you’re in, it’s smooth sailing, but the entry fee’s steep. It’s a tool for the dedicated, not the dabblers.</p> <p><strong>Verdict</strong></p> <p>WireMin Messenger isn’t here to coddle you.. it’s here to protect you. In 2025, it stands tall as a no-compromise option for anyone serious about privacy. It’s not the slickest or the most popular, but that’s not the point. If you’re ready to wrestle with its setup and don’t mind a smaller network, WireMin’s a fortress worth defending. Need something easier or more connected? SimpleX or Matrix might be your speed. For the privacy diehards, though, WireMin’s a rebel with a hell of a cause, and it’s worth rooting for.</p> <p>sources</p> <p><a href="https://wiremin.org">https://wiremin.org</a></p> <p><a href="https://github.com/up4w/up4w-core">https://github.com/up4w/up4w-core</a></p> <p><a href="https://inleo.io/@danishcrypto/wiremin-messenger-review--kex?referral=danishcrypto">this is also on #hive</a></p> <hr> <p><strong>Want more privacy and crypto rants? Hit me up:</strong></p> <p><strong><a href="https://linkfork.io/danishcrypto">https://linkfork.io/danishcrypto</a></strong></p> <ul> <li>X: <a href="https://x.com/DanishCryptoDK">DanishCryptoDK</a></li> <li>Hive: <a href="https://inleo.io/profile/danishcrypto">DanishCrypto</a></li> <li>Nostr: npub1c3gyzcvf2xakqy4vy06umu7hgpr97ttyp05yrlvmk8g8xvmse57qj286r6</li> <li>Telegram channel: <a href="https://t.me/DanishCryptoDK">DanishCryptoDK</a></li> <li>private Telegram: <a href="https://t.me/DanishCrypto">DanishCrypto</a></li> </ul> <p><img src="https://wiremin.org/main/images/wireminlogo.png" alt=""/></p> </blockquote> 2025-03-15T08:05:23Z