Oddbean new post about | logout
 Anyone working with DVM's (or tag someone you know): 

This is a formal spec to attach embeddings to any event. If you do any embedding work for content organization/recommendation this could help you organize the events and work with events others have labeled. Any feedback is graciously appreciated, and will gladly make essential changes to the spec.

Sure, you can keep all the computation and analysis for yourself, but you can also stand on the shoulders of those who've already done the work for you.

The ultimate goal here is that any for n=1 relay, you can decide on your own labeling for your domain or you can be interoperable with another by adopting a different spec (book, docs, w/e), thats up to the owners of the relay operators in control of the NKB.

nostr:naddr1qqyxu6mzd9cz6vpjqgsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpsrqsqqq7rz69jdtm 
 #asknostr #RunDVM 
nostr:nevent1qqs8rum6nldrpfvnj7sgqh5glc29qucyt50ahq22czd869qht6c3gugpzemhxue69uhk2er9dchxummnw3ezumrpdejz7q3qm3xdppkd0njmrqe2ma8a6ys39zvgp5k8u22mev8xsnqp4nh80srqxpqqqqqqzzs5ssc 
 This is more like Kind 1986, in my opinion. Has more to do with labeling than with article modularity. I would change the number. 🤔 
 I would just reference it from NKBIP-01, name the spec NKBIP-02, but the Kind 1986.

Then it shows up under 1984 and 1985 on the event register. So, people will be more likely to find it and less-likely to recreate it.