I'd argue outbox is less important that segregated communities.
nostr:nevent1qqsfzv43xveq6uxc9ce6q3q4ccdvl5rq4u7plnxrmkhztw49xrwde9gpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqpga9n9v
- 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.
And I'll continue shouting into the void
nostr:nevent1qqsw5kef08rh94xkwljfrenw7gtznqwtvpsdgjthkfxccfjzpquckdgpr4mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmp0qgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqqqqpgzpu6z
because
https://media1.tenor.com/m/eIxMdxL8G8AAAAAC/adam-neely.gif
i understand we're never going to align on the perspective of transgender. I still respect your desire to isolate yourself from that conversation. Isolated communities should at least keep it away from your life. If you don't encounter that content you wont be mad about it and i wont have to observe it.
if i am confused, let me be confused away from you. Beyond that, conversation i can still have respect and converse with you. But this is veering away from the topic at hand.
Give me better relay selection to isolate my communities from each other. Reporting exists but are essentually useless mechanistically.
Moderation comes free. Now operators are incentivized to take care of who is on their relay because their community is telling them that some asshole shit in their garden.
Seems like the simplest solution. Sure we can have multiple groups on a relay, but we've clearly seen what a mess it is. Solve the easiest problem first. Incentivizing focused communities that care to be isolated will come here because they don't have to worry about vandalism.
Hence why we publish to wikifreedia, for fast, permissionless feedback. anyone can use it, they can make suggestions and we may not honor it, but they are welcome to use their version. Problems with interoperability? Negotiate on a better spec. Let the best specs win.
nostr:nevent1qqst9sqf7ugmjc9zvmqg5pw5qzfq96jf8kq2w2fexmwygmstx3559fcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7q3qm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqxpqqqqqqz20zqaw
It is inevitable. Embrace it.
nostr:nevent1qqswszxz7tcj2e0hh70tjd58plum89cd753q0vs2gszetc5v72t0p6spzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyrwye5yxe47wtvvr9t05lhgjzy5f3qxjcl3ft09su6zvqxkwua7qvqcyqqqqqqg4g55tt
The entire reason is decentralized, permissionless, censorship resistant speech. Code and specs are speech. You can have any subset of interop that you care. The empty set is still a subset.
nostr:nprofile1qqsd6ejdteqpvse63ntf7qz6u9yqspp4z7ymt8094urzwm0x2ceaxxgprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qguwaehxw309a6xsetrd96xzer9dshxummnw3erztnrdakj7qgcwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tcn2pqw8 nostr:nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpzemhxue69uhkwun9v4h8xmm4dsh8xurpvdjj7qgswaehxw309ahx7um5wghx6mmd9uq35amnwvaz7tmwdaehgu3ww35x2umpd4jkxct59e5k7tckquc5r might be something to consider for nkbip-01, any potential incompatabilities?
Nostr is decentralized and there is no mechanism to force compatability. What matters most is compatability between relays and clients that share functionality. If there isn't a shared functionality - go ahead and make lists kind 1 and notes 30023 because its not bugging anyone, just don't expect anyone to work with you on your island.
NIPs repository stands as protocol level standards to ensure interoperability at a base level. This isn't a proposal for a standard at a base level, and so doesn't need to be submitted, let alone asked for permission to be a part of a core set of specs.
Also, me not being a native web developer - what business do I have submitting a proposal for some functionality that is difficult to convey? I'm not wasting core nostr dev's time asking to be merged. If it is useful, implement it. If it is useful but brings incompatability - tell me to change it or fork it. Any worries for interoperability will converge on a shared standard if there is a need for shared functionality between clients, i don't even need to agree with it.
I'll reiterate, its not a core standard. Its is a descriptive spec for knowledge bases on top of nostr, who is using that right now other that our group? No one, therefore we don't need to worry about new standards.
effective navigation on a knowledge base is entirely dependent on the domain it is a part of.
A biology knowledge base is not going to have the same labels and tags as a literature, coding or writing knowledge base, and that's perfectly fine. So long as they are internally consistent with their users, they can exist as their own island. Now if your biology KB users and someone else's physics KB users want to collaborate but there are incompatabilities, the users will tell the developers to figure something out. If the developers are stubborn and don't want to change, they'll move to another client that actually works. Its not a claim for universal compatability.
Also, never made the claim that my spec is correct or cannonical. if its shit i want to know and nostr's functionality provides the fastest way to get feedback from those more experienced without permission. If a NKB really is that important, go ahead and submit it to the core nips repository, that's just not my priority. I don't really care who finds the "correct spec" i just want it to exist.
Sure, and if it's shit no one will work with it aside from those that don't think its shit however retarded you think they may be. No need to be in the nips repository. Make the spec, get scrutinized and learn for yourself.
Only if shared functionality is expected between clients that share the same relays. If it is expected, go ahead and debate it and come to a shared agreement on best practices.
right know kind 30040 and 30041 exist on 2 relays for experimentation. No major client uses it. If there is incompatibility, tell me and maybe I'll change it, maybe not if I'm stuborn. In any case, I'm fine having my knowledge base client connected to my knowledge base relay where we follow all the typical NIPs with the exception of whatever specifications we use that are unique to our client.
Also community. A stronger community ideally places constraints on bad actors in the community before the state gets involved. Without community self regulation, more things fester in the dark.
To speak to your point nostr:nprofile1qqs8qy3p9qnnhhq847d7wujl5hztcr7pg6rxhmpc63pkphztcmxp3wgpzemhxue69uhkwun9v4h8xmm4dsh8xurpvdjj7qgswaehxw309ahx7um5wghx6mmd9uq35amnwvaz7tmwdaehgu3ww35x2umpd4jkxct59e5k7tckquc5r, its constraints everywhere. Just because the mouse dopamine button exists doesn't mean that it is always right.
Meaning is collective at all scales, its not just about the individual. Our microbiome influences our mood, signals us through cravings of what to eat to help our gut biota continue to persist - biota that thrives on sugar will tell us to eat sugar but as a collective organism can choose against that and fix our diet, just as a society can put constraints on an individual who finds meaning from kicking puppies.
The key here is signaling+ communication across multiple scales; a sort of fractal communication that has a gradient of influence across the system. A "governmental system" with effective communication and signaling with those that occupy its domain should in principle be productive, but at the scale our societies exist, especially in large cities we just haven't found an effective way for this type of communication. They try to __govern__ and we just end up with one system imposing constraints on another without feedback based upon what one system values.
I'd typically take all this advice with the understanding that they're all selling things in some way, may have a radical leaning for engagement and would calibrate my behaviors accordingly - but things being as you've described, i'd say really internalize it.
Ken Berry is very much an advocate for full carnivore, even if you can only afford hot dogs and says that milk is useless for anyone beyond breast feeding age. Of course grass fed/finished meat, ethically raised animals is the best way to go.
Snacking on bacon, pork rinds. High fat content will help stave off any cravings hunger and sugar cravings.
I do one meal a day, assisted by a bulletproof type of coffee: grass fed butter + mct oil, I do grass fed ghee + coconut oil.
You have a tough path ahead, but its a path nonetheless.
Keto-chow a mineral and salt suppliment helps with getting what you need because you'll be losing a lot of liquid and minerals in that transition phase.
I've really dropped off this past month - sugary alcohol, less strict with carbs and multiple meals, might be noticing early symptoms myself so I'm going back.
Two things I noticed with the ketovore&one meal a day brings an eternal but subtle tunnel vision through out the day from the fast and the diet change definitely with energy levels + skin flare ups way less and more managable.
Also just remembered Paul Saladino, started 100% carnivore and shifted a little for a more wholistic evolutionary diet, but still primarily meat based.
https://www.youtube.com/watch?v=CamFyBFTbmg
think in general they'd agree that short term ketosis is helpful. At the minimum you've done an elimination diet and can introduce things after
Rooting for you. ✌️
It is inevitable. Embrace it.
nostr:nevent1qqswszxz7tcj2e0hh70tjd58plum89cd753q0vs2gszetc5v72t0p6spzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyrwye5yxe47wtvvr9t05lhgjzy5f3qxjcl3ft09su6zvqxkwua7qvqcyqqqqqqg4g55tt
Yo nostr:nprofile1qqsrg8d45l36jv05jz2as2j2ejfee79xw2fmreqhnl2ttsz5f38u9mcpr9mhxue69uhhyetvv9ujuumgd96xvmmjvdjjummwv5qs6amnwvaz7tmwdaejumr0dsq3zamnwvaz7tmwdaehgun4v5hxxmmd63qn5w can i make a request? Made a track that i'm titling "...it crumbles" because I just visualize an imposing & monolithic statue crumbling and disintegrating in slow motion when I listen to it.
nostr:nevent1qqswxx27xhlgvkj7xnk9dddsvuljckxw0d3qstterzexr5dxqp023rqpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyrwye5yxe47wtvvr9t05lhgjzy5f3qxjcl3ft09su6zvqxkwua7qvqcyqqqqqqgys8z2q
Oddbean new post about login | logout
Notes by liminal | export