I read the source on wikistr for the kind 1987 specification.
I like the idea about precalculating embeddings when generating content for efficiency.
One main question though:
You cannot avoid forged embeddings, can you?
This is SEO back to field one. The content “does not speak for itself”.
You cannot get around some concept of source reputation, I guess.
Or is there a fast way to check on an embedding by verifying it against the content? Like we do for hashes?
schmijos / Josua Schmid
npub1ax…h6ukq
2024-10-10 13:26:30
in reply to nevent1q…4x53
Author Public Key
npub1axy65mspxl2j5sgweky6uk0h4klmp00vj7rtjxquxure2j6vlf5smh6ukqPublished at
2024-10-10 13:26:30Event JSON
{
"id": "6a120a3fb58c012e92d6325d9fe1bd93c022df117bdc89d2b5e4f4845d55566b",
"pubkey": "e989aa6e0137d52a410ecd89ae59f7adbfb0bdec9786b9181c3707954b4cfa69",
"created_at": 1728566790,
"kind": 1,
"tags": [
[
"e",
"a89bcb089b90dc33278e32d9e546444d8cf86250879608db30ca03f7e027583a",
"wss://niel.nostr1.com/",
"root"
],
[
"e",
"9eb5514a5781893ce3c70fb04285c791a61ca0c511f27154687183b07e3ee23f",
"",
"reply"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be"
],
[
"p",
"dc4cd086cd7ce5b1832adf4fdd1211289880d2c7e295bcb0e684c01acee77c06"
],
[
"p",
"70122128273bdc07af9be7725fa5c4bc0fc146866bec38d44360dc4bc6cc18b9"
],
[
"p",
"fd208ee8c8f283780a9552896e4823cc9dc6bfd442063889577106940fd927c1"
]
],
"content": "I read the source on wikistr for the kind 1987 specification.\nI like the idea about precalculating embeddings when generating content for efficiency.\n\nOne main question though:\nYou cannot avoid forged embeddings, can you?\nThis is SEO back to field one. The content “does not speak for itself”.\nYou cannot get around some concept of source reputation, I guess.\n\nOr is there a fast way to check on an embedding by verifying it against the content? Like we do for hashes?",
"sig": "cb8e77a32a2fd1bbb716e35295792f48401bcd963bf9465b50ba18dc5168c9eb501dce44414d17ba4322d540e519a60103411813bc79ccd7ff05e48778e270f2"
}