oh yeah, Steem (and hive) are specifically social network related but they are proof of stake, trash from that Dan Larimer Bytemaster guy. but their consensus is stake based, the stake is delegated by users voting for them.
i think it's worth taking a shot at building one and since you and I both want to do such a thing, it would probably be productive to continue a dialog, if you are interested, as it really depends on enough users to actually prove the concept.
I def want to build a system of distributed consensus using WoT — and a neo4j nostr relay will be a very useful step in that direction!
If you like, I can propose a schema for this. (Brainstorm doesn’t need a fully functional neo4j relay — it can make do with a much more restricted schema as described in my docs, at least for now — but a fully functional relay would be awesome and is def worth doing. Nothing like going above and beyond!)
Cool. Will work on it probably tonight and let you know when it’s done.
I can see two ways to go about it.
The first way would be to store the entirety of the data, including content fields, inside neo4j. I guess this would be the “purist” way, but events with lots in the content would eat up memory.
So the second way would be to omit content (and sig) properties from neo4j (with perhaps some exceptions, like kind 0 events), the goal being to reduce the amount of memory required for neo4j. In this method, we would view neo4j as an adjunct to a non-graph database, which could be relational, KV, etc, which would store each event in its entirety.
Perhaps I’ll design a schema for the purist method first and we can switch to the second method if/when bloat becomes too much of a problem.
https://git.nostrdev.com/mleku/next.orly.dev/src/branch/main/docs/FIND_RATE_LIMITING_MECHANISMS.md
this lists a number of options that have been used somewhere or discussed previously. a few of them might work. as i see it the main thing i haven't covered in the design is that initial bonanza problem.
yes, also, name->npub registration has been added to my design, in addition to all the standard DNS records. the idea would be that aside from the connectivity to the data source, it would be functionally equivalent to BIND
