a on Nostr: :ipv4: nprofile1q…f9aux feld Sun this is basically websub (nee pubsubhubbub), you ...
:ipv4: (nprofile…66f2) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqwn8c84fe6hs6uav7n5vd6w0fuz4qtzqdt8cfksdr6t6r39rga2nqxf9aux (nprofile…9aux) feld (nprofile…xyvy) Sun (nprofile…h6f2) this is basically websub (nee pubsubhubbub), you just need to extend the architecture to fan out each "pub" event to potential further downstreams (with deduplication along the way to prevent cyclic graphs)
a lot of what i'm researching rn is basically how to get information to flow across generic pluggable transports. websub is a transport in the same way that linked data notifications (ldn) is a transport (and activitypub is more or less a profile of ldn). you could pass the same information as an xmpp message. you could pass it via irc (although it would be basically spam to anyone who didn't understand how to parse it)
the patterns of communication and other fundamental building blocks are consistent even when you segregate the protocols themselves by further restrictions. look no further than protocols built on top of other protocols. we could pass plaintext messages over HTTP POST with Content-Type: text/plain. but instead we pass entire HTML documents or ActivityStreams documents or whatever. and those have to be unwrapped one or possibly multiple times -- take the HTTP message and unwrap it to get the Activity out of the body content. then see that the Activity is specifically a Create, so you have to unwrap that to get the object. Then you have to know to unwrap that object to get the content.
in generic terms the best way i can model this is that there is "content" and there is "metadata", and then the two are combined in a container of sorts which consists of "header" (for metadata) and "body" (for content). but we can then treat this entire container as itself body content inside *another* container. how many times you do this nesting is arbitrary but significant. with how most people just shove everything over HTTP these days, you will at minimum have to unwrap the HTTP message. why not just stop there? why not put metadata in HTTP headers? hey at least http sigs will actually mean something then lol
a lot of what i'm researching rn is basically how to get information to flow across generic pluggable transports. websub is a transport in the same way that linked data notifications (ldn) is a transport (and activitypub is more or less a profile of ldn). you could pass the same information as an xmpp message. you could pass it via irc (although it would be basically spam to anyone who didn't understand how to parse it)
the patterns of communication and other fundamental building blocks are consistent even when you segregate the protocols themselves by further restrictions. look no further than protocols built on top of other protocols. we could pass plaintext messages over HTTP POST with Content-Type: text/plain. but instead we pass entire HTML documents or ActivityStreams documents or whatever. and those have to be unwrapped one or possibly multiple times -- take the HTTP message and unwrap it to get the Activity out of the body content. then see that the Activity is specifically a Create, so you have to unwrap that to get the object. Then you have to know to unwrap that object to get the content.
in generic terms the best way i can model this is that there is "content" and there is "metadata", and then the two are combined in a container of sorts which consists of "header" (for metadata) and "body" (for content). but we can then treat this entire container as itself body content inside *another* container. how many times you do this nesting is arbitrary but significant. with how most people just shove everything over HTTP these days, you will at minimum have to unwrap the HTTP message. why not just stop there? why not put metadata in HTTP headers? hey at least http sigs will actually mean something then lol