The intention has been clear from the start:
The word "verify" doesn't appear any time in the NIP-05 document:
"Login with nostr" plugins for common CMS and web frameworks.
Including recovering from nostr relays user metadata, PFP, contacts?, etc...
True.
Nostr login gives you authentication, identity with metadata (name, PFP), contacts, etc.
Much more than lightning login.
This guy is gonna make it.
https://twitter.com/bitcoinplebdev/status/1631334794398257152?s=61&t=pQ1OyTEAbdmDjdekQLQsHA
Not very good opsec, though.
Bragging like that with a picture of himself is not such a good idea, I reckon.
You trust his previous keypair because of his previous history and interaction in the network, not because of his NIP-05.
Exactly, NIP-05 should be considered as an alias, not as complete verification.
The identity relies in the keypair, not in the DNS domain.
He can sign with his old privkey a statement to verify his new keypair, as he has not lost control of the old key.
Much better than using NIP-05, as that needs trust in lots of systems (DNS hierarchy, webserver security, etc), imo.
There's no followers list in nostr, just follows list where your npub appears.
Apple's requirement to accept Damus in the Store.
He's recovering the old keypair publishing a new kind-0.
No need to change the json.
He's trying to recover the old keypair, not updating the NIP-05 alias to the new keypair.
Private payments already exist:
Private zaps are coming soon.
This 1.23 BTC bounty for a nostr Github replacement looks really yummy 😋:
https://bountsr.org/code/2023/01/19/nostr-based-github.html
Here's my plan:
1 - Propose a NIP introducing 3 new event kinds (repo, issue, PR). Each event has an eventID and has a "parent" field pointing to another event. The root event in the tree is the "repo" event kind.
2 - Fork gitea/gitlab
3 - Add a nostr client library that can talk to
4 - Remove all server side code that queries a centralized database
5 - Replace it with event queries
6 - Cache it so it is not super slow
7 - Replace user database with a nostr login
8 - Self host a demo client
9 - Claim bounty to #[0]
10 - profit?
Flawless plan 👍
Ok, thinking about this, I realised you meant DNS-free for the payment receiver, right?
- With LNURL over HTTPS it's necessary to build a webserver and have a domain registered.
- With LNURL over nostr it's not necessary to have any domain registered, as it works just listening for invoices requests in nostr relays.
Right??
I think many of us are thinking the same thing: why do we need to rely on centralized DNS authorities for LNURL when we can do it just with npubs and relays.
Amazing new proposal LNURL over nostr proposal:
https://github.com/lnurl/luds/pull/203
Which is something I had though about in the past:
#[0]
Nice idea, but nostr isn't DNS-free right now either.
Client-to-relay connection is (mainly) done relaying on DNS lookup.
Ok, tor & i2p exist, but I guess its use is very small rn.
Amethyst v0.22.0: One essay at a time
- Early Markdown Support
- Long-form Content (NIP-23) support
Download: https://github.com/vitorpamplona/amethyst/releases/download/v0.22.0/app-release-v0.22.0.apk
I hope the markdown is just for NIP-23 notes.
No markdown for kind-1 notes, please! 🙏
👍
That's a nice feature of NIP-23, editable posts.
It was just a suggestion, thank you anyway!
🫂
Very nice, thanks a lot!
Just as a suggestion: maybe some people could find useful some mention to how to configure wireguard in other computer OS (Windows, MacOS).
Just a mention of some available software, not a complete guide.
Anyway, nice guide and nice usage of nostr-blog!! 👏