1) Smart relays, like filter.wine, that work as business-logic "controllers" (in the model-view-controller architecture), wrapped around a model (the custom data set they manage). Nostr is originally designed to only have models (databases, in the form of dumb relays that store anything from anyone) and viewers (clients that contain both business logic and application logic).
Moving the BL to a Layer2 relay takes some of the control of the data from the client and puts it in the hands of the person running that relay, such as a community admin. It also makes the choice of client less important, so long as everyone in the community uses the same Layer2 relay, they could access it from anywhere those events are handled.
2) The client is the one managing the signing of events, so it has to sign the authorization request from relays. That signing function has to be built, and it's difficult.
3) Every product has a business model. If you don't see it, look a level higher. Someone's interests are being served. Who is that person or persons and what are their interests? In what direction is the development trending? Everyone has a strategy to serve some business model.
Laeserin
npub1m4n…c2jl
2024-07-03 10:52:32
in reply to nevent1q…j8cw
Author Public Key
npub1m4ny6hjqzepn4rxknuq94c2gpqzr29ufkkw7ttcxyak7v43n6vvsajc2jlPublished at
2024-07-03 10:52:32Event JSON
{
"id": "d2493436492152b31617517ae8d13ddfae76a6d410e4aaa07f96ece83ac5ac12",
"pubkey": "dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319",
"created_at": 1719996752,
"kind": 1,
"tags": [
[
"e",
"acb92ce69991ed2bdd760cfe8a963108a571a58bd9b98d3482c33b6a7ebc4363",
"wss://eden.nostr.land/",
"root"
],
[
"e",
"88a54bb20d226911b6196c065a3d5ec0969d515bf253f548efa89148726817f6",
"",
"reply"
],
[
"p",
"a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be",
"",
"mention"
],
[
"p",
"50809a53fef95904513a840d4082a92b45cd5f1b9e436d9d2b92a89ce091f164",
"",
"mention"
]
],
"content": "1) Smart relays, like filter.wine, that work as business-logic \"controllers\" (in the model-view-controller architecture), wrapped around a model (the custom data set they manage). Nostr is originally designed to only have models (databases, in the form of dumb relays that store anything from anyone) and viewers (clients that contain both business logic and application logic).\n\nMoving the BL to a Layer2 relay takes some of the control of the data from the client and puts it in the hands of the person running that relay, such as a community admin. It also makes the choice of client less important, so long as everyone in the community uses the same Layer2 relay, they could access it from anywhere those events are handled.\n\n2) The client is the one managing the signing of events, so it has to sign the authorization request from relays. That signing function has to be built, and it's difficult.\n\n3) Every product has a business model. If you don't see it, look a level higher. Someone's interests are being served. Who is that person or persons and what are their interests? In what direction is the development trending? Everyone has a strategy to serve some business model.",
"sig": "c25cb593fc2113c7ad7c184c60a8fea112ea4bf86b9a09f682748c6ce12077ad2ea2f0f7244e90bc16b1b287743ab54b5860bd2576665203a15306df68a3ae86"
}