I get your worries on client dependency to coordinate, and notes not being shared broadly via the outbox model. My suggestion doesn't change the outbox model but rather optimizes it. It would not be able to solve the broadcasting issue, but it can resolve many other concerns.
The idea is more like “Relay-as-a-Service (RaaS)” concept whereby you have a personal relay that is more lightweight as it only stores your notes, messages etc compared to general relays that store all the data. You can have this hosted locally for security purposes or relay devs can expand their service to "cloud" for users who don't want to host locally, just because or for safety reasons.
When you send data, someone else who has some common relays with you will be able to view it.
It can be cross synched to your other devices like will's idea or use IoT concept like LoRa or Zigbee or regular wifi but might need some network protocal synch
To enhance privacy, clients can also enhance UX for users who want to share both privately and globally presuming what they share is limited to selected relays or not visible to the public.
Users can delete their own notes but it might need some protocol to delete notes that are temporarily or permanently stored anywhere else.
Users can also upgrade storage capacity or use external relays for specific functions (images, video stage, streaming etc) to ensure modularity and scalability.
The overall idea is to not only optimize data storage, but also gives users full control of their own data (delete, edit, privacy etc).
pam
npub1pv…kdx8c
2024-09-05 14:10:36
in reply to nevent1q…y9dn
Author Public Key
npub1pvgcusxk7006hvtlyx555erhq8c5pk9svw57snlxujpkgnkup89sekdx8cPublished at
2024-09-05 14:10:36Event JSON
{
"id": "51ebf355a2b57cbccfe3f02942fdc3fb666d06367dc9fe4402e19d4720c05468",
"pubkey": "0b118e40d6f3dfabb17f21a94a647701f140d8b063a9e84fe6e483644edc09cb",
"created_at": 1725545436,
"kind": 1,
"tags": [
[
"e",
"bd79ffb8fdfdad6dfbe6be9fea869b1f12d560efcfcdad5912bc76d16208b7fb",
"",
"root"
],
[
"e",
"b32b9f75f77894eb30bb7839951ce41e0cdad4df78cc0dc80919fdfaca76227e",
"",
"reply"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"9fec72d579baaa772af9e71e638b529215721ace6e0f8320725ecbf9f77f85b1"
],
[
"p",
"0b118e40d6f3dfabb17f21a94a647701f140d8b063a9e84fe6e483644edc09cb"
]
],
"content": "I get your worries on client dependency to coordinate, and notes not being shared broadly via the outbox model. My suggestion doesn't change the outbox model but rather optimizes it. It would not be able to solve the broadcasting issue, but it can resolve many other concerns. \n\nThe idea is more like “Relay-as-a-Service (RaaS)” concept whereby you have a personal relay that is more lightweight as it only stores your notes, messages etc compared to general relays that store all the data. You can have this hosted locally for security purposes or relay devs can expand their service to \"cloud\" for users who don't want to host locally, just because or for safety reasons. \n\nWhen you send data, someone else who has some common relays with you will be able to view it.\n\nIt can be cross synched to your other devices like will's idea or use IoT concept like LoRa or Zigbee or regular wifi but might need some network protocal synch\n\nTo enhance privacy, clients can also enhance UX for users who want to share both privately and globally presuming what they share is limited to selected relays or not visible to the public. \n\nUsers can delete their own notes but it might need some protocol to delete notes that are temporarily or permanently stored anywhere else.\n\nUsers can also upgrade storage capacity or use external relays for specific functions (images, video stage, streaming etc) to ensure modularity and scalability. \n\nThe overall idea is to not only optimize data storage, but also gives users full control of their own data (delete, edit, privacy etc). \n",
"sig": "ba2682b45a8bfe4c27958e3de5fbcdbe11cbd1f3d1510284c4a006eedb42b1285afb0b03cd3917b7a433e5498e5fa58d7e9e694a73b51a4a58320e4bc7b845a6"
}