lumbroso

7 ms·

1.
by lumbroso 1y ago
I hope this doesn't become the only way to access the underlying model. As a power user: - I know exactly when I would like to work with any given model! - I like to switch models during a conversation for various purposes. I would fin
2.
by lumbroso 1y ago
Not sure I understand this one? Reexplain?
3.
by lumbroso 1y ago
Yes, I see your point: You are saying that embedding time points doesn't equate with giving an understanding of time. I think you're right. Part of the point of the article is that the process of giving LLMs awareness of specific
4.
by lumbroso 1y ago
This is an awesome idea! And the multiple levels of abstraction enrich the concept. What would be the pricing model? I also want to give two shout-outs: - the Echoes Chrome Extension that makes it easy to search through conversations: http
5.
by lumbroso 1y ago
First, I think various models have various degrees of sycophancy — and that there are a lot of stereotypes out there. Often, the sycophancy, is a "shit sandwich" — in my experience, the models I interact with do push back, even
6.
by lumbroso 1y ago
Without engaging in the whole "anthropomorphizing" debate in this post, I'll say I reject the framing, for many reasons I'd be happy to discuss. At the same time I understand what you mean and I agree that no, this does
7.
by lumbroso 1y ago
Thank you so much for sharing your customizations and conversations, it is really fascinating and generous! In both of your conversations, there is only one depth of interaction. Is that typical for your conversations? Do you have example
8.
by lumbroso 1y ago
One last thing I will say: The MCP server specification is unclear how much the initial "instructions", the README.md of the server for the model, is discovered. In the "passage-of-time" MCP server, the instructions prov
9.
by lumbroso 1y ago
It's good idea. I didn't think of it because this project came about a "let's try to write a remote MCP server now that the standard has stabilized." But there are some issues: 1. Cheaper + Deterministic: It is much
10.
by lumbroso 1y ago
Glad the little political wink landed with at least one reader! You’re right: Stripping away all ambient context is both a bug and a feature. It lets us rebuild “senses” one at a time—clean interfaces instead of the tangled wiring in our o
11.
by lumbroso 1y ago
Noted, thank you!
12.
by lumbroso 1y ago
Great question! Injecting a raw epoch each turn can work for tiny chats, but a tool call solves four practical problems: 1. *Hands‑free integration*: ChatGPT, Claude, etc. don’t let you auto‑append text, so you have to manually do it. He
13.
by lumbroso 1y ago
One‑shot timestamps (the kind hard‑coded into Claude’s system prompt or passed once at chat‑start) go stale fast. In a project I did with GPT‑4 and Claude during a two‑week programming contest, our chat gaps ranged from 10 seconds to 3 day
14.
by lumbroso 1y ago
Hey, thanks so much for sharing, your repo is really cool, including the GEMINI.md context engineering file! I am curious: You say "offline-first or local-first, quantified self projects", what models do you use with your projects
15.
by lumbroso 1y ago
I'm sorry for choosing an inappropriate title — that was my bad, and fortunately @dang helped correct this mistake. Aside from the title, what claims do I make that you find ridiculous?
16.
by lumbroso 1y ago
Thanks so much for the title change! I completely understand. I apologize to the community for the mistake. I appreciate this feature of this community's discourse. I'll remember to use literal, precise language in the future. You
17.
by lumbroso 1y ago
Disposal8433, I am not unsympathetic to your point, but I think that bad managers and CEOs are bad managers and CEOs. For instance at Boeing, the fault of software problems lies entirely on the managers: They made the decision to subcontrac
18.
by lumbroso 1y ago
I'm sorry for the misleading title about a sundial, it was a metaphor, and based on the feedback here, if I had to do it again I would pick a different one. :-) My only worry with these MCP "sensors" is that they add-up to th
19.
by lumbroso 1y ago
That's exactly what I've been thinking too! MCP + LLMs = our solution to data integration problems, which include context awareness limitations. It's an exciting development and I am glad you see it too!
20.
by lumbroso 1y ago
Fair point on the metaphor—let me be concrete. What’s new here isn’t just exposing `current_datetime()`. The server also gives the model tools to reason about time: (1) time_difference(t1, t2) – exact gaps with human wording (
21.
Show HN: An MCP server that gives LLMs temporal awareness and time calculation(github.com)
91 points by lumbroso 1y ago|55 comments