7 ms·
Successful standards usually start out scrappy, are embraced by a community, and then are blessed by standards bodies. What comes out of working groups of stand
by underbluewaters 1y ago
Successful standards usually start out scrappy, are embraced by a community, and then are blessed by standards bodies. What comes out of working groups of standards bodies rarely gains traction. See xhtml vs "html5".
- croes 1y agoDoes MCP still have the security issues? A big mistake in the first place to start it without proper security. That not Web 2.0 2.0, that‘s Web 1.0
- doug_durham 1y agoIt's a mistake to not start at all because of an issue that may not be important for many important use cases.
- croes 1y agoIt’s a mistake to start and to think security is a non important issue. Anything that’s connected to the web has to consider security at step one. How often are we repeating the same mistakes over and over again?
- troupo 1y agoIt's a mistake to invent your own terminology, skip all existing forms/standards/protocols of communication and chose the objectively worst-fitting one, and skip implementing one of the most fundamental part required by nearly anything
- jedisct1 1y agoMCP Servers are usually installed locally and can do whatever they want on the local machine. But this is solved by sandboxes such as mcp.run .
- croes 1y agoSandboxes aren’t a solution just a workaround for a bigger problem