are backlinks part of the design or on the roadmap for NKB/Wikistr nostr:nprofile1qqs06gywary09qmcp2249ztwfq3ue8wxhl2yyp3c39thzp55plvj0sgprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qguwaehxw309a6xsetrd96xzer9dshxummnw3erztnrdakj7qgmwaehxw309amksetpwshxsctswpuhgctkv4exutnrduhsw0qlr4 nostr:nprofile1qqsdcnxssmxheed3sv4d7n7azggj3xyq6tr799dukrngfsq6emnhcpspzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7hy49z6 ?
Do you mean the tags for derivative events? I'm already using those in some of the publications and we have a ticket to display them in the cards, for Gutenberg (0.1.0).
Wiki viewer and internal [[linkage]] is coming in the Euler (0.2.0) version, since we need it for research papers.
I'm not sure, if that's what you meant.
Derivative link example for nostr:nprofile1qqsvdxm3m3tylhp4ptxal7ff7fwhyq4vz3cvsaygvz9adkvwgf46wccpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uq3zamnwvaz7tmwdaehgu3wwa5kuef0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0urhjv6's book, at the bottom of the json.
I mean the events that link TO a given event. inbound links. (Which I imagine is far harder to compute. And it would have to be client/relay side, not part of the event itself for a lot of reasons... it updating occasionally being one of them)
See Obsidian's concept of backlinks.
