Vitor, are you planning on using NIP-65 to publish the user relay list?
NIP-65 > NIP-05 relays publishing.
Because with NIP-05 you trust the domain/web operator to set the relays, as you already stated.
Amethyst v0.17.0: Long live Amethyst
Several improvements to memory use to avoid OutOfMemmory crashes.
- Filters out the duplicated-message type of Spam
- Fixes Reply not showing up in the Thread View after the user posts a new note
- Adds Reports Tab to Profile Page
- Separates Notes from Replies in the Profile Page
- Significantly improves the speed of the Follower calculation
- Decreased User/Note object size -> 4x more objects can fit in memory.
- Prunes memory to 1000 messages per public channel
- Improves the speed of rendering long threads and thread-level calculation
- Fixes Quoted Post appearing as a Reply
- Fixes Mutex state when Android kills threads.
- Refactors current filter classes into Relay filters and Screen filters
- Moves Notification Dot calculation to background threads.
- Loads new Posts on the Thread view on the fly
Download: https://github.com/vitorpamplona/amethyst/releases/download/v0.17.0/app-release-v0.17.0.apk
It's working much smoothly, thanks Vitor!
π
Btw, I'm having problems with my profile picture and banner since previous version, I reckon it could be related with the image proxy.
I'm seeing them ok on other web clients but
I'm not able to see them on Amethyst.
What could this be about?

Mmmm... not working yet from Amethyst.
I'm seeing you have updated your profile a few minutes ago, but no Lightning Address yet, but a Lightning invoice?

They could at least verify signatures on some events, i.e. kind-0, 3, 4 & 65.
It's not as crucial to verify reactions (kind 7) as it is to verify metadata (kind 0) to get someone Lightning Address, for example.
π
We'll see how it goes, but I think it's a missed opportunity to have have been named something like Voight-Kampff Test.
π
Ok, but actually Bitcoin doesn't care about motivations.
Paid relays allow unauthenticated connection for read operations.
They will only require authentication for write operation.
The idea could be to allow writes without authentication if the note to be written is a zap-note referencing a paying subscriber.
I don't know how adding this policy could affect websockets connections management.
Oh yes!
What about accepting zap-notes from not registered pubkeys (zappers) but referring to registered pubkeys?
Those relays could have a policy to allow publishing of zap-notes that mention registered pubkeys, for example.
cc. #[2] : thoughts on implementing some policy like this one?
Zaps are like any other reaction in #nostr: they could be easily faked.
The signal is not in the quantity but on the quality: it's not 'how many' but 'who' react to a post.
I reckon Web of Trust (kind of) is where is going to reside the signal. What are your follows doing. Nobody can faked your follow list. Just you.
The rest is noise.
You can try a mobile app, if you want:
- Damus on iOS
- Amethyst on Android
Mmmm.
I think #[12] from Stacker News is fixing some issue with zaps publication. So, maybe better to wait for his confirmation that everything is working or we have to wait some time.
π


