👨‍🍳 @Zap Cooking

I just realized that my life long opposition to platforms, their stupid accounts and walled garden silo bullshit, at its core comes from frustration. Being aware that alternative ways of doing/organizing would be fundamentally better and possible, just made me dislike the current paradigm from the start. I recon most people never had those a priori frustration, and as a result they/we now all experience the multitude of frustrations after the fact. ''We'' need to realize that ''we'' made the mistake in our behavior. ''We'' all went to had full of sites to sign up there, and ''We'' pretended that these corporate owned spaces were the public square, and ''We'' made ourselves dependent. I am not advocating for some collective action, the ''We'' is capitalized and in quotes for a reason, its just to point out that we ought to stop advocating for ''Them'' to change. Take the following clip. ''I don't know''... thats just it. Between captured network effects and alternatives being shitty, people feel lost and defeated. We are at the point that most if not every person is aware they dislike the current paradigm. They need to be convinced the alternative is here....for real this time. Nostr for me primarily is a relieve from the frustration i described. It made sense to me, so i accept all its (hopefully initial) quirks. Unfortunately, regardless of the dislike people have for legacy platforms, it seems they hate quirks more.

One quirk in Nostr, is that you are supposed to share npub or event ID and relay(hints) at the same time; this immediately tackles the vast majority of issues finding stuff. So when you reference someone, you don't use the npub, but the nprofile, that has relay hints encoded in it; when you reference a thing, you don't use the event ID but the nevent, that has relay hints encoded in it. But nprofile and nevent are not static things; you ''are'' still your npub. You can wonder to what extend the npub as such is of any use to anyone, at the very least at the foreground. All it means is that we somehow have to make clear to users that the string they share to others about themselves can be different from time to time, because it is both the ''ID''(/npub) and some possible locations. Or maybe most users will never care because clients just automate this stuff, i dunno. I think people can wrap their minds around npubs, but they are not all that usefull on their own.

Guys, we solved Nostr's adoption problem. Just get lots of babies. I hear @OpenSats is willing to fund the breeding program. View quoted note →

I see so many videos with commentary etc. about the various troublesome aspects of the current platform-centric web paradigm. And i'd love to make these people aware of Nostr, but there is seemingly no way to contact them without being on those platforms themselves... Hahahah the irony. We need a Morpheus who bothers to go into the matrix to purple pill all these Neo's. Not it!🙆‍♂

#asknostr How would one submit a talk about Nostr/Permissionless systems/TEPP for Oslo Freedom Forum? The madness surrounding ''online safety'' has been escalating.

This video is very good, watch it.

@jb55 listened to a podcast you did a few months ago, where you talked about leveraging follow-packs as an on-boarding method. I think in second instance, follow-packs are a great thing, but new users should start at curated relay feeds first, instead of curated follows; The user selects interests, so showing them stuff that aligns with those interests is indeed what you want; but whether the user actually wants to follow those people or not is a second thing altogether; and if it turns out they don't, they are forced to take some action. Whereas with relays feeds, they just pick another feed and are not attached to anything; the only action the user is ''forced'' to make is this learning moment that they can change perspectives. You could always offer associated follow-packs consisting out of the npubs the relayfeed is made out of. With a relay feeds you can curate on the event level, instead of getting all of what npubs publish. Also, these topic-(sub-)relays could be read only, scraping stuff from other places; users interacting with those events will do so using outbox anyway.