Price's law states that half your output will be generated by the square root of your total workers. I follow 40 accounts. I would expect half the notes in my feed to come from 6 accounts. Instead 70% are from 1 account. Do I need to encourage everyone else to post more or does nostr:npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jl need an intervention?

I kid of course, she does have interesting things to say, but it makes me reflect on how I post. I generally only respond. It isn't because I don't think about things, I do constantly, but it never crosses my mind to post what I am thinking unless it is already a topic of discussion.

I am grateful for accounts that break the ice on topics that I have thought deeply on but never considered sharing unprompted. How do people make the decision what to impose on their followers? Presumably people follow me to hear what I have to say, but I rarely consider my take worthy of the cold open of a top-level note.

Reply to this note

Please Login to reply.

Discussion

10% of users post 92% of tweets.

I am one of the most prolific accounts on here, since I do project docs and technical discussions with Nostr, too, and I'm working on like 5 projects.

Most devs are still on legacy systems like Slack or GitHub, and just show up here to post announcements and collect some zaps. Or they're Lone Wolves.

You might want to mute the word "Nostr" and then I'll show up less. Or just follow people who post stuff.

It isn't a complaint. It is an observation. Before you it was nostr:npub1cmmswlckn82se7f2jeftl6ll4szlc6zzh8hrjyyfm9vm3t2afr7svqlr6f but he has simmered down a bit.

I'm following like 500 people. Maybe you should try an algo, or something, to get more posts. Or maybe livelier relays. 🤷‍♀️

I'll get there. I am growing it organically. If I see someone making interesting replies I'll check their feed to see if their own notes are also interesting then add. Or I look through other people's follow lists to find a couple to add. I am trying to keep it high quality. Hard to go wrong mostly following people who work on active projects.

I wonder what pushes it away from Price's law. Do forums have similar ratios?

No.

Are we nostr_bb yet? Most online communication has siloed into Twitter like, Slack like, or Reddit like. But the OG forums and irc models are still super useful bookend of the spectrum.

Nostr is going to cover the entire spectrum.

I'm going to be mostly wiki, articles, projects, and forums, I think.

I find the Twittery stuff increasingly tedious.

really threaded chats can be remodeled as instant messaging with infinite threads too, it's really a model

i was just talking now with a friend who had the idea of turning conversations into like chatrooms, and how to go about nudging users towards this model, i think it's a cool idea, actually, probably just needs to be a tag that you attach that is based on the original and another tag that declares the nickname of the channel

I waffle back and forth on whether they should be network wide topic tag based or instance based where the initial message declares the relay used and everything after is just signed webrtc. The first is more resilient and open but suffers from confusing coherence. "Who are you talking to?!"

Yeah, sorta random.

We probably need to try both. There are lots of decisions to make on what your client displays in order to rectify the appearance of shouting into the void whenever someone you are talking to also talks to someone on a relay you aren't polling. Do that third parties previous posts get retro-actively added to your view of the thread messing up your history? Do your friends replies to accounts you don't see get hidden so you don't get confused? How does the client know who they are replying to anyway? AI classifier?

If you have instancing on one relay is there moderation? If not how do you handle spam?

Man I wish I had more time to code.

well, you can start by studying consensus algorithms and the tradeoffs they require

nostr is not a consensus, it is just a way to spew data around

nostr tries to move that "how to replicate" question to another layer, be it the client or a second level of infrastructure