rabble on Nostr: Yeah I’ve worked with standards bodies and there are problems. In particular there ...
Yeah I’ve worked with standards bodies and there are problems. In particular there is the way language around inclusivity and support are used to create overly complicated standards that are subject to capture by institutional players. I worked on OAuth and saw how the original vision, elegant security, and simplicity of OAuth 1.0 was lost so we could neet the needs of google.
IETF does a better job than W3C but they’re all operating under a paradigm of big companies making very static systems.
Rough consensus and running code is bettet than a consortium where you need to pay $50k a year and have full time staffers in order to participate in the open standards process.
Published at
2023-11-18 22:28:11Event JSON
{
"id": "df4f3e0480fd533c9cbb55a98aa31991485f3a56df347ad109dd321b34eefb12",
"pubkey": "76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa",
"created_at": 1700346491,
"kind": 1,
"tags": [
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
],
[
"e",
"5b7a0e7473a5d7cc497d5c565ffe31704f2cb6d5634789af0030a9daafb700b7",
"",
"root"
]
],
"content": "Yeah I’ve worked with standards bodies and there are problems. In particular there is the way language around inclusivity and support are used to create overly complicated standards that are subject to capture by institutional players. I worked on OAuth and saw how the original vision, elegant security, and simplicity of OAuth 1.0 was lost so we could neet the needs of google. \n\nIETF does a better job than W3C but they’re all operating under a paradigm of big companies making very static systems. \n\nRough consensus and running code is bettet than a consortium where you need to pay $50k a year and have full time staffers in order to participate in the open standards process. ",
"sig": "d3cd8e90ccb4ef0173856f096cd5dc9923e898484723550a8cd2dcb453a22a902e9cd3e34f0dec6ed7b39b8ccce7fcf1d0b569c2776b784a9b40ed392e35bca4"
}