HackerTrans
TopNewTrendsCommentsPastAskShowJobs

hmdai

no profile record

Submissions

Living Canvas: A web-based puzzle game powered by Generative AI

github.com
1 points·by hmdai·năm ngoái·0 comments

Why MCP can't be as simple as Naive Context Protocol

github.com
4 points·by hmdai·năm ngoái·1 comments

Show HN: I made a MIDI-based Piano training app

piano.hiku.app
2 points·by hmdai·năm ngoái·0 comments

Tell HN: ChatGPT adds utm_source=chatgpt.com to external links

4 points·by hmdai·2 năm trước·1 comments

comments

hmdai
·4 tháng trước·discuss
Genuine question, why can't this be done via an API that the agents call? there are already established ways to call APIs on behalf of the user. Seems to me that the agent is loading a web app just to be able to access it's apis, what am i missng?
hmdai
·năm ngoái·discuss
I absolutely love this, bonus: I can now read Cuneiform numbers, if I ever need that.

Suggestion: You can potentially show the Cuneiform time in the url.

sent at: 𒌋:𒎙𒐛:𒐏𒐗
hmdai
·năm ngoái·discuss
[flagged]
hmdai
·năm ngoái·discuss
Since the introduction of Model Context Protocol, I've been wondering why this protocol is so complicated to work with and after many wasted hours and a few MCP spec updates, I've decided to write down what I think MCP should have been and I call it Naive Context Protocol ¯\_(ツ)_/¯.

Maybe this approach is in fact naive (please tell why!), the "spec" is very minimal at this point (I will expand based on feedback here) and it probably ignores some use-case (some of them on purpose), but I would like to hear:

1. What everyone here thinks the MCP/NCP should've been/should be?

2. What use-cases would you like a context protocol to support?
hmdai
·năm ngoái·discuss
I'm building a client-side encrypted personal management tool for myself, with support for file encryption: