Oddbean new post about login | logout - different communities, different rules - Actually incentivizes action on reporting - instant boosting is actually less annoying, and encourages relevant rebroadcasting - specialized groups won't worry about vandalism or brigading in their communities.
I'd argue outbox is less important that segregated communities. nostr:nevent1qqsfzv43xveq6uxc9ce6q3q4ccdvl5rq4u7plnxrmkhztw49xrwde9gpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqpga9n9v
Honest question: why not just use mastadon then?
Because nostr is better. Mastodon's (and likely all centralized social media's) capability is a subset of nostr's capabilities, you can have any level of openeness you care for.
Makes sense. I would like to see more experimentation with topical/regional/community relays.
Multiple communties per relay is a mess especially private groups/communities. This is the simplest and most bang for your buck and doesn't need to be perfect. You can have hashtag feeds, why not feeds where you toggle what rooms you care to be in?
this probably explains it most nostr:nevent1qqs8m643lu9gtlacsal7ufuk8mgea4v95wj626v7625fekgw0yp3hyspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqpl2djqg
cc nostr:nprofile1qqsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3gprpmhxue69uhhwetvvdhk6efwdehhxarj9emkjmn9qyxhwumn8ghj7mn0wvhxcmmvqyg8wumn8ghj7mn0wd68ytnhd9hx2yhtlun nostr:nprofile1qqsw3znfr6vdnxrujezjrhlkqqjlvpcqx79ys7gcph9mkjjsy7zsgygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz8thwden5te0dehhxarj9ekh2arfdeuhwctvd3jhgtnrdakj7qgkwaehxw309ajkgetw9ehx7um5wghxcctwvshspg7dju nostr:nprofile1qqspz8vkaeknfpudjkhmlegtr7qwsyjk6anzw6u2ypx7x3sc2ftzgtspzamhxue69uhhyetvv9ujumn0wd68y6trdqhxgeg9t5nzw on ReasonTV. The interview that put nostr on the map for me and got me on. https://www.youtube.com/watch?v=pi2JbHWd_BM
And I'll continue shouting into the void nostr:nevent1qqsw5kef08rh94xkwljfrenw7gtznqwtvpsdgjthkfxccfjzpquckdgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqpgzpu6z because https://media1.tenor.com/m/eIxMdxL8G8AAAAAC/adam-neely.gif
💯 Until my face turns blue
Are you gonna skip around and sing la-la-lalalala like a Smurf? 😂
and thoughts on community security? Literally the only person who actually engages me on this topic is nostr:nprofile1qqsyeqqz27jc32pgf8gynqtu90d2mxztykj94k0kmttxu37nk3lrktcpz9mhxue69uhkummnw3ezumrpdejz7qg3waehxw309ahx7um5wgh8w6twv5hsz9mhwden5te0d4kx26m49ehx7um5wgcjucm0d5hspyest0 because he vehemently opposes a perspective I have but we gucci otherwise. nostr:nevent1qqsdynz4nvh6k62cexwjl5nwuf67xw5xmnr90utx2qnh6y8p8wp25fgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqpj2s0gu
i think echo chambers are bad. but what does this have to do with community security? what am i missing?
keeping people connected and not letting them get fragmented i'm still gonna keep liminal blocked and unfollowed until he understands there is nothing benign about the trans agenda tho
If you want to be an asshole be an asshole on your relay, but you can still be on my relay if you follow my rules. Specialized communities wont come to nostr if anyone can comment on their content because of the chance of vandalism. Nostr itself is an echo chamber and anyone veering from the average perspective is ganged up on disencentivizing others away. switch relays for specifc topics, or groups multiple relays together for different communities. Just like amethyst uses lists to follow hashtags you can do that for relays. Famous user posts, incoming reboost cascade. I get it, I already saw it five times. you can of course have any mix of relays you want and relays that have loose moderation tools thats perfectly fine and now boosting is less annoying if you're cross posting across communities. Reporting is actually actionable because it holds moderators/relay operators accountable for user behaviors because no one likes a community garden where anyone can shit there as they please. its not about "forcing" an echo chambers, its allowing a gradient level of openness.
This first paragraph sounds like Fediverse. Communitites and relays shouldn't be a 1:1 relationship. Probably a many:many.
Yes, and we should have it but our data shouldn't be beholden to any single relay operator as the fediverse has it.
i guess technically a relay could only allow reading and writing from authorized npubs or they could do heavy filtering to only show content from specific npubs. this is almost similar to what Ditto is doing with their community instances.
I argue that you get the most bang for your development time with relay selection and whitelisted relays.
I would agree here that relay management is key, but I also understand that most people don't want to configure their relays and find fine their experience. The masses just want it to work.
And that's fine, let the prebiotic soup be the starting point. You learn the landscape make frens and find where your tribes are, you can worry about how to configure your relays after, especially if you're following others who have already done it.
Essentially, yes. Some methods will work for some people and other different methods will work for others. As long as we have choices and more options for more technical users, but also don't forget about newbies, I think we'll be okay.
i think that creating a "free tier" scheme for reqs that ONLY include a specific npub that is a paid member is one element of making distributed relay data storage more practical another is that the relays need to have garbage collection, so only specialist archivists keep everything and lower the cost of most usage (and archivists can sell that acceses to paid relay operators so they can fetch it and cache it in their GC'd data stores) - and yes, also, my GC implementation is not selective about anything except frequency of access but more advanced GC mark configuration could include things like preferring to purge non-paid member events that have also old parent nodes to be cut off before cutting out the paid relay old events, and so on one of the things i want to do with my work on replicatr is making a "layer 2" event store that you configure with other relays that you share with, so they can distribute events horizontally to shard out storage for users outside of that, tools that let users know what relays are best for getting everyone on their follows both their events and them seeing them would be really useful as well
and thoughts on community security? Literally the only person who actually engages me on this topic is nostr:nprofile1qqsyeqqz27jc32pgf8gynqtu90d2mxztykj94k0kmttxu37nk3lrktcpz9mhxue69uhkummnw3ezumrpdejz7qg3waehxw309ahx7um5wgh8w6twv5hsz9mhwden5te0d4kx26m49ehx7um5wgcjucm0d5hspyest0 because he vehemently opposes a perspective I have but we gucci otherwise. nostr:nevent1qqsdynz4nvh6k62cexwjl5nwuf67xw5xmnr90utx2qnh6y8p8wp25fgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqpj2s0gu
i think echo chambers are bad. but what does this have to do with community security? what am i missing?
keeping people connected and not letting them get fragmented i'm still gonna keep liminal blocked and unfollowed until he understands there is nothing benign about the trans agenda tho
If you want to be an asshole be an asshole on your relay, but you can still be on my relay if you follow my rules. Specialized communities wont come to nostr if anyone can comment on their content because of the chance of vandalism. Nostr itself is an echo chamber and anyone veering from the average perspective is ganged up on disencentivizing others away. switch relays for specifc topics, or groups multiple relays together for different communities. Just like amethyst uses lists to follow hashtags you can do that for relays. Famous user posts, incoming reboost cascade. I get it, I already saw it five times. you can of course have any mix of relays you want and relays that have loose moderation tools thats perfectly fine and now boosting is less annoying if you're cross posting across communities. Reporting is actually actionable because it holds moderators/relay operators accountable for user behaviors because no one likes a community garden where anyone can shit there as they please. its not about "forcing" an echo chambers, its allowing a gradient level of openness.
This first paragraph sounds like Fediverse. Communitites and relays shouldn't be a 1:1 relationship. Probably a many:many.
Yes, and we should have it but our data shouldn't be beholden to any single relay operator as the fediverse has it.
i guess technically a relay could only allow reading and writing from authorized npubs or they could do heavy filtering to only show content from specific npubs. this is almost similar to what Ditto is doing with their community instances.
I argue that you get the most bang for your development time with relay selection and whitelisted relays.
I would agree here that relay management is key, but I also understand that most people don't want to configure their relays and find fine their experience. The masses just want it to work.
And that's fine, let the prebiotic soup be the starting point. You learn the landscape make frens and find where your tribes are, you can worry about how to configure your relays after, especially if you're following others who have already done it.
Essentially, yes. Some methods will work for some people and other different methods will work for others. As long as we have choices and more options for more technical users, but also don't forget about newbies, I think we'll be okay.
i think that creating a "free tier" scheme for reqs that ONLY include a specific npub that is a paid member is one element of making distributed relay data storage more practical another is that the relays need to have garbage collection, so only specialist archivists keep everything and lower the cost of most usage (and archivists can sell that acceses to paid relay operators so they can fetch it and cache it in their GC'd data stores) - and yes, also, my GC implementation is not selective about anything except frequency of access but more advanced GC mark configuration could include things like preferring to purge non-paid member events that have also old parent nodes to be cut off before cutting out the paid relay old events, and so on one of the things i want to do with my work on replicatr is making a "layer 2" event store that you configure with other relays that you share with, so they can distribute events horizontally to shard out storage for users outside of that, tools that let users know what relays are best for getting everyone on their follows both their events and them seeing them would be really useful as well
what I'm more saying is we need closed communities. yes decentralization, yes gossip/outbox etc. A melting pot is nice but we need closed communities to help encourage a focused & thematic discussion. Nostr groups are a mess and i argue the simplest implementation is select the relay(s) for a specific community you want to be in. Will UX be difficult? Maybe, but just like a feed where only posts with a single hashtag comes through, you can do the same for relays. Always optional. Like a faucet, you & the relays choose what level of openness you want. nostr:nevent1qqsqxhad2z4fqca22ljxvu24m2fdn250t475wd6ewlxfhwcshs65fpspr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqps48hmm
