Social media has never worked, and will never serve people, ever. But there's a better way.
Social media was bootstrapped from communities, and then bastardized them to sell people off to advertisers.
The embrace -> extend -> extinguish paradigm that feeds on distrust and discord.
I am increasingly astonished that freedom-minded people ever thought that this distorted view of society can be tweaked to suddenly become useful. Reminds me of communists trying for ever to make their central planning "paradise on earth" a reality. Well, I guess that deep envy and resentment covered with moral camouflage will never go away either. It is highly attractive to the leeches of society.
It's time to wake up. And time to invest in communities. Nostr can really shine if it can let go of the dopamine-fueled NGU vision of social media.
You want to get closer to how people actually form successful relationships? They create families. Big families that form the root of trust. They extend it with friends, and they further extend the circle with communities forming around common interests and goals.
Nostr can make these communities compatible with each other, with less lock-in, better discovery and more flourishing than any other model we have had so far.
Just enough technological enhancement, with people's real interests in mind. No other way.
Replies (8)
The single Global feed is not the way.
That's not really what I do on Nostr, but I agree with your approach.
I have been thinking about outbox model since this pod.
I came to the conclusion that outbox model also only works in the context of communities. End-users don't care about servers, community leaders do. Users care about the community they joined. Big difference.
Also, for communities, discoverability matters. Their leaders are ready to pay for services to create a better place for their members.
Outbox model falls apart if it's done on the user-level. Will never work. But it _will_ in the context of communities.
It's a scalable and sustainable model for nostr.
you are describing the Communikeys proposal
https://wikistr.com/nip-communikey*a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be
https://github.com/nostr-protocol/nips/pull/1823
I think this is a phase where the problem is that for the community there are more protocols than developers who are working on the same protocol implementation
Yes, this is the closest conceptually.
I have been aware of #communikeys and want to see it happen.
And you are right, there are a lot of specs and it's confusing but the exploration phase is naturally like that.
Hope to ossify around sth like communikeys, and I am leaning towards sth like this implemented for #Budabit in due time.
Budabit actually doesn't fully use nip29 yet, we never migrated along with #Flotilla .
- Flotilla left the channels/rooms concept behind, something I value because it helps frame chat discussions. Note that this is not supported by communikeys either.
- Communikeys has badges to whitelist content types but I may need richer moderation methods, like in nip29.
Right now for Budabit I want to make a decent social experience with advanced Git features happen, so it can be lucrative for open-source communities to join. Unique utility comes first. Flotilla has most things implemented nicely. It's enough for now.
After onboarding some communities and getting feedback, we will tend to the social features again, and re-evaluate the specs.
Yes, the protocol also follows the type of community that the client follows, but if it changes from the same Nip Protocol is easier. Will you also integrate Satshoot in the Gitchat? Or in Communikeys because in some way he follows outbox. Everything becomes complicated even just saying it
Yes it is natural to merge markets with communities (I built a PoC Jobs tab in Flotilla but disabled it for now), it is not very clear to me how it's done best.
Can integrate communities as the primary sources of trust for freelancers and clients on SatShoot, once some communities are online.
I can render Jobs/Services in BudaBit then, and link this content type to SatShoot.
That seems like a good start to me.
