melvincarvalho on Nostr: I believe the way we do paywalls can be improved if you consider how the web was ...
I believe the way we do paywalls can be improved if you consider how the web was designed.
401 = forbidden
402 = payment required
403 = not allowed
Consider that public html is only one form of the web. Think in terms of a unix style permissions system.
The 401 case is that you dont have access.
The 402 case tells you that if you pay you can get access.
The 403 case tells you that your user does not (yet) have access
Can you see what's going on here? It's a progression. It's a workflow.
First you pay. Then the server adds you to the access control, after the payment is verified.
This allows you to send your nostr id over the wire, e.g. with NIP-98. And on the server, there is a small glue file (like an inode in unix) that tells the server who has access. New payee, and new access.
This was built into the web, and I designed it into nostr from day 1. Same system can do much more than paywalls, it's a whole web operating system, that scales massively.
https://www.w3.org/wiki/WebAccessControl Yesterday, some users were able to test an early version of my lightning paywall service.
I received some great feedback, already implemented a few of the recommendations, working on NWC and shorter URLs.
You can also give it a try. If possible, please share your feedback.
https://zapit-unlock.vercel.app/
Published at
2024-10-06 11:39:37Event JSON
{
"id": "885117c410292a07c617fadb3cd3da5285b8cc6165a3c4e968f6a51ac8c879dd",
"pubkey": "de7ecd1e2976a6adb2ffa5f4db81a7d812c8bb6698aa00dcf1e76adb55efd645",
"created_at": 1728214777,
"kind": 1,
"tags": [
[
"q",
"c86abf875f66e3155beacae7c5b76dc6531cd649779b4bdc4c75035cdd607872",
"wss://ditto.pub/relay",
"",
"c6f7077f1699d50cf92a9652bfebffac05fc6842b9ee391089d959b8ad5d48fd"
],
[
"p",
"c6f7077f1699d50cf92a9652bfebffac05fc6842b9ee391089d959b8ad5d48fd",
"wss://ditto.pub/relay"
],
[
"r",
"https://www.w3.org/wiki/WebAccessControl"
]
],
"content": "I believe the way we do paywalls can be improved if you consider how the web was designed. \n\n401 = forbidden\n402 = payment required\n403 = not allowed\n\nConsider that public html is only one form of the web. Think in terms of a unix style permissions system.\n\nThe 401 case is that you dont have access.\nThe 402 case tells you that if you pay you can get access.\nThe 403 case tells you that your user does not (yet) have access\n\nCan you see what's going on here? It's a progression. It's a workflow.\n\nFirst you pay. Then the server adds you to the access control, after the payment is verified.\n\nThis allows you to send your nostr id over the wire, e.g. with NIP-98. And on the server, there is a small glue file (like an inode in unix) that tells the server who has access. New payee, and new access.\n\nThis was built into the web, and I designed it into nostr from day 1. Same system can do much more than paywalls, it's a whole web operating system, that scales massively.\n\nhttps://www.w3.org/wiki/WebAccessControl\n\nnostr:nevent1qvzqqqqqqypzp3hhqal3dxw4pnuj49jjhl4lltq9l35y9w0w8yggnk2ehzk46j8aqy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqpqep4tlp6lvm332kl2etnutdmdcef3e4jfw7d5hhzvw5p4ehtq0peqzpla7n",
"sig": "860c7678df3d17528d01069fedd7259b9ab4fbe5dc1184791e02156a17941ad92544243e0690fd8ed524c356e6ae8b08f9086d6914c60b6d7bd10594d452643f"
}
