Aha. Too many NIPS! Thank you.
BTW, should that have been :relay instead of :relays?
>From: aasaa<-DerekRoss at 05/05/23 07:56:24 on wss://relay.damus.io
>---------------
>It's described in NIP-19.
>
>Here's how Nuestr decodes it: https://github.com/alemmens/nuestr/blob/master/src/nuestr/nip19.clj
>
>For example:
>> (nuestr.nip19/decode "nevent1qqsx2qg9w9mxrffyuv32l7vewzvawlnfrerv5gqphkcd4rmqtz6qqxgpz9mhxue69uhkummnw3ezuamfdejj7q3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqqqqzqa58hn")
>["nevent"
> {:special "650105717661a524e322aff9997099d77e691e46ca2001bdb0da8f6058b40019",
> :relays ("wss://nostr.wine/"),
> :author "460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
> :kind 0N}]
I have no idea. Why not both? At very least you don't need an invitation to be on nostr.
>From: (tomas) at 05/05/23 08:44:08 on wss://offchain.pub
>---------------
>Why should I stick with Nostr and not with e.g. Bluesky?
What is your favorite Nostrich image?
I decoded it as a string (which is not strictly valid bech32 but...) and it gave me a bunch of garbage. Amidst that garbage, however, was 'wss://nostr.wine/'. So this is definitely not a bech32 representation of a 32 byte event id.
Here's what I see:
nevent1qqsx2qg9w9mxrffyuv32l7vewzvawlnfrerv5gqphkcd4rmqtz6qqxgpz9mhxue69uhkummnw3ezuamfdejj7q3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqqqqzqa58hn
Whatever this is it's too long to be a valid bech32 address that converts to a 32 byte id.
>From: DerekRoss at 05/04/23 20:23:04 on wss://atlas.nostr.land
>---------------
>Interesting. It looks fine for me on Amethyst and Snort.
Whatever that nevent1 bech32 thing down there is, it's not the id of a message. What is it?
>From: DerekRoss at 05/04/23 18:32:23 on wss://atlas.nostr.land
>---------------
>I have wanted lists since my beginning days of Nostr. I am very excited to have this feature on Amethyst. I guess it's time to start building my Lists out!
>
Oh, the woes of airplane ownership.
Thanks! I was in the air yesterday doing stalls, Lazy-8s, Steep Turns, and power-off 180s. Great day!
What is Nostr?
Have fun with it!
If you look in the `private` directory you'll find a file named `user-configuration`. In there you'll see some font configurations. You can play with those if you like.
I'll have to do some work on the cosmetics at some point. My current focus has been function over form.
>From: fiatjaf at 05/03/23 19:31:24 on wss://relay.damus.io
>---------------
>Well, after this video I felt an irresistible urge to try more-speech again after a long time. But unfortunately I remember why I stopped using it in the first place. It looks much better on the video than on my computer, it's hard to read even. I don't know what my computer is doing wrong, maybe Swing just doesn't like Linux:
...All of which leave me guessing as to how I find out who send me a zap...
Yeah, that's probably it. What is a 'preimage'. In the zap reciept (NIP-57) it's a 32 byte hex code.
Can I ask how you initially set up these trust links? More-speech was able to download them so I assume they're stored by relays? Congratulations on your appearance in nostr:npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnft's demo!
The people you trust are your contacts (kind 3). Other clients use your contacts as your "follow" list. More-speech uses contacts as 'trusted individuals'.
I love nostr, there are so many ways to use the protocol.
How can you tell who zapped you? The 'lnbc' invoice can be decoded but the pubkey within it is 65 bytes long... Wierd.
Correct. Unless, of course, you send a DM. DMs _are_ encrypted.
>From: (the_valley) at 05/03/23 17:17:00 on wss://relay.damus.io
>---------------
>yeah so nostr is not encrypted then. hehehe.
>From: unclebobmartin at 05/03/23 15:48:31 on wss://relay.nostrplebs.com
>---------------
>Thank you #[3]
Thank you @035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226