The theory of operation of more-speech is:
1. Relays are categorized as trust, web-of-trust, or all.
* trust: Only events from those who are trusted (kind 3) are subscribed.
* web-of-trust: Only events from those who are trusted, and those whom they trust are subscribed.
* All: Every event is subscribed.
Users make this choice based upon the volume of the relay. A very high volume relay will have to be constrained to just 'trust'. Moderate volume relays can be relaxed to 'web-of-trust'. Lower volume relays can be set to 'all'.
2. Every event is subject to a set of filters associated with tabs on the display. The filters within a tab can select or block based upon the ids of users, events, or the content of events. So, for example, I can set up a tab that will select for all events mentioning GAZA while also blocking certain nasty people based on their ids. I can also set up a tab that selects for any event sent as a reply to a particular event id -- thus capturing the thread of an event.
From: manime<-mazin at 05/08 14:00
> What’s more-speech?
CC: ManiMe (npub1man…n9tn)
CC: fiatjaf (npub180c…h6w6)
CC: Thoreau (npub1th0…l7mx)
CC: Derek Ross (npub18am…p424)
CC: unclebobmartin (npub19mu…jnft)
unclebobmartin /
npub19m…njnft
2024-05-09 15:27:13
in reply to nevent1q…6t4q
Author Public Key
npub19mun7qwdyjf7qs3456u8kyxncjn5u2n7klpu4utgy68k4aenzj6synjnftPublished at
2024-05-09 15:27:13Event JSON
{
"id": "000930e9a0a1edeafc09dc04d42c0ebe7863f249fae4de84ce585797c5045e0d",
"pubkey": "2ef93f01cd2493e04235a6b87b10d3c4a74e2a7eb7c3caf168268f6af73314b5",
"created_at": 1715261233,
"kind": 1,
"tags": [
[
"e",
"04116695cf477a99fcc89ce7337fe1686ce5d490dce7cd0e1eb1ef9884cb489c",
"",
"root"
],
[
"e",
"acda10746f7132eefaebabfb85a9e6e1b639459c3eea957ccb8e6f4b85f699fc",
"",
"reply"
],
[
"p",
"df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200"
],
[
"client",
"more-speech - 2023-07-13T12:37"
],
[
"p",
"df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"5dde36195bc484050ca193690ef939b2329506c4da473bd985f1d0e26d9a953a"
],
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
],
[
"p",
"2ef93f01cd2493e04235a6b87b10d3c4a74e2a7eb7c3caf168268f6af73314b5"
],
[
"nonce",
"1063",
"12"
]
],
"content": "The theory of operation of more-speech is:\n\n1. Relays are categorized as trust, web-of-trust, or all. \n * trust: Only events from those who are trusted (kind 3) are subscribed.\n * web-of-trust: Only events from those who are trusted, and those whom they trust are subscribed.\n * All: Every event is subscribed. \n\nUsers make this choice based upon the volume of the relay. A very high volume relay will have to be constrained to just 'trust'. Moderate volume relays can be relaxed to 'web-of-trust'. Lower volume relays can be set to 'all'.\n\n2. Every event is subject to a set of filters associated with tabs on the display. The filters within a tab can select or block based upon the ids of users, events, or the content of events. So, for example, I can set up a tab that will select for all events mentioning GAZA while also blocking certain nasty people based on their ids. I can also set up a tab that selects for any event sent as a reply to a particular event id -- thus capturing the thread of an event. \n\n\n\n\nFrom: manime\u003c-mazin at 05/08 14:00\n\n\u003e What’s more-speech?\n\nCC: #[4]\nCC: #[5]\nCC: #[6]\nCC: #[7]\nCC: #[8]",
"sig": "ade2787b1c99c6f7d7976987656e579fedd3a63a4ccf4f442e0360bd26b5a74ca3fa6e528fd5d9d8bc43c7c786f0abd45a602e3e9356b9ed72584653aca7d328"
}