Real Nostr clients don't require any servers, they can work completely on the client side. The fact that we have apps that still work perfectly well but are now inaccessible because a domain name has expired (or whatever) is some bullshit we inherited from the "web" world that we should try to circumvent, not embrace. There are multiple ways to circumvent these flaws and build true Nostr clients that can't be controlled by anyone, not even by their original author. View quoted note →

SQRL invented the anti-phishing public key cryptography based approach to website authentication many years ago. It was a beautiful spec of one page with multiple grassroots implementations. Then they decided that the simple "I sign something with a key" approach wasn't good enough, they also had to cover a bazillion other key management things in the protocol so they brought a team of academics that turned the thing into a 300-page unreadable spec that no one ever implemented fully. LNURL-auth basically reinvented the original simple SQRL version in 2019 and got many implementations and some traction within the bitcoiner realm. But at the same time another team of academics probably by paid by some evil people were creating Webauthn, i.e. "passkeys", which solves the exact same problem and works in the exact same way, although this time the spec is much bigger than even the worst version of SQRL and apparently designed to create centralization. It took them at least 6 years to get browsers and phones and some websites to start adopting this behemoth, but so far there are no answers to what is their real purpose or to the question: "what if I lose my phone?".

Added a "spell" command to

GitHub

GitHub - fiatjaf/nak: a command line tool for doing all things nostr

a command line tool for doing all things nostr. Contribute to fiatjaf/nak development by creating an account on GitHub.

- `nak req -k 777 -a verbiricha@habla.news --outbox | jq` to see all @verbiricha spells - pick one and run `nak req -i c1214b196b3664bc7fc8c8dfaa082a24ed09b25028773bcae60fef8dfe6646fa -a verbiricha@habla.news --outbox | nak spell --pub fiatjaf.com` to run it in the context of your user (replace 'fiatjaf.com' with your npub or nip05) - `nak spell` will list your previously used spells with ids that you can use to invoke them again: `nak spell spellcgk4u9c --pub fiatjaf.com` It's not super useful, but it is something. View quoted note →

#grimoire might make all the other clients obsolete. View quoted note →

Cellar Relay Readme | nostr.wine

Last Updated: November 21, 2023

is still great.

#pyramid has had some updates since the v1 release: - support for nip05 addresses on the same domain the relay is running; - more color customization, and fonts; - support for one-click updates, no command lines required; - /inbox relay support for filtered mentions and replies and NIP-17 DMs; - personal /u stats page for relay members; - global /stats page for the relay owner; - per user on-demand negentropy sync with other relays; - arm64 support on easy-install. download

GitHub

GitHub - fiatjaf/pyramid: a wondrous furnace of communityzenship backed by a dynamic ladder of socialhood

a wondrous furnace of communityzenship backed by a dynamic ladder of socialhood - fiatjaf/pyramid

join

chachi.chat

vibe with your tribe

#grimoire notifications on the left, a feed of pictures and video from people I follow (with outbox by default) on the center, a feed of a bunch of kinds from selected relays on the right. Oh, what, you can have multiple dashboards? Then this thing can do my NIP-29 chat rooms too.

grimoire - a nostr client for magicians

Instead of "protocol" we should call Nostr a "system".

Nostr Devtools: https://chromewebstore.google.com/detail/nostr-devtools/ogoaodeklpfbboeopebgdggammkcndcp Get clear insight of what relays are serving what subscriptions and what events came from where. Everything is filterable by arbitrary strings, groupable by relay, event, subscription or by any arbitrary Nostr filter elements (click on them, or Ctrl+click to add to existing). It only captures stuff while the devtools is open, so open it first then refresh the page to use, otherwise you'll get incomplete data.

How can we get Bluesky banned in Brazil now?

Can you see this note?