Thread

Replies (70)

A grosso modo, intenta dar una calificaciΓ³n al revisar la cadena para llegar de un usuario a otro segΓΊn la cantidad de saltos usando a tus contactos y los contactos de tus contactos (por lo general lo usan asΓ­), analiza todas las cadenas y da una puntuaciΓ³n, mientras menos saltos y mΓ‘s cadenas es mΓ‘s confiable el usuario… el valor lΓ­mite para definir confiable lo define el dev ademΓ‘s de las variaciones en el cΓ‘lculo para llegar al valor, mΓ‘s menos es asΓ­ como funciona
So, Vertex uses pagerank which is a probability, which implies it's a number between 0 and 1. Pagerank is distributed as a power law, which means that between an average pagerank and a high pagerank there are 4 or more order of magnitude difference. Jack dorsey has 1000-10000x the pagerank of a normal person. Power laws are hard to comprehend for the human mind, which is why Profilestr tried different formulas to normalize this score to be between 0 to 100, in ways that make sense. These formulas were not great, so I suggested they use something like this. It's poorly written but I don't have much time to work out the details. TLDR; Vertex didn't change anything, the ranks are computed as before, they are simply presented differently to the end users. This whole conversation is making me more adamant in my belief that ranks should not be displayed to end users.
your kind 0 metadata shows as this, and I just re-ran it against your listed relays "profile": { "name": "pippellia", "nip05": null, "lud16": "whitebat1", partial match only applies to the name field, and demarcated by spaces... we wouldn't want "pip" to also occupy "pi" for example... but would want someones first name to hit if they used name as First Last Partial matches do not count in the lud16/nip05's prefixes since those wouldn't have spaces... but neither your nip05 or lud16 are populated with "pip" Since your name field is "pippellia" that's what you occupy image
er, what i mean is, i don't think it should be optional. can we trust nostr clients more now than before everyone started vibe coding? no, it should be MUST not SHOULD. or you are not NIP-01 compliant and that should be avoided.