cloud fodder on Nostr: samsies but for relays, brain hurtz Write ACLS was hard enough, and now we have ...
samsies but for relays, brain hurtz
Write ACLS was hard enough, and now we have NIP-42 AUTH read ACLs to layer on top of write. 'Types' of relays expanding constantly. People using Relays as TCP/IP, using them as base64 image servers, using them as DNS, using them as cashu wallets, using them for anything and not really saying what they're using them for. Unlimited "kinds", or limited, but who knows what they even are? Github searching the nips repo like a donkey with rabies and not finding anything you need to find, forced to login and KYC with them just to search. Kinds galore, kinds upon kinds.. What to limit what to not limit? Will people even use lightning or will clients even help them pay for relays or just keep giving it away for free? Servers exploding under 60+ load average and then having zero traffic. Clients sending drafts to 600+ relays on every keystroke via blastr. Like bots, follow bots, happy new year bots, comment bots, stalker bots, denial of service bots, jealous bots, bots that are ok.
Implementing 'private inboxes' to allow everyone to connect and AUTH, but only allow them to send a message if they're a subscriber, but ALSO allow anyone to send if they tag someone who IS a subscriber, but only if it's a 'private message' of 6-7 different kinds. Only allowing each individual pubkey to download their OWN private messages if they're a subscriber instead of the whole network of private messages.
Allowing things, blocking things, but override the allows with blocks, and then do that for reads AND writes, and for kinds and pubkeys and keywords, but with separate logic when required.
Well, I am looking forward to client outboxes/inboxes and upgrading all relays to AUTH so much and I know it's super hard. The relays will be here to support you. If anyone can do it it's
Vitor Pamplona (npub1gcx…nj5z) and
Mike Dilger (npub1acg…p35c) Ok, keeping the feed consistency between the outbox model (only downloading certain event kinds from certain relays based on the author's lists) + maintaining EOSE's for each subscription in each separate relay so we don't download things twice + rotating the filter within each relay because either the follow list or the kind list is too big for that particular relay + reconnecting to AUTH as separate users that are logged into the app + packing as much into a single subscription as possible because many relays limit the number of subscriptions is driving me slighly crazy.
Nostr is easy only in the first 10 days of developing an app.
Published at
2024-07-23 21:29:24Event JSON
{
"id": "00000656ae7de86281d87bfbf9ad69b3eaf436059576fc01b527213f82020d7f",
"pubkey": "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e",
"created_at": 1721770164,
"kind": 1,
"tags": [
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49"
],
[
"q",
"3f2c021b29ccf963e9563e9ac0c2ebaf0e99ebc37530a2aedbd44764cff1c41b"
],
[
"nonce",
"9223372036855220241",
"21"
]
],
"content": "samsies but for relays, brain hurtz\n\nWrite ACLS was hard enough, and now we have NIP-42 AUTH read ACLs to layer on top of write. 'Types' of relays expanding constantly. People using Relays as TCP/IP, using them as base64 image servers, using them as DNS, using them as cashu wallets, using them for anything and not really saying what they're using them for. Unlimited \"kinds\", or limited, but who knows what they even are? Github searching the nips repo like a donkey with rabies and not finding anything you need to find, forced to login and KYC with them just to search. Kinds galore, kinds upon kinds.. What to limit what to not limit? Will people even use lightning or will clients even help them pay for relays or just keep giving it away for free? Servers exploding under 60+ load average and then having zero traffic. Clients sending drafts to 600+ relays on every keystroke via blastr. Like bots, follow bots, happy new year bots, comment bots, stalker bots, denial of service bots, jealous bots, bots that are ok.\n\nImplementing 'private inboxes' to allow everyone to connect and AUTH, but only allow them to send a message if they're a subscriber, but ALSO allow anyone to send if they tag someone who IS a subscriber, but only if it's a 'private message' of 6-7 different kinds. Only allowing each individual pubkey to download their OWN private messages if they're a subscriber instead of the whole network of private messages.\n\nAllowing things, blocking things, but override the allows with blocks, and then do that for reads AND writes, and for kinds and pubkeys and keywords, but with separate logic when required.\n\nWell, I am looking forward to client outboxes/inboxes and upgrading all relays to AUTH so much and I know it's super hard. The relays will be here to support you. If anyone can do it it's nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z and nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c\n\nnostr:nevent1qqsr7tqzrv5ue7tra9traxkqct467r5ea0ph2v9z4mdag3myelcugxcudvj2c\n",
"sig": "f4c2252a6d192b0a76d786de61afa082b83c5e3821bd9ea53cae1c3bbe741b809d8dde153f69eb8e49753680e7f7cfcaef3de1dfbbdcabe5a462f0dc7e04b03c"
}
