Hacker Newsnew | past | comments | ask | show | jobs | submit | ripley12's commentslogin

The search bugs in Mail are absolutely real. They might not affect every user but I've had major issues on both macOS and iOS mail, and eventually gave up and switched to Gmail.

Have you checked if it’s the fault of your mail providers? The search function queries the remote mail servers in addition to the local cache. If the mail servers return garbage you get garbage results.

This was with an iCloud email address.

Maybe iCloud search is rubbish.

Mail search works flawlessly for me with Gmail and Outlook. It takes a sec but the results are always relevant.


As I used to ask field teams and PMs back when I was a SWE - provide the steps to reproduce the bug as I can't seem to recreate it.

I can see where Mario is coming from, but IMO MCP still has a place because it 1) solves authentication+discoverability, 2) doesn't require code execution.

MCP shines when you want to add external functionality to an agent quickly, and in situations where it's not practical to let an agent go wild with code execution and network access.

Feels like we're in the "backlash to the early hype" part of the hype cycle. MCP is one way to give agents access to tools; it's OK that it doesn't work for every possible use case.


Oh, I didn't intend this to come across as MCP being useless. I've written this from the perspective of someone who uses LLMs mostly for coding/computer tasks, where I found MCP to be less than ideal for my use cases.

I actually think MCP can be a multiplier for non-technical users, where it not for some nits like being a bit too technical and the various security footguns many MCP servers hand you.


That makes sense to me, thanks for the clarification.


120m would be an absolutely insane width for a trench. It seems more likely that you’ve misinterpreted that.


Midori was fascinating. Joe Duffy's writing on it is the most comprehensive I've seen: https://joeduffyblog.com/2015/11/03/blogging-about-midori/

I've heard someone at Microsoft describe it as a moonshot but also a retention project; IIRC it had a hundred plus engineers on it at one time, including a lot of very senior people.

Apparently a bunch of research from Midori made it into .NET so it wasn't all lost, but still...


> retention project

Never heard this phrase before, but I can definitely see this happening at companies of that size


Similar approach as MCPCat (telling agents to specify context about why a tool was called in special tool arguments): https://mcpcat.io/

I don't love it (potential privacy issues, and it makes the user's agent spend more tokens), but I don't think there's a better approach right now. Would be great if someone took the time to add an observability mechanism to the MCP spec itself.


After taking a closer look at MCPCat the implementation is quite different for MCPCat you need to integrate a SDK and HyprMCP works as a proxy in front for your already existing MCP server.


The token spend only increases due to the additional parameter names and descriptions, right?


Not just that - for every tool call, the user's agent has to output some extra tokens to put the context info in the additional argument.


That's more or less how Tokyo works. Almost no on-street parking, people have to prove that they have a parking spot when buying a car, liberal zoning so there are lots of very small pay parking lots around the city. It works really well IMO but it would be politically very difficult in North America.


Sharpening a knife to r/sharpening standards is hard. But just honing frequently and occasionally using a cheap sharpener will get you further than 95% of home chefs.


> This has already led to more easily introducing GUI features like a new GTK titlebar tabs option

Yes! This is huge, I previously gave up on Ghostty because the title bar wasted so much space on my laptop screen: https://bsky.app/profile/reillywood.bsky.social/post/3lebapf...

I found the PR in case anyone else is curious what the new functionality looks like: https://github.com/ghostty-org/ghostty/pull/8166


If it’s not maximized, the space isn’t wasted. The title in the response image looks incredibly crowded. May be ok if several buttons could be removed from the titlebar.


It's literally wasted because it's used for nothing useful. Also, you can have other apps that now can take up less area.


Titlebars are quite useful, I use them frequently to move, raise, lower, and maximize windows.


Oh sure, but some people use more ergonomic ways to perform those actions, so to them the title bars would be a waste even if not maximized


Nothing more “ergonomic” than a titlebar. Discoverable, standard, usable.


Many people use tiling window managers, so title bars become useless. The first thing I did in configuring ghostty was disabling window decoration for this reason.


Probably ten times more people don’t.


I work in this space and I was not able to understand how this project works in a couple minutes. The README feels LLM-generated. I think you're supposed to point this at your MCP server's code and not the server itself, is that right?


sorry for the issues you are facing. can you let me know what was the issue? the repo can scan github mcp server code posted in the repo like https://github.com/punkpeye/awesome-mcp-servers and provide a quick, deep, or deep with ai analysis. let us know if there is anything we can help with.


Aider is good at one-shotting Git commits, but requires a human in the loop for a lot of iteration. Claude Code is better at iterating on problems that take multiple tries to get right (which is most problems IMO). I was really impressed by Aider until I started using CC.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: