“Scarcity” may be too simplistic because it reduces events to one scale. A “distance” metric could be more precise for the kinds of problems we’d like to solve with nostr. And we’re used to multi-dimensional distance.
Following, muting, banning is all binary on a distance scale. In the real world instead we attach social capital to individuals and screaming can bridge this gap, but not from Europe to America and not for long because you’ll get a sore throat.
It would be nice, if clients would experiment with more continuous distance metrics. Zapping being one of them.
Regarding Follows you might enjoy this thread: nostr:nevent1qvzqqqqqqypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqqszfm9mvw25s2s720slcx389sw4ylamnl4j6zk2mdm9qsdx2wlyvqqf8hm6t
Regarding Zaps I agree with you. That's why I'm designing for Zaps to be more than just Tips.
IF
1. Creators can reply to them
2. Zappers can see their zap amount in context
THEN
We can see some kind of market pricing form around what amounts/comments are going to get you recognition/attention/reputation ...
Nice, thank you for sharing!
@Silberengel do we have a proposal somewhere for non-discrete relationship declaration? I’m missing the numerics in nostr. It would be cool if we could do calculations with events instead of sticking to categories.
For example I’d like to think a bit more about npub “location” and “distance”. May something to be tried out with a spatial database such as postgis.
Facebook has graphs, but does anyone have a spatial database underlying its social network?
Well, we have the NKBIP-02 for vector embeddings, that @liminal wrote.
relationship_status: [embedding float32 x 768] is the new "it's complicated"
nostr:nevent1qvzqqqqqqypzp6vf4fhqzd749fqsanvf4evl0tdlkz77e9uxhyvpcdc8j495e7nfqqs2g8xpcfrzfpk2dey4jvxsh4qgslat7puwk5adxghn4gqj7xhd5eqcr6l02
Oddbean new post about login | logout