This talk is good: https://youtu.be/8pTEmbeENF4?t=748
This part (marked above) in which he talks about how "APIs" are crap is very enlightening. Unfortunately he doesn't say how we can get rid of APIs. But I think Nostr can and is solving at least part of the problem.
Interesting train of thoughts.
I see a potential conflict. While we have to be open for new ways of doing things, we also have to look at software development as a trade, that requires learning and mastering.
So, digging into the details and training ourselfes as much as possible but still be "open".
That sounds like becoming a master pianist and still looking for new musical instruments to learn.
Sending the registration code via a curated list of public relays makes the whole process super easy and super fast.
Register your #nostr address now on https://app.nip05.social
Did that years ago. It was hell on earth. Will never do it again.
New option to deliver the login validation code via a curated list of 13 public relays.
Ultra fast delivery. Now live on https://app.nip05.social

That sounds like a great idea and would have helped me get to know the LN features earlier.
Amethyst 0.50.6: Performance Improvements
- Adds a cache layer for citation parser in Notes
- Deprecates IMGUR uploads
- Fixes NWC with Auth
- Adds Immutable and Stable annotations to avoid recomposing
- Improves the speed of updating Notification notes
- Fixes click on the Home to update the feed
- Fixes size for the following symbol in chat
- Adds Better translations to `unfollow` in Portuguese
- Updates dependencies
- Moves zapping progress to a general IO update task
- Stops recomposing the drawer at every new route
- Adjusts bottom bar to not recalculate notifications after every recomposition.
- Moves default state of url previews to the remember function
- Remembering Background color and Text elements for posts
- Optimizes MultiSetCompose rendering
- Optimizes recomposition of bottom navigation items
- Optimizes NIP-05 procedures
- Optimizes Drawer for Recomposition
- Removes the time log for Composing a note
- Only updates the refreshing state if it was refreshing.
- Updates relay UI on messages sent by the logged-in user in the chat
- Migrates notification summary to a new day without having to restart
- Adds hashtags and #[n] rendering to markdown
- Adds `nostr:` prefix to channel id share.
Download:
- Play Edition with Push Notifications & Translations: https://github.com/vitorpamplona/amethyst/releases/download/v0.50.6/amethyst-googleplay-universal-v0.50.6.apk
- F-Droid Edition without Translations: https://github.com/vitorpamplona/amethyst/releases/download/v0.50.6/amethyst-fdroid-universal-v0.50.6.apk
Awesome. Thank you for your great work.
Azure functions cold start is bugging me ...
Interesting things you can find in the woods ...

Lightning address forwarding now available on "NIP05.social".
Get a #nostr address for free here: https://app.nip05.social
This is indeed a big problem, especially when Wikipedia holds untrue information (which it does for some topics).
💯
The initial release is the hardest part. Once that is done, it gets easier.
I have been reworking the UI and also added a stats view to "NIP05.social".
Lightning address forwarding coming next.
Get your #nostr address on nip05.social


Cool thing. That is also in my list 😀
These are my relays in Amethyst (defaults):


My proposal to use 'wss://nostr-pub.wellorder.net' was related to the login- and registration process on https://nip05.social where you need to enter a relay that the system uses to send your code to.
In your nostr client you of course also need to be connected to that relay in order to receive the message.
I am using Amethyst (on Android) as client. This client connects to 19 relays at the same time. The mentioned relay above is just one of them.
When I post something, it is automatically posted to all 19 relays.
And you are right. You must bei connected to at least one of These relays in order to receive my message.
It was indeed a bug in the system that prevented the delivery.
I have deployed a quick-fix that resolves the problem.
The delivery should usually only take 5-10 seconds. I personally use the following relay that always worked for me:
wss://nostr-pub.wellorder.net
Thank you for bringing this to my attention. I will Look into it.
This ist not acceptable.


