aftermath on Nostr: pkt strike jack mallers <start> Hello World! Here is a quick example on how to get ...

pkt (npub1ej4…ndrm) strike (npub1ex7…vyt9) jack mallers (npub1cn4…3vle)

<start>
Hello World!

Here is a quick example on how to get the verified flag on nostr.

We will use Peter Todd's profile which is currently missing the flag.
Keep everything as it is.

Just add following static text file under /.well-known directory
in you webroot serving petertodd.org: nostr.json

The file contents follow:

```json
{
"names": {
"petertodd": "ccaa58e37c99c85bc5e754028a718bd46485e5d3cb3345691ecab83c755d48cc"
}
}
```

This hex I got from your npub by using nak:

```
$ ./nak-v0.7.6-linux-amd64 decode pkt (npub1ej4…ndrm)
{
"pubkey": "ccaa58e37c99c85bc5e754028a718bd46485e5d3cb3345691ecab83c755d48cc"
}
```

Verify by opening https://petertodd.org/.well-known/nostr.json where the
file is preferably served with `content-type: application/json`

Maybe even `content-type: application/json; charset=UTF-8` if you expect
international characters…

Another thing would be if you want to serve that file for more users.
I do static files with Caddy2 webserver, and `nostr.json?name=hello`
gets rewritten (internally, the user still gets the same file) to
`nostr.json-name=hello`

Try it:

https://anyone.eu.org/.well-known/nostr.json?name=justsmile

https://strike.me/.well-known/nostr.json

https://anyone.eu.org/.well-known/nostr.json?name=strike

(shout out to @strike)

In Caddy2 it looks like this

```
...
@question_mark {
expression {uri}.contains('?')
}
@jsonfiles {
path /.well-known/*
}
header @jsonfiles {
Content-Type "application/json; charset=UTF-8"
}
rewrite @question_mark {path}-{query}
...
```

Yet another thing is the LN address. I do `justsmile@anyone.eu.org`
also as a LN address but it calls back to Strike and the sats are sent
there. By the way such hard wall between nostr and real sats works
for me as I can easily zap on nostr by scanning the QR of BOLT-11
invoice and paying it from Strike app.

See https://stacker.news/.well-known/lnurlp/petertodd

Compare https://strike.me/.well-known/lnurlp/carnhofdaki
and https://strike.me/.well-known/lnurlp/carnhofdaki
The latter is a static text file. The `nostrPubkey` does
not seem to be doing much here, but I have changed it to
match the one I use currently on nostr.
<end>

See this at https://anyone.eu.org/ws/863242-191a75.txt where you can find everything between the start and end tags. The SHA256 checksum of that text is XOR-red with the block's 863242 checksum. But let's leave that for further curiosity.

Hoping this is helpful to someone!