gotta be able to say when ur being a lil stupid!! amen

Pubky seems to fix this issue with PKARR but please correct me if I'm wrong :msn-nerd-smile:

yeah y'all got your architecture Down. the more i think about it the more i realize how many good decisions were made lol keep up the great work

Sure, but doesn't the client need to know which relay your NIP-65 data is on to even do that in the first place? Yeah you could manually type that in, but that just feels like bad UX, and also limits what new users and normies would be able to do and find. If we had DHT, wouldn't this indexing problem be fixed? Also how many clients actually do utilize outbox?

I mean so many apps on here already Do rely on a global state. Unless your client pulls from a huge predefined relay, you won't see a lot of data or know where to look for user information if they start using your client. You Could provide a list of relays you prefer, but who's spending the time to do that? Also, things can exist in community contexts still, it just means that client might not rely on the DHT. You're right that in many cases, it would disincentivize Outbox model stuff, but that implementation is up to clients, and I think DHT would probably be used for querying global stuff and posting stuff and whatnot would use your specified relays. I think DHT would be a great approach for this, it doesn't take away that you use certain relays for whatever purpose, just makes information and account indexing a lot easier and prevents centralization on a relay level. Let me know your thoughts :)

Using your nostrlib Go library and I believe I ran into a bug. Using pool.FetchManyNotifyClosed(), the events channel does not transmit any data, the connection is closed before it can get any events, even though the connection to the relay is successful. This issue is not present in pool.FetchMany() and I am able to receive events no problem. Please let me know your thoughts!

its super fast and pretty easy to get the hang of! I'm a big fan so far!

welp there 100% does need to be a successor to nostr. building an app with it has made me realize just How centralized it really is. Don't get me wrong, I Love Nostr. This place has taught me so much in the short time I have been here and has opened my eyes to a whole new world. But I can also acknowledge that the architecture has some inherent problems and I would love to see something more p2p and censorship resistant. I think my ideal sorta thing looks like Bitsocial + Pubky. I like your idea with the social indexing too!

what about erlang makes it the best language ever? what do you enjoy about it over modern languages?

Pubky over Reticulum would be so incredible to see :trillian-eek:

what are your fav programming languages? I am learning Go rn! :skype_giggling:

many signers have granular permissions! I think that is crucial for using apps in the nostr ecosystem without having to worry that a malicious app now has your nsec.

he's spitting facts lowkey 😭😭