Oddbean

Poor experience trying to onboard newbs to nostr during the conference (mostly on iOS which I do not use), around 10-12 people. Granted the cell coverage was not great and not sure I remember everything that went wrong, but users were generally confused with loading/lacking data. Create a profile, then I tried to follow them but could not find them from Amethyst. So scanned QR code, which is a non-obvious step. Then their profile showed just the npub but no info or pfp, some commented on that. Followed them but they didn't receive a notification for that on Damus, this confused most. And then what? Post a note? (I was recommending #introductions ). While you wait for all this to load, tap, retry... between laughs you need to come up with conversation and try to somewhat defend nostr, tell them we're early and bugs will be fixed etc. On Primal follows do appear but feeds don't load. And it autofollows a bunch of random people - some liked it some didn;t. They posted a note and I wanted to like/zap it but I could not see that note on my client either, even though I'm connected to major relays (could be nostr.wine's fault, but I tried with the zap.store account as well). I saw one guy KYC himself 3 times with the wallet because when he switched to his email client to get the code and the app kept resetting the screen. Lucky that the majority of people were eager and did their best to try. Since some of these were after Jordi's talk where he offered several clients to download, it was not always my choice/recommendation on which client to download - they just came with it. I know we do our best but guys... it's bad. This reminds me of getting a newb to open a LN channel and get liquidity. Painful. If we have to centralize more to better onramps, so be it. nostr:nevent1qvzqqqqqqypzq96n3hp2vfmf6z2y8uvvxl97xk86kkalnqghx4p25lzl79c76a7yqqsz3jeztxwv28ahksw070zcxs8e5xv25ttv07xq8tpaldczrqxsk9s2a5hg5

By far the most likely. NIP-01 should force clients to expose REQs through a regular HTTP endpoint (in addition to websockets) where to fall back on. I implemented that on relay.zap.store. 20 lines of code. But there's no interest? Or, what is another hypothesis for these data loading issues? nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3xamnwvaz7tmhda6zuat50phjummwv5hsx7c9z9 nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tch2deau nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3qamnwvaz7tmwdaehgu3wwa5kuegpp4mhxue69uhkummn9ekx7mqcu9929 nostr:nprofile1qqsdv8emcke7k3qqaldwv956tstu40ejg663gdsaayuuujs6pknw7jspp4mhxue69uhkummn9ekx7mqpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpzfmhxue69uhhqatjwpkx2urpvuhx2uc86mqq0 nostr:nevent1qqsfpq4xlqxgzt305w6lt267zm3vskju490f8sr7733utxcx66t3jfcprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0qgsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygrqsqqqqqpzjys8e

Sure the onboarding sucks. The initial setup sucks. Discovery sucks. Getting zaps to work sucks. Nostr sucks in a lot of ways. Yet there are a lot of people who are Nostr-only. There are a lot of people who are dedicated to building it out. It's growing at a pace that's mind-boggling. Maybe people should think about why that is when they're trying to participate in the network. In my experience, you get out of it as much as you put in.