Yeah, that’s one flow. The important part is that you accept events as inputs so if I create a 5250 with
[ i, “event-id”, “event” ]
You fetch event-id and use that content as the text to be processed
That way i can:
* create a nostr content discovery event
-> output of that is 50 or 100 e tags of interesting events
* create a summarization job that takes those 50 or 100 events as input and creates a single summarization content
* create a 5250 that reads me the summarization in guy swann’s voice
PABLOF7z
npub1l2…tajft
2024-01-04 09:58:33
in reply to nevent1q…e9yn
Author Public Key
npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajftPublished at
2024-01-04 09:58:33Event JSON
{
"id": "4b14d4dd7c1942445c14737dc373a6996f35c25880c1a4dee2ea93184f938075",
"pubkey": "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"created_at": 1704358713,
"kind": 1,
"tags": [
[
"e",
"d1db8f8f1db6845e9b40e583356f6ca98c29b1203f874e3d8046dceff5da4c3e"
],
[
"e",
"cf1a93b56457a62661e08e138f05b36a478e4c80c0ae85e02a232f034c1ede8a"
],
[
"p",
"be7358c4fe50148cccafc02ea205d80145e253889aa3958daafa8637047c840e"
]
],
"content": "Yeah, that’s one flow. The important part is that you accept events as inputs so if I create a 5250 with\n\n[ i, “event-id”, “event” ]\n\nYou fetch event-id and use that content as the text to be processed\n\nThat way i can:\n* create a nostr content discovery event\n-\u003e output of that is 50 or 100 e tags of interesting events\n* create a summarization job that takes those 50 or 100 events as input and creates a single summarization content\n* create a 5250 that reads me the summarization in guy swann’s voice",
"sig": "cb13a6c11b039482ca5cdb357cd344375ab2407068562657d538b2462075ad44388cfcf87afe1935aa2429a3fc6d47bfd9da195f9696c4ebdaf1212f63eeedf2"
}