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!
Coming up: private and public follow lists
https://i.imgur.com/g74XHKY.mp4
Create them on listr.lol and use it on Amethyst.
Discussion
Have we settled the nip95 fiasco?
Nah. It's still a thing, many relays don't want it, at least one does, but we don't have to use NIP-94/95 if we don't want to use it.
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!
>
Interesting. It looks fine for me on Amethyst and Snort.
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.
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.