How do you create an open standard that allows for a slight different versions of implementations of #HashScore to meet the requirements of the unknown and protect against "open source gatekeeping"? A way to do is is using JSON Schemes (of course applicable also for bytes).
@WhatBitcoinDid @NSmolenski @NSmolenski touches on the social graph that @pippellia is talking about. I've also written about it here on Twitter and in doing so, detailed how we could leverage #PeerCuration and #OpenGroup to create a crowd sourced filtering mechanism. https://t.co/octrwLTFJf
With #OpenGroup (OG) everyone has their own group. When your OG and my OG overlap, we get a virtual group, manifesting itself as a distributed filtering mechanism. This way coherence and moderation can be realised, despite censorship not being possible. #future#society 1/2
@pippellia@pippellia some years back I detailed #Peercuration and it's based on the social graph. The idea is to use a JSON scheme, to define a #HashScore. #FOSS Can I DM you so we can talk more about this?
@peterktodd@ElectrumWallet True! I solved this issue in Treebit (similar to Nostr but 100% P2P and #FOSS) using a mechanism I named PeerCuration. PeerCuration fixes DDoS and spam. Designed to work in meshnets. The curious people, checks my profile for github links.
@RSvoboda432 Luck and bad luck also exists as an experience. Ive got empirical evidence of bad luck & can ensure you that this experience feels very real when ur subjected to it. We should have sympathy with people who had bad luck, because they didn't diserve it. Sometime random 2h1t happen.
People don't appreciate how much luck plays a part in their lives until they experience themselves that you can't control everything & what bad luck is! Also remember that many people (yes I am not alone) spent their wealth trying to actually improve the world.
@StackingHats With basically zero satoshis left after having to finance my own projects (which are FOSS by the way!) in addition to having to pay some un-expected expenses, these kind of posts really triggers me! "Better hodler" is so easy to say, but u also have to be lucky!!!
@RSvoboda432 Yes. It's a random event that turns out in your favour. However, only when you die there can be certainty if the event was in your favour & also you wont be able to ascertain the opportunity cost. Bad luck is the absence of luck. Because of entropy, it must be 1 of these 2.
@BitcoinErrorLog@archimedeanapex "U spent some coins to me, but after 100 confirmation it wasn't final enough for me, so I sent them to someone else. Sorry, u can't stay in my AirBnB because you never paid me... because it was never final enough." #upToTheCounterParty2Decide
@StackingHats With basically zero satoshis left after having to finance my own projects (which are FOSS by the way!) in addition to having to pay some un-expected expenses, these kind of posts really triggers me! "Better hodler" is so easy to say, but u also have to be lucky!!!
@RSvoboda432@Tocharus In the PeerCurated system I designed, the HashScore (PeerScore) is created automatically the background with inputs such as (but not limited to) number of times content was consumed, liked, re-posted, etc. This way content get ranked just as you proposed above.
@nvk@nvk by adding "open groups" and peercuration to it (simple protocols 100% designed to work with nostr), moderating that list would be breeze. Do you already know about these concepts?
@RSvoboda432@Tocharus One hates: 0. One loves: 1. Average is 0.5. However more importantly, you will tend to filter out the peers that don't share your taste, thus end up with people that you think scores the way you want your peers to score. Correct?
@RSvoboda432@Tocharus IMDb (and similar, such as twitter Likes) is a "shoutbox" trying to deduce the "global truth". With HashScore there is only your own contextual truth and your incentive is to only select peers you trust to score well If you want to you can individually weight your peers scores to