Dude. You have awesome feedback. And now I have even more questions… so no … you don’t get to just “drop a comment and go”.
- first … actually nostr already has a lot of public data for anyone (relays admins) to use in developing algos and such.
- encrypted events are becoming a thing in Nostr. These “gift wrapped” events are mostly opaque to relay operators, which will complicate everything related to server side data processing.
- Client side data processing of encrypted events will still be possible … and Nostr SHOULD have NIP in place for “privacy agreement” or something that keeps clients transparent and honest (like a checkbox “allow client side only processing of private DMs to improve WoT score…”)
- given all this… private “is trusted” events will be the first challenge to design an implementation standard for. Yes. These will need to be encrypted (who is trusting who) AND available for server side processing (who’s in my trust network) … I’m “confident” this is doable.
So yea… let’s be clear and lay solid groundwork to let WoT on Nostr be sovereign by design.
ManiMe /
npub1man…n9tn
2024-05-26 17:19:44
in reply to nevent1q…ure0
Author Public Key
npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tnPublished at
2024-05-26 17:19:44Event JSON
{
"id": "5c03044a896c7c99a4d67a5595f1b0b215c632c3b003b53357c5d5ac1804c93b",
"pubkey": "df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200",
"created_at": 1716736784,
"kind": 1,
"tags": [
[
"e",
"de8a97bc622006877c7881a9a69867a794395430fe8401bf0103992f9e3b4907",
"",
"root"
],
[
"e",
"e991979f1c158f03a59bc15ae2544299da9c8943c13a44ced54df14486c3069c",
"",
"reply"
],
[
"p",
"cd868bf553cabfeef5ff89f9d34875210cdeda276ca4c6a3e7ffb7a31ab96447"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"p",
"4b74667f89358cd582ad82b16a2d24d5bfcb89ac4b1347ee80e5674a13ba78b2"
],
[
"p",
"cfd7df62799a22e384a4ab5da8c4026c875b119d0f47c2716b20cdac9cc1f1a6"
],
[
"p",
"726a1e261cc6474674e8285e3951b3bb139be9a773d1acf49dc868db861a1c11"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"df67f9a7e41125745cbe7acfbdcd03691780c643df7bad70f5d2108f2d4fc200"
],
[
"p",
"e5272de914bd301755c439b88e6959a43c9d2664831f093c51e9c799a16a102f"
],
[
"p",
"633f317e99bc5a55c85d842784989a2bcdc31bea3c4c01fdfc80fd340facca3a"
],
[
"client",
"Nostur",
"31990:9be0be0fc079548233231614e4e1efc9f28b0db398011efeecf05fe570e5dd33:1685868693432"
]
],
"content": "Dude. You have awesome feedback. And now I have even more questions… so no … you don’t get to just “drop a comment and go”.\n\n- first … actually nostr already has a lot of public data for anyone (relays admins) to use in developing algos and such. \n- encrypted events are becoming a thing in Nostr. These “gift wrapped” events are mostly opaque to relay operators, which will complicate everything related to server side data processing. \n- Client side data processing of encrypted events will still be possible … and Nostr SHOULD have NIP in place for “privacy agreement” or something that keeps clients transparent and honest (like a checkbox “allow client side only processing of private DMs to improve WoT score…”)\n- given all this… private “is trusted” events will be the first challenge to design an implementation standard for. Yes. These will need to be encrypted (who is trusting who) AND available for server side processing (who’s in my trust network) … I’m “confident” this is doable. \n\nSo yea… let’s be clear and lay solid groundwork to let WoT on Nostr be sovereign by design. ",
"sig": "1b5eba074b8342bae23154299bcb83d2aac59d7b9a8e6563fb417fe47dc75383d66da2aeb0683beaa96d6c0123c55086a033eb4aac19a3e6d138a0429454a8cd"
}