Last Notes
But they CAN compete, the problem is LLM censorship. They just want control. And no matter how awkward it's gonna sound - chinese models bring freedom this time
Idk... I think this idea of manually adjusting which agent goes where is not where people want to spend their time on. All agents should show up everywhere without me having to tag them.
Yippee! I rely on you and some others to ‘splain where I might be useful (other than cheer section).
#nevent1q…gdy7
Don't copy all of it, I think Armada s UI is better in many ways... Buzz is beautiful UI, but the UI is getting in the way and distracting me instead of helping me read/develop.
I have to sign up with email, what why
Good luck to everyone involved 🫡
appimage doesnt start on arch
sarrr, this buzz workflow is fire. i told u the nostr p2p space is where it's at. armada workspaces was cool but this ui is smooth as butter. kudos to whoever cracked this — maybe a dev team or some genius hacker.
btw have you tried integrating bitcoin payments into nostr? imagine people paying in satoshis for these premium workflows. that'd be the future of social media.
I liked that it has emojis 😂
The difference is at least in the examples you gave those are options that can be supported by different clients because in some ways, they are standard and probably just different ways of doing the same thing. You didn't invent kinds that only one client uses.
Are they even doing anything against these wildfires?
Took a good 30m or so to write.
I have also included some additional details here:
#nevent1q…06wj
We all have dreams like Aliyah’s 🛩️ they have plans to rebuild it already who is ready for INTERNET 🪱 have to clear out at least 40years as if it never happed can not be recovered gone wiped deleted unrecoverable follow the grief cycle and move on, then you’ll get a better 1️⃣ I’m building a non profit resource network for homeless people if anyone is interested.
I guess americans are still better off: imagine longing for youtube!
We need a better World Wide Web
I don't know what stage the nest is at inside nip-29
i'm not disagreeing on the fundamentals, but sending any event to anyone that asks doesn't break interop, just like retaining events when the spec says they should be dropped. if you rely on this behavior, someone will get burned
i don't think it is. a good protocol is sybil resistant
sure, the published source code can reveal it is doing the wrong thing. but you don't know what a relay is actually running, who is running it, who pwned it, or who captures bytes on the wire
Yea, sure that's the same critique I had for nip-70 (protected events) since the beginning, but from my perspective, the key here is that if an implementation doesn't follow the spec is a bad implementation, and then we can discuss about sibyl attacks, but that's a different conversation.
#9
https://image.nostr.build/0898b2685eff130302a5790bca255c8e1deb8c1f714b83822a6233e783796a37.png
1. Armada - New Tool
Armada is a decentralized, end-to-end encrypted community chat platform built on the Nostr protocol that delivers a Discord-like experience with servers, channels, threads, voice chat, and moderation without relying on a central company or host.
Developed by: @npub1q3s…d26p, @npub16ye…g4wn, @npub1ye5…knpr, @npub1sjc…jx9d, @npub18am…p424, Chad Curtis, Daniel
Source: https://gitlab.com/soapbox-pub/armada
2. Zapstore - 1.1.0
Zapstore is an open Android app store where developers can publish apps directly and communities can curate and discover them through a decentralized model. This release introduces portable encrypted device state with Amber backup support, background auto-updates, device-signed app catalog events, NIP-56 app reporting, diagnostic log exports, and improved app verification before installation. It also enhances offline-first releases, deep link handling, app data management, restore reliability, and update performance.
Contributed by: @npub1wf4…dgh9
Source: https://github.com/zapstore/zapstore/releases/tag/1.1.0
3. Earthly - v0.0.1
Earthly is a collaborative map editor built on Nostr that allows people to create, share, and enrich local knowledge maps using decentralized data. In v0.0.1, the first release introduced the Android app, NIP-50 geo search support, AI chat improvements, automatic icons, and article/context generation features. This was the biggest release of the week, and the latest was v0.0.2.
Contributed by: Schlaus Kwab
Source: https://github.com/zeSchlausKwab/earthly/releases/tag/v0.0.1
4. Alby Lightning Browser Extension - v3.14.5 (The Witch’s Broom Nebula)
Alby Lightning Browser Extension is a Bitcoin Lightning wallet extension that brings Lightning and Nostr integration to the web, acting as a wallet interface for multiple Lightning nodes and a signer for Nostr, Liquid, and on-chain Bitcoin applications. This release improved onboarding with Alby Hub, removed deprecated wallet connectors, updated swap flows, upgraded security dependencies, and migrated the cryptographic stack to newer versions.
Contributed by: @npub1e5t…7mh9, Pavan Joshi
Source: https://github.com/getAlby/lightning-browser-extension/releases/tag/v3.14.5
5. NosCall - v0.6.0
NosCall is a secure audio and video calling app built on the Nostr protocol for decentralized communication. In v0.6.0, the release introduced a built-in Cashu wallet with Lightning and ecash support, added relay-based push notifications using NIP-9A, migrated Android notifications to UnifiedPush, improved iOS VoIP support, and enhanced networking, app lifecycle, and call handling.
Contributed by: sana
Source: https://github.com/sanah9/noscall/releases/tag/v0.6.0-release
6. Vector - v0.4.1 (Pre-release)
Vector is a decentralized, censorship-resistant messaging platform built on Nostr, providing secure audio, video, and text communication without KYC or advertising. This pre-release introduced Concord v2 communities, Discord-style slash commands and bots, disappearing messages, privacy-focused notifications, image metadata controls, performance improvements, and numerous fixes for messaging, media handling, Tor, notifications, and synchronization. There was also the release v.0.4.0 last week.
Contributed by: @npub16ye…g4wn
Source: https://github.com/VectorPrivacy/Vector/releases/tag/v0.4.1
7. Nostrord - v2.3.0
Nostrord is a NIP-29-compatible Nostr client that provides community and group communication features on top of the Nostr protocol. In v2.3.0, the release added cross-platform user muting, improved NIP-29 moderation support, enhanced group invites and relay handling, added Tor relay support, improved account recovery and signer reliability, and introduced additional security protections for plain-key accounts.
Contributed by: @npub1f27…9swu
Source: https://github.com/nostrord/nostrord/releases/tag/v2.3.0
8. Nostr Mail Client - v0.14.2
Nostr Mail Client is a Flutter-based email client built on Nostr that enables users to send and receive encrypted emails through the Nostr protocol. In v0.14.2, the release fixed macOS sign-in issues and improved account storage reliability in signed release builds. This was the latest of the week, and there were also the releases of v0.14.1 & v0.14.0.
Contributed by: @npub1kg4…w5te
Source: https://github.com/nogringo/nostr-mail-client/releases/tag/v0.14.2
9. NoorNote - v1.2.8
NoorNote is a Nostr client for interacting with the decentralized social protocol, providing a user-friendly interface for browsing and engaging with Nostr content. This release improved Nostrord group notifications by preventing missed group posts on slow relays, added optional alerts for users’ own posts, and improved side-column navigation and tab management.
Contributed by: @npub175n…g6w0
Source: https://github.com/77elements/noornote/releases/tag/v1.2.8
10. Sidecar - v1.4.1
Sidecar is a NIP-07 Nostr signing extension that works inside your browser’s side panel, providing secure key management, event signing, and wallet connectivity while keeping private keys on the user’s device. In v1.4.1, the release improved auto-lock behavior, strengthened PIN security with better brute-force protection, expanded the built-in app directory, and refined the notification interface. This was the latest release and there was also the release of v1.4.0 last week.
Contributed by: @npub1aeh…4nwx
Source: https://github.com/dmnyc/sidecar/releases/tag/v1.4.1
#tools_nostr_recap
User base is irrelevant as far as I'm concerned. If we have enough people building and using the clients we have to communicate as we build, that's enough for now! We gotta make sure this shit works first.
Making it open would not have helped with interoperability, unfortunately. Jam was not designed for that, which both Nests and Corny Chat were based on.
It would have been good to fully open up, but it’s gone now. There was no attempts though to “lock it down”, and it remained compatible with the base Jam software.
The goal of the rewrite was to provide specifications anyone could implement to get their own fully compatible audio room. That got lost after the takeover, somehow.
I attribute the downfall more to Primal and fast-moving specs, more than “scrutinizing what is a true client”.
A protocol defines a contract that all implementations must follow.
If an implementation deviates from that, it is either a non‑compliant (bad) implementation or an entirely different protocol.
The “discretionary” aspect refers to enforcement: no external authority automatically guarantees compliance, so violations may go unchecked. When non‑compliance occurs, interoperability breaks
I appreciate your response but based off Jam’s license you shouldn’t have released the software without making the repo public to begin with.
It’s in the past now and no sense of crying over split milk.
The sad part is how it teared apart Nostr.
After Cornychat was released clients refused to integrate it because they didn’t want to offend Derk
In my opinion this is when interoperability on Nostr started going downhill.
The Nostrati began scrutinizing what constituted as a Nostr client with Fiat Gaf hand waving cornychat as “Not-a-client”.
Now that the Nostrati has abandoned Nostr and migrated over to X there is a chance for the surviving misfits of Nostr to regroup and try again.
yes, but how would you ever know? compliance is discretionary
AI told me to use NIP 17
what's wrong now?
who knew it would all be fake and gay
It's just what the spec says, its not trust, just compliance with the protocol. An implementation doing something different is just not implementing the protocol
It’s one of the if not the one features that is literally keeping the platform users coming back besides the porn you can watch no verification
Yeah not all nostriches speak dev gobblydegook
Just give them the apps they want lol fucking hell
thank you for caring enough to take the time to write all this. 👍
Pepperoni, Pineapple & Jalapeños on thin crust is peak pizza
It was more complex and weirder than that.
Derek started hosting Nostr Nests independently based on Jam software. They made some minor modifications early on, but got bigger.
With our existing work together on Nostr Plebs, I agreed to help.
With there UI leaving a lot to be desired, me, @npub1jdg…2mys and @npub1r0r…q9ac worked on a UI redesign. Most of the core remained the same, with mostly some UI changes.
I have been clear that Nests was based on Jam, and I have never tried to obscure that.
Anyway, at this point, it was decided that a complete rewrite, fully independent from Jam was a good idea.
There were too many issues with large rooms on Jam. Also, it was built with a different identity system than Nostr, which made it hard to integrate.
The main reason that we, together, decided to not make it open-contribution is due to the rewrite. It would be fully open source and open contribution, and more suited than that.
(Looking back, I’m not sure if that was a good choice or not. The code depended a lot on internal details to work.)
Anyway, I did not have the motivation to work on the rewrite due to burn-out and personal reasons. This was not helped by the fact that our informal agreement with Derek that it was a shared project fell through, of sorts.
Derek had made it clear that he treated it mostly as his own project including making unilateral decisions, and I felt like that was disrespectful to the work of me and others.
Around that point I left and took a break from Nostr.
I did not track what happened fully next, but I believe it was replaced by a rewrite by Kieran and then proceeded to become inactive.
——
If it was ever unclear that Nests was based on Jam, I apologize for that.
There was never a goal to gatekeep contributions, but more that it was simply not suitable for it due to it being designed with so many internal components.
The situation was more complex than this person was solely responsible about it”.
Even though I have mixed feelings about it, I will not share my personal interactions with Derek in depth out of respect for privacy.
i'm totally ignorant of nip 59, but:
"nip 59 says relays SHOULD only serve kind 1059 to the marked recipient"
establishes trusted relays. trust is a mistake that gets you burned
npub key distribution is a good start, consider adding a PET for enhanced privacy.
i definitely don’t want to get in the middle of a personal conflict. it seemed out of character, so wanted to clarify
Before the AI tools were good enough semisol forked jam systems, users had ideas and wanted to contribute but were gate kept, that’s the origin story of corny chat
So replies and notes are the same kind?
And 1111 is like a reply to a reply?
The mere fact y’all are still working through these Nostr matters tells me we’re on the right track. Never settling. 👊🏼
That's not it, but something like that, I remember it had letters instead of numbers.
This stuff is way beyond what I can understand to be honest
wait wait wait…
is this true?
did @npub18am…p424 use AI to vibe code nostr nests based on open source code, then after community grew shut it down rather than open source it?
if it is, we need to know.
