humanity is about to be ddos'd by a flood of ai generated engagement baiting slop
the only real mitigation will be cryptographically verifiable reputations and webs of trust
https://blossom.primal.net/d0840c002715b2c0ceaafce0756fbf5301b5d5ad193bbfa27a88140acf048a19.mp4
We also need human verification. I have a scheme planned for it with some friends and we'll build a prototype for it, for Nostr of course. If we can't build a proper human Web of Trust, we will loose.
"Do not make any changes, until have you 95% confidence that you know what to build ask me follow up questions until you have that confidence"
Thanks, guess what? When I run locally, it works.
One minor complaint: It asks for pubkey twice on login, other than that it's good!
Summer is here! ☀️😎
Doesn't work still, is the code available somewhere so I could test and fix?
As you see here, the window.nostr provider is registered and available in console:

I made a little tool to publish a nip-65 relay list for you, the outbox style: https://npub.dev/
I think a lot of people onboarded before outbox was a thing and various clients implement this functionality, some do not. so why not a tiny app?
please let me know if you see any issues with it.
"NIP-07 compatible extension not found."
I'm using Blockcore Wallet, it works with all Nostr apps, but your app gives me this message.
Love this quote:
"For Nostr to remain truly decentralized, we need to know where to find each other's notes. Without proper relay distribution, we risk creating just a few super-node relays where everyone goes, defeating the purpose of a distributed network."
It is such a joy being on Nostr! No other social media comes close, the best content available! 😍
Implemented the prototype for Feeds in Nostria, it's pretty neat! Needs a lot more work, but I wanted to share it with you now anyway. Hopefully very useful for us with wide screens.
Enjoy!
Latency is also something to consider, so that a user can choose relays that are geographically close.
Proximity to relay servers is important for quality of experience. Did a little test with the nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsqgx3h5enxdenmnzpru8w3yan3wzj9lqdugnllazemxgyfnkeue2crvh0ug2k Find app with a few selected relays to see.

Thanks for you feedback, much appreciated. I'm not a sales guy so if it gives ICO vibes it's just an effect of that.
The main principle is to ensure user's are distributed more evenly across many relays and that it becomes possible to discover them no matter where they host their events.
Step one is building a new Nostr app that builds on these ideas and ensures everyone can be discovered, even if you don't post any content to the current large and popular relays.
Second step is ensuring that there are reliable pool of user relays available and that the app itself picks from the available pool in a manner that ensures good distribution and when load is high on a relay.
Kind of like World of Warcraft, where you could see if a server was massively populated or not and could choose a less popular one. This must be automated and seamless for most users to get large scale adoption.
Perhaps I could have spiced up the offers a bit for early investors, just don't want to promise too much. Goal now is to complete an MVP within the next 3 months and demonstrate that the concept is viable, that we can help Nostr scale and increase user adoption.
Got a good foundation already to build on and I have high hopes it will work out great. Thanks!
nostr:npub1zl3g38a6qypp6py2z07shggg45cu8qex992xpss7d8zrl28mu52s4cjajh can you kindly create a RFC / proposed best practice in https://github.com/nostrability/nostrability/issues for this?
I see you did already? Thank you ❤️
Here is a demonstration of the issue with profiles (metadata) not being accessible on the User Relays. I hope all clients, like Primal, Damus and others will begin to always publish Relay List and Profile to all relays whenever the user modifies either their profile or their relay lists. If that happens, everything will be working better for everyone.
Doing a "high-performance" decentralized lookup of hundreds of Nostr profiles is very, very hard to do.
Many lack Relay Lists, many have massive amount of relays, many don't have their profiles published on all their relays.
Many keep stale and dead relays in their lists.
It becomes impossible to ensure a very good experience, it will be an best-effort and sometimes fail the first attempts.
Hopefully as people user Nostr more and Nostr clients helps users maintain their Relay lists, this will improve in the future.
Here is one way to improve in Nostr clients: Make sure that your client broadcasts Relay List/Following List/Metadata whenever the user modifies their relays. Ensuring that any Nostr clients can pick a smaller set of relays when they attempt to retrieve that important data for the health of the network.

Yes, they get some benefits mentioned here, and it's a SAFE agreement so they get discount on the Seed Round later this year: https://www.nostria.app/funding
How is this not simply solved by having Nostr clients refresh when they receive an updated kind 3? Nostr clients should keep an subscription open to the current user's relays to receive updated metadata (profile) and following list (kind 3) and relay list (kind 10002).
If any of those are received, simply update locally. Should not merge, should replace. Nostria keeps the original event itself, but if a client parse the content and store in a normalized structure, they should still remove/add when such an event is received.
Then in theory, following lists shouldn't be replaced by older ones, only if a device is offline, you edit your list and it publishes a new list when it comes online. That could also be solved by clients, by ensuring to first retrieve latest following list before publishing offline-generated events.
Right? Or am I not seeing the problem here? I understand that there has been issues, but the problem in my opinion, is clients, not the protocol. I truly believe another event kind is not the right solution to clients implementing existing protocol in a "problematic" manner.
(Yes, I know kind 3 has been renamed "contact list" and not following list, but I've always used that name).
It's not caused by something else? Sometimes if the server (in general, not specifically cashu mint) has other issues, the browser might report it was CORS issues, while the underlaying error is a server issue.
The apps will pick them for you based upon your proximity (latency) to them. Ensuring you're not going half way across the globe.
Can of course be manually edited, but automated for most users.
I'll show her we can make Nostr approachable by everyone. Even my mom.

