2 ms·
I might be naive, but I think it's time we seriously start implementing "HTTP status code 402: Payment Required" across the board. "L402" is an interesting pro
by hugs 2y ago
I might be naive, but I think it's time we seriously start implementing "HTTP status code 402: Payment Required" across the board.
"L402" is an interesting proposal. Paying a fraction of a penny per request.
https://github.com/l402-protocol/l402 https://github.com/l402-protocol/l402
- rambambram 2y agoI stumbled upon this status code last year - had never heard of it before - and I bookmarked it and then forgot about it. Thanks for the reminder.
- cwmma 2y agothis is basically what they are doing, but instead of charging actual money they are making visitors spin the CPU ideally in a proof of work problem, which has the same outcome from the crawlers perspective.
- woah 2y agoThis has existed for decades. The proof of CPU work is called "frontend frameworks"
- fewsats 2y agoI've talked with tons of publishers and all say the same thing: "Hey, we'd happily give these companies clean data if they just paid us instead of building these scrapers." I think there is a psychological aspect that made micropayments never work for humans but machines may be better suited for it.
- SoftTalker 2y agoThis is ultimately the answer. If something has value, users should pay for it. We haven't had a good way to do that on the web, so it has resulted in the complete shitshow that most websites are.