I like this but would leave out the "centralized control" phrasinf. Not sure how to word it but focus more on where we going rather than what we are escaping from
Censorship resistance is not a main selling point, would not prioritize it. Focus on the social graph portability with no permission (even tho we know they are essentially the same thing)
I would not focus immediately on the negative. State how awesome nostr is
Then below use questions such as "have you ever had x/ig/tiktok removed a comment you made?" (Or any similar questions any normie can relate to)...and then present the nostr solution more fleshed out
I don't use Windows but heard similar stories, unfortunately, and it's not exclusive to Rust
In one way or another, I will fix this with nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0
I understand the 1 btc = 1 btc meme but isn't it a bit hypocritical?
Isn't it conveying the idea that the price does not matter?
I find it hard to believe a significant increase in purchasing power for someone's goods and services makes no difference
Why do we connect/publish to so many relays?
It seems like an absolute waste of bandwidth, storage, processing when probably no one here is being censored.
Not a good tradeoff in my view: it directly leads to worse UX, which directly leads to less adoption.
#asknostr
Why 3-5? I'm arguing for one relay per user, and probably out of a set of popular ones. When you aggregate relays in an outbox model, you want to connect to as few as possible. The more relays the worse UX. This is how we lose.
An interesting alternative is to have relays that work as aggregators like filter.nostr.wine
True but I still don't see how connecting to a ton of smaller relays from a client will result in user experience matching/exceeding centralized services. My hunch is this will have to be solved server side and with trust
Partially true. Life is more nuanced.
Low self esteem can manifest in different ways, and talking is essential in the thinking process. Why do you think we value free speech so much?
So many times we hide low self esteem by "doing" things as a way of escaping instead of facing the fears right on. For that you need to understand patterns of the mind, your self and your shadow.
So the actual good advice is: yes, totally go do things in the physical world *and* consider talking to a good therapist.
nostr:note1g8qcyz7s7765n0cxr6kt4cucmul2de7zmc55mc8r7g7wvtdk28esr0mtme
Kenya is the one wanting to kyc every imei entering the country, and went full dictatorial during the covid vaccine days. Some real lunatics in power over there
La pase genial pero baja calidad de gente (lleno de cripto bros, haciendo colas para el sorteo de boludeces), ruidoso, y pesimas opciones de comida aun en el vip
Nostr booth fue lo mejor, y 4-5 charlas buenas
Prolific nostriches losing follows still an unsolved problem.
Big brain devs, could we use NIP-03 to help with this?
@elsat
nostr:nevent1qvzqqqqqqypzqgxjnqgddf0e9vz94hszawadeypk6aquc6rtqpq4cs45ydh7ftf0qqspjmjmhjxkzkpnwzt0vsfe4ezdfx88600u74z3gkc28rack2tn7hgdggku6
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
Totalmente. La estamos cagando fuerte en algun lado y no se que es.
nostr:nevent1qqsdfhmtmq6g57zh6ep5chk6g7jf4ewu7wfy2xrtntvanwulpcskcecpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygpq62vpp449ly4sgkk7qt4m4hysxmt5rnrgdvqyzhzzks3kle9d9upsgqqqqqqsz46u62
Damn, good catch. Thanks man. The name is confusing nostr:nprofile1qqsrmpp2lmx4u2fl9zmxy7fnwp9rlwxwz5a2j8tep2c376n494z2gtgpzamhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuegpzamhxue69uhkxetvd3shytnwdaehgu3wwa5kuegpzpmhxue69uhkummnw3ezuamfdejsz4sum5
But what I will say, if I couldn't get this right: not a chance in a million a normie will.
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
Totalmente. La estamos cagando fuerte en algun lado y no se que es.
nostr:nevent1qqsdfhmtmq6g57zh6ep5chk6g7jf4ewu7wfy2xrtntvanwulpcskcecpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygpq62vpp449ly4sgkk7qt4m4hysxmt5rnrgdvqyzhzzks3kle9d9upsgqqqqqqsz46u62
On the topic of painful nostr: nostrudel is impossible to use with a single paid nostr.wine relay. It constantly loses the auth and it's not easy to reconnect.
Recommendations for open source MacOS clients that work well with auth? (desktop or web)
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
Agree it might be useful to build on top of Material, it can be bent to be lots of things and likely best underlying support.
Here's an example of another design system: https://github.com/serverpod/stockholm
Sure! I'll add it.
Unless nostr:nprofile1qqs9500z3l7sn46sdnls5fnjm0d3lqmrq7707qshes2y7j8pnm4rllcprpmhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0jrvsqn would like to sign the release with their own nsec? 👀
Oddbean new post about login | logout
Notes by franzap | export